Profile WinRT Application
WinRT applications are applications that use Windows Runtime framework. More specifically, these are Windows Store and Universal Windows Platform (UWP) applications.
Note that dotTrace is unable to profile a UWP application if it uses .NET native tool chain. To profile such an application, you should disable the Compile with .NET Native tool chain option in Visual Studio (via the menu ) and rebuild the project.
To profile a WinRT application
Run dotTrace as a standalone application. The dotTrace Home window will open.
Add a run configuration - the configuration that tells dotTrace how to run the profiled application:
Under Choose what you want to profile, New Process Run, click Add run configuration.
In the New Run Configuration wizard, choose WinRT Application and click Next.
Specify application options:
In Packages, choose the application you are going to profile. If the application you are looking for is missing, click Refresh to update the list.
In Set environment variables specify the required environment variables. Each variable must be specified on a new line.
Make sure the created run configuration is selected in the New Process Run list.
Under Choose how you want to profile it, specify profiling options:
Profiling Type: typically, you should choose between Sampling (evaluate performance and determine 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.
If you want dotTrace to start collecting profiling data right after you start the session, under Run profiling, select Collect profiling data from start.
Click Start. This will start the profiling session.
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
After you collect the data, either close the profiled application or detach the profiler using the Detach button in the controller window.