I'm trying to use profiler 7 (full version) to profile a WCF service hosted in IIS 6, on Win Server 2003. I am having trouble getting any meaningful trace in the profiler. I don't know if they are related but here are the steps.
Using original port
1. Installed profiler 7 on existing QA environment.
2. Run profiler, start a new session
a. Select ASP.NET web application (IIS)
b. Enter root of service in URL (e.g. http://localhost/MyService
); also tried with actual url (http://localhost/MyService/Service.svc
) with identical results.
c. Profiling mode: Line-level (most detailed)
d. Profile on original port
I do see w3wp and friends recycling, and after generating traffic from a remote client, I see activity. However, the code trace stops at a constructor and does not allow me to deep-dive into it. I can point it to the single source code file (service.cs), and it shows the right code, but it does not allow me to deep-dive past that one assembly.
Using unused port
When I try to do the same with an unused port (e.g. 81), the site never responds. That is, trying to get the wsdl (http://localhost/MyService/MyService.svc?wsdl
) shows a 404 both locally and remotely (using the server's IP of course).
I am much more interested in using port 80 and trying to get my code deep dive to work. I looked at the integration directions on here, and I didn't see anything relevant.
Oh, and I'm doing all this on the server as an administrator, if that matters.
Any ideas? I am clearly doing things incorrectly.