Code Profiling ASP.NET MVC2 applications

The thread here seems close: Profiling ASP.NET websites with EQATEC Profiler

However, in the free version of Equatec I downloaded today there is no checkboxes for ASP.NET, and ordinary web. I have pointed the App path to my bin directory in my project folder as well as started up the localhost hosting for my application via Visual Studio.

I am open to other free tools as well. I am just looking for someway to profile the code as to optimize some reflection we are using.

I am using开发者_StackOverflow the professional edition so unfortunantly do not have access to MS Code Profiling.

I am looking to do performance profiling at this point.

Is the free version of Equatec capable of doing ASP.NET applications?

Is there a free profiler (I realize this has been asked before, and little seems to have surfaced but paid apps, but might as well ask)?

Is MVC a special thing to look for in a profiler?

Comprehensive profiling tools still seem to be quite expensive. I like the dotTrace family, but they're not free.

You haven't specified what kind of profiling you want to do. Are you trying to understand more about the memory usage of your application, or CPU usage?

There is nothing special about MVC applications when it comes to profiling. You will need a profiler that's capable of launching ASP.NET. Beyond that, MVC is just a regular bunch of class libraries.

Have you tried the free CLR Profiler? It handles ASP.NET and will show both memory and some method call activity. It's not as comprehensive as say dotTrace, but it is a great free alternative if you're starting out.

The guide is actually not out of date: the few steps described in the stackoverflow duplicate question (last edited April 8th) still describes best how you should profile ASP.NET apps. Note that you should look at the accepted answer, the one with currently 16 upvotes.

After you've build the instrumented app the important thing to note in the stackoverflow-answer above is step 3: "load your app". It means that you should cause your app to be loaded and is the only step the profiler can't do automatically for ASP.NET apps.

You typically load the app simply by navigating to it in a browser so you simply need to do that after the build-step. When your (instrumented) code is activated the profiling part of it will spring into life and connect to the profiler and then you can take snapshots.

Note that ASP.NET doesn't need a main entry point. That's just an added convenience for automatically taking snapshots for real executables that has a Main method.

You just need a .NET profiler.

Profiling WebForms, MVC, SharePoint, Sitecore, Ektron, Sitefinity, or any other product that runs on .NET doesn't change that.