There are a few steps to do this:
Step A. Please download and install the latest script debugger first from
Step B. Ensure your IIS settings are set for profiling. Although undocumented, ideally you should have the following settings in place:
Visit your Internet Information Services Snap-In in MMC.exe. This snap in is usually located here: c:\winnt\system32\inetsrv\iis.msc.
Once you open the iis.msc snap-in, go to the Default Web Site location, and ensure the settings are:
1. Home Directory Tab:
Application Protection: Low (IIS Process)
Execute Permissions: Scripts and Executables
2. Web Site Tab:
Connection Timeout: (if you get any timeouts, increase this value to double or triple what is normal for your program).
Step C .Configure Performance/Coverage Analysis for your web service.
Navigate to the Tools=>Options settings within the .NET IDE. From there, proceed to the DevPartner options group. To the right you will see an option to "Select Analysis Method". Choose the correct DevPartner feature product, then enable "Collect information about IIS/ASP.NET applications". *Note, this feature will disable the Distributed Analysis feature product.
You may also visit other tabs for appropriate configurations.
At this time, you should be able to use Performance/Coverage Analysis to profile your WebService. After rebuilding your solution with Performance, please use 'Start without Debugging ' to run your service.
*Please also note that in order to stop inetinfo.exe you need go to Performance/Coverage settings, uncheck 'collect information about IIS/ASP.NET applications'.
This article was written for DPS version 7.0, 7.0.2 and 7.1