Restriction: This topic applies only when the Enterprise Server feature is enabled.
Prepare for debugging, see
To prepare for debugging on Enterprise Server.
Click
Project >
myprojectProperties and go to the
Debug tab.
Click the tab for the type of service or application that you want to debug and enter its details, as follows:
For a Web Service, enter the IP address of the client that will make the service request. You can also enter the fully qualified
name of the service. This is formed by taking the name of the service and appending a pound or hash character (#) followed
by the name of the operation that you want to debug. For example, if the service name for the web service that you deployed
is
http://tempuri.org/wmapserv, and the operation to be debugged is
Read, the fully qualified service name is
http://tempuri.org/wmapserv#Read.
Click
Debug > Start Debugging.
Start the Web service or the application you want to debug on the
enterprise server region. The way you do this depends on the type of application, for example:
For a Web Service, run the client program and enter some input to trigger the service. It is not possible to run the client
module from within your debug session. However, if the client program is also part of a different project than the one that
you are debugging, you can start another debug session, open the client project and run the client module.
Step through the application in the usual manner.
When the debugger reaches the
exit program statement and no line is highlighted, the service or the application exits. The debugger now waits for the next matching
service or application to start.
When you have finished debugging, click
Debug > Stop Debugging.
If specified in your Enterprise Server preferences, when closing the project it will stop and delete the enterprise server
used to debug the application.