Click here to Skip to main content
Click here to Skip to main content

Profile and Navigate Third-Party Code as if it Were Your Own

By , 30 Mar 2012

Editorial Note

This article is in the Product Showcase section for our sponsors at CodeProject. These reviews are intended to provide you with information on products and services that we consider useful and of value to developers.

The key to understanding and improving performance is to examine as many aspects of code performance as possible. Performance bottlenecks sometimes lie in the way your code calls methods in third-party or framework assemblies but, without the source code, problems like this can be hard to identify.

Integrated Decompilation

ANTS Performance Profiler is a code profiling tool, used to identify performance issues in .NET applications. Version 7.0 introduces integrated decompilation, which lets you explore performance bottlenecks even in assemblies for which source code isn’t available.

Integrated decompilation is powered by .NET Reflector, an assembly browser and decompiler. This technology is incorporated into the profiler, so even if you’re working on a legacy application, or your application references third-party code, you can get right to the root of the performance issue. You won’t even need to leave the profiling environment. Integrated decompilation can also highlight ways in which you aren’t using third-party controls efficiently, or where those controls aren’t performing as well as expected.

Profiling Assemblies Without Source

When you’re profiling methods and assemblies with no source code file, you can generate source code from the profiler interface. Begin profiling, and select an area on the timeline that you want to investigate. In the Call Tree View, select the method that you would like to explore and click the Decompile button in the Source Code View:

337484/image_1.png

This generates source code for the method. You can then browse and navigate the automatically generated code as if it were your own. The first line of the method body is highlighted:

337484/image_2.png

If you have the assembly’s .pdb file, you can even view line-level timings for the decompiled code, letting you identify the exact line that caused the bottleneck. The heat map alongside the vertical scroll bar helps you jump directly to the lines of code that account for the greatest execution time:

337484/image_3.png

So, do the performance problems in your applications lie in your own code or elsewhere? With ANTS Performance Profiler, you can pin down the bottleneck wherever it lies.

To learn more, simply visit the Red Gate website and help yourself to a free 14-day free trial of ANTS Performance Profiler.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

Red Gate Software
Red Gate Software Ltd.
United Kingdom United Kingdom
Red Gate Software makes ingeniously simple tools used by over 650,000 Microsoft technology professionals working with .NET (incl. ASP.NET), SQL Server, Azure, and Oracle. More than 100,000 companies use our products, including 93% of the Fortune 100.

Our philosophy is to design highly usable, reliable tools which elegantly solve the problems that developers and database administrators face every day.
Group type: Organisation

4 members

Follow on   Twitter   Google+

Comments and Discussions

 
-- There are no messages in this forum --
| Advertise | Privacy | Mobile
Web03 | 2.8.140415.2 | Last Updated 30 Mar 2012
Article Copyright 2012 by Red Gate Software
Everything else Copyright © CodeProject, 1999-2014
Terms of Use
Layout: fixed | fluid