Forum Discussion

Lane_Schafer_55's avatar
Lane_Schafer_55
Icon for Nimbostratus rankNimbostratus
Mar 31, 2006

iControl web referance error in VS 2k5

Hey, i keep getting an error in VS 2k5 when trying to add the iControl url https:///iControl/iControlPortal.cgi? that says this

 

 

"Unable to cast COM object of type 'System.__ComObject' to interface type 'EnvDTE.IVsExtensibility'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{3C536122-57B1-46DE-AB34-ACC524140093}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE))."

 

 

But on the same box in VS 2k3 it works just fine...is there any other setup that has to be done for 2k5 as opposed to 2k3...please help!
dev
devops
iControl
v9

1 Reply

Sort By
  • Joe_Pruitt's avatar
    Joe_Pruitt
    Apr 06, 2006
    This seems to be a common issue that people have reported with VS.NET. The EnvDTE control seems to be a internal extensibility component of VS. This seems to be a bug with VS.NET. I've worked around this by typing the full url to the WSDL the first time in the web reference wizard. For some reason in my install, browsing to our WSDL listing and then clicking on a WSDL file will result in this error but fully specifying the WSDL file on the initial request will work. But, we've had customers using the Express versions of VS that say neither method works.

     

     

    The only other option is to go with the manual route. VS.NET comes with a command line tool (wsdl.exe) to parse wsdl documents into C or VB classes. You can either get the WSDL from the BIG-IP directly via a browser or from the SDK. Place it in your project directory, use WSDL.exe to create the client bindings, and then add it as an existing file to your project. Kind of a pain I know, but until MS comes out with a fix for this, there may not be any other option.

     

     

    -Joe