Occasionally, using web references in VS2005, does not meet your requirements. This could be due to specific deployment issues, such as language requirements for the proxy class, specification of the proxy class namespace, use of a non-default protocol, login or other security concerns, or any number of special circumstances. Using the command line tools, with their many optional switches and arguments, will often let you fine tune your application's deployment and usability.
This section will review the different ways you can take control of the process of creating and using the proxy, allowing your consuming app to talk to the web service as though they were on the same machine.
Before proceeding with the steps of creating the proxy, it would be helpful to have a consumer application, in this case a web page, to use.
To demonstrate this and to provide a proxy class with a little more meat for analysis, we will work with the
StockTickerComplete web service developed in the previous chapter, listed in its entirety in Example 15-18.
If you don't have a virtual directory for that web service on your machine, create one now called
StockTicker. You can then see the test page for this web service by entering the following URL in a browser:
In VS2005, create a new web site called StockTickerConsumer. This web site will have several text boxes for entering the stock symbol of the firm. ...