Skip to content

Update profiling-feature-tour.md #1690

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 15, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/profiling/profiling-feature-tour.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ While you are debugging, you can use the **Diagnostic Tools** window to analyze

The **Diagnostic Tools** window is often the preferred way to profile apps, but for Release builds you can also do a post-mortem analysis of your app instead. If you want more information on different approaches, see [Run profiling tools with or without the debugger](../profiling/running-profiling-tools-with-or-without-the-debugger.md). To see profiling tool support for different app types, see [Which tool should I use?](#which-tool-should-i-use).

> ![NOTE]
> [!NOTE]
> You can use the post-mortem tools with Windows 7 and later. Windows 8 and later is required to run profiling tools with the debugger (**Diagnostic Tools** window).

## Analyze CPU Usage
Expand Down Expand Up @@ -162,4 +162,4 @@ Here is a table that lists the different tools Visual Studio offers and the diff
|[JavaScript Memory](../profiling/javascript-memory.md)|no|yes for HTML, no for XAML|no|

## See also
[Debugging in Visual Studio](../debugger/debugging-in-visual-studio.md)
[Debugging in Visual Studio](../debugger/debugging-in-visual-studio.md)