I have just finished a web services training course.
Apparently setting a web reference uses wsdl.exe in the background so the two are equivalent for creating a proxy. However wsdl.exe does provide far more control.
Apparently setting a web reference uses wsdl.exe in the background so the two are equivalent for creating a proxy. However wsdl.exe does provide far more control.
The problem comes with the update web reference option. If you have decorated the proxy with attributes (such as a soap extension) these are lost upon regeneration. There does not seem to be a clean way of managing this. We really need more control of the template than WSDL.exe provides. I am sure that xslt could be used…
.NET 2.0 does promise more control over this generation.
