Just a short post today to address a change in how VS 2008 handles proxying your web services.
In earlier versions of Visual Studio, when we went to suck in the ASMX files that represent our web service, proxy code would get created on the client side with the same name as the class that was our web service.
If you do the same thing in Visual Studio 2008, you’ll notice that that class no longer exist. If you have a lot of classes, you’ll also notice that there are several interfaces that show up in intellisense now.
The new proxy class you are looking for is now named ClassNameSoapClient, where ClassName represents the name of the class in the web service.
Hopes this helps someone as they move to Visual Studio 2008
Like this Article? Subscribe to get every article sent to your email.
- DotNetNuke Modules – Creating Base Modules Now that we have DotNetNuke installed into Visual Studio we can go ahead and create our first modules. Actually, creating the modules is pretty simple. But it is even easier to do it […]
- Setting a Web Proxy on a WebService in .NET 3.x A couple of weeks ago I wrote an article stating that Microsoft had changed how the proxy class for web services gets created. Many people found this helpful, but I got one question on the […]
- ASP.NET AJAX using JSON – Here’s how. Last week I wrote a post about how simple JSON is. In it I explained the main differences between using JSON and using the update panel. I really started out thinking I'd get to how to […]
- The Case Against Location: File System See this picture? That’s what could happen to your application if you decide to build your ASP.NET web site using the File System location instead of the HTTP location. To illustrate, […]
About Dave Bush
Dave Bush is a .NET programmer and Certified ScrumMaster who is passionate about managing risk as it relates to developing software. When he is not writing or speaking about topics related to Application Lifecycle Risk Management (ALRM), he is an example to his peers as he develops web sites in the ASP.NET environment using industry best practices.