dotTrace 2017.2 Help

Running dotTrace

Depending on your needs, you can work with dotTrace in three different ways:

The following table summarizes the pros and cons of each way.

Standalonein Visual StudioCommand-Line Tool
Summary Ideal for apps where the original project or source code is not always available or when you want to run dotTrace without having Visual Studio installed or launched. Ideal when you have to work with a number of different profiling configurations Ideal when you need to profile an existing project running under Visual Studio Ideal when you need to automate profiling. E.g., profiling on a continuous integration server
How to Run Profiling Using the dotTrace Home window Using the ReSharper | Profile menu in Visual Studio Using the ConsoleProfiler.exe command-line tool
Local Profiling /help/img/dotnet/2017.2/check.svg /help/img/dotnet/2017.2/check.svg
Additionally, profiling of run configurations is supported. E.g., you are able to profile any static method in your code
/help/img/dotnet/2017.2/check.svg
Only profiling of standalone applications and already running .NET processes is supported
Remote Profiling /help/img/dotnet/2017.2/check.svg /help/img/dotnet/2017.2/cross.svg /help/img/dotnet/2017.2/cross.svg
Controlling Profiling Session
Continuous Integration Support /help/img/dotnet/2017.2/cross.svg /help/img/dotnet/2017.2/cross.svg /help/img/dotnet/2017.2/check.svg
The dotTrace plugin to TeamCity is available
Last modified: 29 August 2017