Re: using WSDL.exe programmatically

Tech-Archive recommends: Fix windows errors by optimizing your registry

Here's an approach using System.Web.Services.Description.ServiceDescriptionImporter:

http://blogs.msdn.com/kaevans/archive/2006/04/27/585013.aspx

Kirk Allen Evans [msft]
blogs.msdn.com/kaevans

====Provided As-Is and Implies no Warranty====

"Pierre" <bubble@xxxxxxxxxx> wrote in message news:1148637625.707931.68020@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi and thx for the answer Gaurav,

Unfortunatly I have around 20 WSs to link this way and some are
added/modified on a regular basis (quite a nightmare I admit).

The idea is to build a tool that builds 1 proxy for all these WSs using
1 namespace...(i'll pass all the advantages given by using wsdl.exe
against using the Add Web Reference).

If the user has to click on 1 button instead of asking me to do the
proxy I could save up some time to do more interesting things. I have
done a .bat, but the exe not being at the same path on every computers,
it's a rather limited approach.

Once more if anyone knows how to use WSDL.exe programmatically (or to
achieve the same in another way) I'd be gratful if this person could
share this knowledge.


.

Quantcast