I've heard how great the CLR Profiler can be when trying to track down memory leaks, and I'd love to use it on my modifications to a website. I've read through the documentation and I was under the impression that I could use the Profiler without too
much trouble. However, I can't seem to get it working, so some help would be greatly appreciated.
Here's the situation:
The website I've modified was originally Classic ASP. Only the new modules are coded in ASP.NET. I start the CLR Profiler and it asks me to start my ASP.NET project, which I do through localhost. I bring up the website (Classic ASP login
screen) in Internet Explorer, log into the site, and then start hitting the ASP.NET pages. However I don't see any output for the CLR Profiler, I can't click the Kill Application button, and the "Waiting for ASP.NET to start common language runtime
- this is the time to load your test page" message never disappears.
I saw a note that I might need to change my machine.config to use System, but making that change doesn't seem to resolve the problem. What could be my problem? Will the CLR Profiler simply not function with my website?
Also, if it's important, I used Visual Studio 2010 to develop the pages.
Thanks in advance!
View Complete Post