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.

	Standalone	in Visual Studio	Command-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		Additionally, profiling of run configurations is supported. E.g., you are able to profile any static method in your code	Only profiling of standalone applications and already running .NET processes is supported
Remote Profiling
Controlling Profiling Session	Auto-taking snapshot on process completion Using the Controller window Using the API	Auto-taking snapshot on process completion Using the Controller window Using the API	Auto-taking snapshot on process completion or by timeout Using the API
Continuous Integration Support			The dotTrace plugin to TeamCity is available

Last modified: 15 March 2019