Forum Discussion
Dec 13, 2005
This is very bizarre. I'm seeing this as well and it seems to stem from the fact that the url for the selected wsdl is coming from a HTML page that we return with a listed set of available WSDL files. I've verified that this is also the case for other (non-F5) wsdl files when referenced from inside the "Add Web Reference" dialog.
If you specify the entire path for the WSDL file in the first request within the Add Web Reference dialog, then the import seems to work successfully.
This looks to me like a VS2005 bug.
Try entering the following url in the "Add Web Reference" dialog and see if it works:
https://1.1.0.5/iControl/iControlPortal.cgi?WSDL=System.SystemInfo
You can replace the System.SystemInfo with whichever module and interface you are interested in. All of which are available from the WSDL listing page in the iControl portal (https://1.1.0.5/iControl/iControlPortal.cgi).
Alternately, you can use the WSDL command line tool included with VS.NET (that's how we build all our sample code). You'll just have to have the SDK (or copies of the WSDL from the servers).
Let me know if this works for you.
-Joe