Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here.

Debugging XML Web Services

This topic applies to:

Visual Studio

Visual Basic

C#

C++

J#

Visual Web Developer

Express

No

No

No

No

Yes

Standard

Yes

Yes

Yes

Yes

Yes

Pro/Team

Yes

Yes

Yes

Yes

Yes

XML Web services use the common language runtime, so debugging them is very similar to debugging ASP.NET applications. The main difference is that your debugging of ASP.NET applications often focuses on visible controls and control events. XML Web services are usually deployed on a middle-tier and have no visible user interface.

Attaching to the ASP.NET worker process is no different from attaching to any other remote process. After you attach to the ASP.NET worker process, if you do not have the appropriate project open, a dialog box appears the next time the application breaks. This dialog box prompts you for the location of the application's source files. Use this dialog box to locate the source. The file name you specify in the dialog box must match the file name specified in the debug symbols, located on the Web server. For more information, see Attaching to Running Processes.

Hitting Breakpoints in XML Web Services

The debugger does not automatically attach to an XML Web service unless you step into the call. This means that any breakpoints set in the XML Web service will not be hit unless you step into the call. If you try to run to the breakpoint by using Start Debugging or Continue, instead of using Step Into, the breakpoint will not be hit.

See Also

Community Additions

ADD
Show:
© 2015 Microsoft