Skip to content

Fix build suggestions #29114

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.

Sign up for GitHub

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
Apr 20, 2022
Merged

Fix build suggestions #29114

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 3 additions & 3 deletions docs/core/diagnostics/eventsource-collect-and-view-traces.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,13 +85,13 @@ keyword-based filtering, and "Demo" does no keyword or level filtering.

## Visual Studio

The [Visual Studio profiler](https://docs.microsoft.com/visualstudio/profiling) supports both collecting and viewing traces. It also can view traces
The [Visual Studio profiler](/visualstudio/profiling) supports both collecting and viewing traces. It also can view traces
that have been collected in advance by other tools, such as [dotnet-trace](./dotnet-trace.md).

### Collect a trace

Most of Visual Studio's profiling tools use predefined sets of events that serve a particular purpose, such as analyzing CPU usage or allocations. To
collect a trace with customized events, you'll use the [Events Viewer](https://docs.microsoft.com/visualstudio/profiling/events-viewer) tool.
collect a trace with customized events, you'll use the [Events Viewer](/visualstudio/profiling/events-viewer) tool.

1. To open the Performance Profiler in Visual Studio, select **Alt**+**F2**.

Expand Down Expand Up @@ -177,7 +177,7 @@ of that type in the table on the right.

### Learn more

To learn more about using PerfView, see the [PerfView video tutorials](https://docs.microsoft.com/shows/PerfView-Tutorial/).
To learn more about using PerfView, see the [PerfView video tutorials](/shows/PerfView-Tutorial/).

## dotnet-trace

Expand Down
2 changes: 1 addition & 1 deletion docs/core/diagnostics/eventsource-instrumentation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,7 +187,7 @@ enabled.

### Setting OpCodes and Tasks

ETW has concepts of [Tasks and OpCodes](https://docs.microsoft.com/windows/win32/wes/defining-tasks-and-opcodes)
ETW has concepts of [Tasks and OpCodes](/windows/win32/wes/defining-tasks-and-opcodes)
which are further mechanisms for tagging and filtering events. You can associate events with specific tasks and opcodes
using the <xref:System.Diagnostics.Tracing.EventAttribute.Task%2A> and
<xref:System.Diagnostics.Tracing.EventAttribute.Opcode%2A> properties. Here's an example:
Expand Down