Forum Discussion

Mark_Canup_6238's avatar
Mark_Canup_6238
Icon for Nimbostratus rankNimbostratus
Mar 14, 2005

WSDL - Common conflicts

I've got a ASP.NET application in C that is using WSDL files for 9.x and 4.x interfaces.     I'm using several different WSDL files in this application, but many of them has their own defin...
dev
devops
iControl
Joe_Pruitt's avatar
Joe_Pruitt
Mar 14, 2005
The reason we did this was so that a user could use any wsdl file without dealing with wsdl includes (which at the time of our initial design were not standard yet).

 

 

The best way to work around this is to specify a namespace with the wsdl.exe command. Accessing by web reference automatically does this but the command line doesn't. So for LocalLB.VirtualServer.wsdl do something like the following

 

 

wsdl.exe /namespace:LocalLBVirtualServer LocalLB.VirtualServer.wsdl

 

 

Do the same for the rest of the WSDL files you are working with and then each of the interfaces will be uniquely defined.

 

 

-Joe