Forum Discussion
Nov 29, 2006
We've had this issue reported before and I believe it has to do with a bug in the "Express" versions of .NET not allowing web references to be created to ssl based web services. We haven't seen this issue with the full blow versions.
You can try these work-arounds.
1. Open a browser and connect to the iControl portal link you included. After it authenticates, it will supply a list of links to the available WSDL files. Copy the direct link to the interface you want to add and then try your procedure again with the direct URL (ie. http://192.168.1.198/iControl/iControlPortal.cgi?WSDL=LocalLB.Pool ) bypassing the iControl Portals WSDL listing.
If this doesn't work...
2. download the SDK
2a. open a visual studio command prompt window
2b. change directories to the sdk_root/sdk/wsdl directory
2c. Run wsdl.exe on the WSDL for the interface you are interested in.
2c. copy the generated .cs or .vb file to your project and select add existing item.
This is essentially what the web reference does but this is the manual step. Take a look at all the .NET samples in the iControl SDK as references as this is how they do it. There is a directory in each project with a batch file to compile the appropriate wsdl files for the respective projects.
Let me know if this works out...
-Joe