Debugging XML Web Services

[This documentation is for preview only, and is subject to change in later releases. Blank topics are included as placeholders.]

This topic applies to:


Visual Basic



Web Developer


Topic does not apply Topic does not apply Topic does not apply Topic does not apply


Topic does not apply Topic does not apply Topic does not apply Topic applies

Pro and Team

Topic applies Topic applies Topic does not apply Topic applies

Table legend:

Topic applies


Topic does not apply

Does not apply

Topic applies but command hidden by default

Command or commands hidden by default.

XML Web services use the common language runtime. Therefore, debugging a Web service is similar to debugging an ASP.NET application. The main difference is that debugging ASP.NET applications frequently focuses on interface controls and control events. Web services are usually deployed on a middle tier and have no user interface.

Attaching to the ASP.NET worker process is the same as attaching to any other remote process. For more information, see Attaching to Running Processes.

The debugger does not automatically attach to a Web service unless you step into the Web service call.. Therefore, breakpoints in a Web service are not hit unless you step into the call. If you try to reach the breakpoint by using Start Debugging or Continue instead of Step Into, the breakpoint is not hit.

If you hit a breakpoint in a Web service and do not have the Web service project open, a dialog box appears and prompts you for the location of the source files. Use this dialog box to locate the source. The file name that you specify in the dialog box must match the file name that was specified in the debug symbols, located on the Web server.