Automating WSDL.exe in a Custom Build | I have a web application written in C# that consumes several internal web services. We have a development tier, a testing tier, and a production tier. Also, we use the `WSDL.exe` command to generate a `Proxies.cs` file for a given tier's web services.


When we are ready to deploy our code up the stack from development to test or test to production, we need to run the `WSDL.exe` command to point to the appropriate version of the web services.


Is there a generally accepted way to automate this?