Profile .NET Core or .NET Application

1. Run dotTrace as a standalone application. The dotTrace Home window will open.

2. Add a run configuration – the configuration that tells dotTrace how to run the profiled application:

   1. Under Choose what you want to profile, New Process Run, click Add run configuration.

   2. In the New Run Configuration wizard, choose .NET and .NET Core and click Next.

   3. Specify application options:

      • Path to the application executable (if it's a self-contained deployment) or to a library file (if it is a framework-dependent deployment).

      • Command-line Arguments for the executable (if required).

      • A full path to the application Working directory (by default, it's the same directory where the executable is located).

      • Set environment variables lets you run the profiled application with specific environment variables. Each variable must be specified on a new line.

   4. Click Save.

3. Make sure the created run configuration is selected in the New Process Run list.

4. Under Choose how you want to profile it, specify profiling options:

   • Profiling Type: typically, you should choose between Sampling (evaluate performance and determine the slowest methods in your app) and Timeline (same as Sampling but with additional timeline data). Learn more about profiling types

   • Optionally, if your application creates a number of processes, and you want to profile only specific ones, configure process filters.

   • If required, specify other profiling options.

5. If you want dotTrace to start collecting profiling data right after you start the session, under Run profiling, select Collect profiling data from start.

6. Click Start. This will start the profiling session.

7. Go through a particular workflow in your application (if you want to evaluate its performance) or reproduce a particular performance issue. Collect snapshots using the Get Snapshot button in the profiling controller window. Learn more about how to control the profiling session

8. After you collect the data, either close the profiled application or detach the profiler using the Detach button in the controller window.

9. Analyze the collected snapshots using dotTrace Viewer.

To profile a .NET Core application

1. Download dotTrace command-line profiler.

2. To profile an application, run, for example:

   dotTrace.exe start --save-to=C:\snapshots\snapshot.dtp C:\Projects\MyNetCoreApp\MyApp

3. Learn more about profiling with the command-line profiler

1. Run dotTrace as a standalone application. The dotTrace Home window will open.

2. Add a run configuration – the configuration that tells dotTrace how to run the profiled application:

   1. Under Choose what you want to profile, New Process Run, click Add run configuration.

   2. In the New Run Configuration wizard, choose .NET and .NET Core and click Next.

   3. Specify application options:

      • Path to the application executable (if it's a self-contained deployment) or to a library file (if it's a framework-dependent deployment).

      • Command-line Arguments for the executable (if required).

      • A full path to the application Working directory (by default, it is the same directory where the executable is located).

      • Set environment variables lets you run the profiled application with specific environment variables. Each variable must be specified on a new line.

      • If you profile a web application and want its URL to be opened once the profiling starts, select Open URL and specify the URL. The in browser parameter lets you select a browser for opening the URL.

   4. Click Save.

3. Make sure the created run configuration is selected in the New Process Run list.

4. Under Choose how you want to profile it, specify profiling options:

   • Profiling Type: typically, you should choose between Sampling (evaluate performance and determine the slowest methods in your app) and Timeline (same as Sampling but with additional timeline data). Learn more about profiling types

   • Optionally, if your application creates a number of processes, and you want to profile only specific ones, configure process filters.

   • If required, specify other profiling options.

5. If you want dotTrace to start collecting profiling data right after you start the session, under Run profiling, select Collect profiling data from start.

6. Click Start. This will start the profiling session.

7. Go through a particular workflow in your application (if you want to evaluate its performance) or reproduce a particular performance issue. Collect snapshots using the Get Snapshot button in the profiling controller window. Learn more about how to control the profiling session

8. After you collect the data, either close the profiled application or detach the profiler using the Detach button in the controller window.

9. Analyze the collected snapshots using dotTrace Viewer.

1. Download dotTrace command-line profiler.

2. Depending on the .NET Core version used by the profiled application, run one of the following:

   • To profile a .NET Core 3.1 (or later) application MyApp:

     ./dotTrace.sh start --framework=NetCore --save-to=~/snapshots/snapshot.dtp ~/Projects/MyNetCoreApp/MyApp

   • To profile a .NET Core 3.0 (or earlier) application MyApp:

     ./dotTrace.sh start --framework=NetCore --save-to=~/snapshots/snapshot.dtp --support-earlier-net-core ~/Projects/MyNetCoreApp/MyApp

3. Learn more about profiling with the command-line profiler.