A Windows Store application is a new type of application that runs under Windows 8. To help you develop and debug such applications, dotTrace Performance provides an ability to profile them.
- Start dotTrace as a standalone application.
Do one of the following:
- On the menu bar, choose File | Profile. The Profile dialog box opens. Select Windows Store Application, then click OK or just double-click Windows Store Application.
- Click Profile on the Home tab. Click Windows Store Application in the list.
By default, your application is profiled on the local computer.
If you want to start profiling on a remote computer, do one of the following:
- Click Profile on remote computer to specify a remote agent url and thereby define what remote agent to use.
- Select a remote host in the Host drop-down list and click it.
- Click an application to be profiled in the Packages list.
- Select a profiling mode in the Profiling type drop-down list. For more information, see Choosing the Right Profiling Mode.
- Specify which method you want to use for time measurement by selecting an item in the Measure drop-down list. For more information, see Choosing the Right Time Measurement Method.
- If the Start profiling immediately check box is selected, dotTrace Performance starts gathering performance data immediately after you click Run and close the current dialog. Otherwise, dotTrace Performance waits until you press Start Profiling in the dotTrace Performance Controller window. For more information, see Launching and Controlling the Profiling Process.
Optionally, click the arrow to display and configure additional settings, such as
High accuracy, Enable inlining,
Merge threads with equal names etc.
- Select the High accuracy check box to take into account time spent in profiler itself by taking more time samples.
- Clear the Enable inlining check box to disable JIT-inlining in order to get call stacks that closely resemble the structure of application's source code.
- Select the Merge threads with equals names check-box and as a result get the performance information for all threads with the same name under a single thread node in Call Tree and Threads Tree views.
- Click Edit Filters to define in advance what functions should be filtered out and what should be profiled line by line.
- Click Edit Symbol Search Policy to specify locations where the profiler looks for debugging information. For more information, see Edit Symbol Search Policy.
- Select the Use profiler API check box to allow you to control profiling directly from the code of the profiled application. For more information, see Advanced Profiling Using dotTrace API.
- Click Run.