This may be documented elsewhere, but I had a hard time finding it so I’m going to write a quick blog entry about it for my reference.
I needed to build a Visual Studio 2013 project that had a connection to a Web Service. However the the code would only have access to the web service once deployed. In essence I needed to tell Visual Studio how to access the web service without actually having access to the web service.
The solution was actually quite simple, though not exactly intuitive. First get the WSDL file for the web service to be referenced. This usually involves appending the ?wsdl variable to the web service URI.
In my case I used Internet Explorer from a computer that could access the web service (i.e. behind the firewall) and copied the WSDL content to a local file.
Once you have a local copy of the web service WSDL file; adding the Web Reference to Visual Studio is pretty straightforward.
This should load everything Visual Studio needs to know how to call the web service. This won’t really help you test the code, but it will let you get a clean build.
A simple code example using VB.NET LAMDA’s to create an inline BackgroundWorker object. I’m not a VB guru so there may be better ways to do this.
An information technology professional with twenty two year's experience in systems administration, computer programming, requirements gathering, customer service, and technical support.