Launching profiled application from within Visual Studio

1. Open your solution in Visual Studio

2. Start the profiler with a toolbar button in Visual Studio:

Alternatively, you can start the profiler from Windows Start menu.

3. In the profiler window, enusre profiling is enabled.

4. Start application to profile with Visual Studio "Debug" button:

5. Connect to the profiled application from the profiler window.

If you cannot connect to the started application because it is shown with status "Started without profiler", re-start it with "Debug" (it is possible if Visual Studio debug helper process <application name>.vshost.exe has started before you have enabled profiling).

Easy way to open source code of profiling results in Visual Studio

The navigation feature only works for own classes of solution, i.e. corresponding source files should be added to the solution. It will not be able to open source code for core classes or library classes.

When profiling applications, you usually need to browse to the related source code to understand the root of a performance problem. When it is found and located, you edit the source code to fix it.

Instead of forcing you to tell profiler where the source code of your application is located and showing the code in a feature-limited home-made editor surrogate, YourKit provides an alternative approach. When you have a method, class or field selected in the profiler UI, just click Tools | Open Declaration in Visual Studio (F7) to automatically open the underlying source code in the VS editor - the best place to browse and edit the code.

This navigation action always works on the current selection and is available in both CPU and memory views.

The integration is supported for Microsoft Visual Studio 2005, and 2008.