Comments
1 comment
-
Thanks for your post. The two most common causes for this on ASP .NET are
- The ANTS Profiler project type is 'profile performance', the 'profile only methods with source code' option is selected and the web application is not a debug build
- A limitation in ANTS Profiler that does not allow profiling of ASP .NET web applications when the machine.config specifies the SYSTEM account
The second issue is described in our Knowledge Base.
Hopefully this helps.
Add comment
Please sign in to leave a comment.
I have the assmebly being created in debug mode.
I hit the play button that appears from ANT Profiler on Visual Studio
I select Detail Mode
I select ASP.NET Web App hosted on the ASP.NET development web server
I select an ASPX page for the "Path to ASP.NET Web Application"
I set the port to be 1367 as that is the port I see when I am running web apps locally. (http://localhost:1367/MyApp)
I run certain pages that I know will be hitting the methods I want to profile.
I take a snapshot.
Can someone help with what I'm doing wrong?
Thanks.