NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet, #520 most downloaded on NuGet
Event Tracing for Windows (ETW) is a powerful logging mechanism built into the Windows OS and is used extensively in Windows. You can also log ETW events yourself code using the System.Diagnostics.Tracing.EventSource class. The TraceEvent library conains the classes needed to control ETW providers (including .NET EventSources) and parse the events they emit. The library includes -- TraceEventSession which can enable ETW providers, -- EtwTraceEventSource which lets you read the stream of ETW events, and -- TraceLog which is is digested form of ETW events which include decoded stack traces associated with the events. See https://github.com/Microsoft/perfview/blob/master/documentation/TraceEvent/TraceEventLibrary.md for more.
Latest stable
4.0.0
Last release 1 months ago
14 Oct 2026
Ships fairly regularly
a new release about every 4 weeks
Nearly every release is documented
notes for 59 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
13 years old
133 releases · first in 2013
Drag across the ruler to compare, or tap a release to open it.
Disable collection of TPL events by default due to their verbosity. This is configurable via /TPLEvents.
Roll-up until 2021/02/22.
Changes that will accrue to consuming CLRMD 2.0
Roll-up through 01/25/2021.
Add support for advanced memory investigations of the JIT.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Roll-up through 01/05/2020.
• Add support for advanced memory investigations of the JIT. • Include TraceEvent.props in the buildTransitive directory of the TraceEvent NuGet package. • Symbol / source file improvements. • Remove dotnet.myget.org from the default symbol path, since it has been decommissioned.
Fix PDB discovery for .diagsession files.
Roll-up through 11/8/2020.
Support for capturing traces of Windows Process-Isolation containers from the host rather than from inside the containers:
Roll-up through 09/21/2020.
Fix TraceEvent NuGet package to include msvcp140.dll and vcruntime140.dll.
Roll-up through 09/14/2020.
Most visible changes:
Package msvcp140.dll and vcruntime140.dll alongside msdia140.dll, since the new version of msdia140.dll is dependent on them, and not collection machi
Roll-up through 9/4/2020.
Most visible changes:
Updated msdia140.dll included with PerfView and TraceEvent to a new version that is compiled with CFG enabled.
Roll-up through 8/5/2020.
Most visible changes:
Roll-up through 8/5/2020.
Most visible changes:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fixed an issue where ETW stacks contain the wrong thread frame.
Fixed an issue where ETW stacks contain the wrong thread frame.
Fix the missing System.Runtime.CompilerServices.Unsafe dependency in the TraceEvent nuget package.
Fix the missing System.Runtime.CompilerServices.Unsafe dependency in the TraceEvent nuget package.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Includes support for the new EventPipe nettrace format.
Roll-up until 6/18/2019.
Includes support for the new EventPipe nettrace format.
Nothing published for this version
Includes preview support for streaming from EventPipe.
Rollup until 4/24/2019.
Includes preview support for streaming from EventPipe.
Nothing published for this version
This is mostly a bug fix release from the 2.0.26. However there are a few small new features:
This is mostly a bug fix release from the 2.0.26. However there are a few small new features:
To get the tool simply download the PerfView.exe executable and use it. I include the PDB files in case you need to debug something, but that is a rare case and you don't need to do that normally.
The PerfView64.exe is optional. It is a small wrapper that launches PerfView as a 64 bit application. If you are dealing with very large traces that cause 'out of memory' errors, this can be used to avoid the problem. Note that you need PerfView.exe to be present next to PerfView64.exe for it to work.
Like all versions of PerfView you can see the specific release notes from the past year by accessing the 'Help -> Release Notes' menu entry.
You can also see detailed informational about what changes went into this release by viewing the Github history.
Nothing published for this version
Nothing published for this version
Rollup until 1/18/.19. This includes support for Microsoft.Diagnostics.Tracing.Stacks.Formats.SpeedScopeWriter. See #842 for more.
Rollup until 1/18/.19. This includes support for Microsoft.Diagnostics.Tracing.Stacks.Formats.SpeedScopeWriter. See #842 for more.
Rollup until 1/2/19. This includes support for generic Microsoft-Diagnostics-ActivityTracking. See https://github.com/Microsoft/perfview/pull/828.
Rollup until 1/2/19. This includes support for generic Microsoft-Diagnostics-ActivityTracking. See https://github.com/Microsoft/perfview/pull/828.
Rollup until 12/13/18. This includes a fix for CoreFX bug associated with decoding nullable types in EventSources. https://github.com/dotnet/corefx/is
Rollup until 12/13/18. This includes a fix for CoreFX bug associated with decoding nullable types in EventSources. https://github.com/dotnet/corefx/issues/33013 Publishing this so that bug can be fixed.
Rollup until 12/12/2018. Bug that provoked the release was https://github.com/Microsoft/perfview/issues/755, where Building with TraceEvent on a Deskt
Rollup until 12/12/2018. Bug that provoked the release was https://github.com/Microsoft/perfview/issues/755, where Building with TraceEvent on a Desktop framework would sometimes give a missing dependency error for the Microsoft.Win32.Registry.dll.
Fixed a moderately serious bug introduced int 2.0.29, that causes confusion about the thread for an event. The ramifications might be widespread but s
Fixed a moderately serious bug introduced int 2.0.29, that causes confusion about the thread for an event. The ramifications might be widespread but subtle. We noticed it in the 'Thread Time with Tasks' views. We recommend upgrading from 2.0.29 ASAP.
Nothing published for this version
This is a minor bug fix from the previous release. The Start-Stop activity logic had disabled showing AWAIT time. If you use that view, then this bug
This is a minor bug fix from the previous release. The Start-Stop activity logic had disabled showing AWAIT time. If you use that view, then this bug fix is important, otherwise it is not.
This is a bug fix release from the 2.0.23. If you use the Thread Time View with Start-Stop Tasks view you will want to pick up this new release as there was a regression in May that caused AWAIT time to not be displayed. Otherwise there are only small fixes.
To get the tool simply download the PerfView.exe executable and use it. I include the PDB files in case you need to debug something, but that is a rare case and you don't need to do that normally.
The PerfView64.exe is optional. It is a small wrapper that launches PerfView as a 64 bit application. If you are dealing with very large traces that cause 'out of memory' errors, this can be used to avoid the problem. Note that you need PerfView.exe to be present next to PerfView64.exe for it to work.
Like all versions of PerfView you can see the specific release notes from the past year by accessing the 'Help -> Release Notes' menu entry.
You can also see detailed informational about what changes went into this release by viewing the Github history.
rollup of bug fixes. See github for details.
rollup of bug fixes. See github for details.
This is a small bug-fix release of PerfView since the 2.0.15 release. Here are some of the fixes. Also added a /DotNetCallsSampled option that samples every ~1000 calls, which is infrequent enough that it does not affect perf too badly (more like 10% rather than 100s of %).
To get the tool simply download the PerfView.exe executable and use it. I include the PDB files in case you need to debug something, but that is a rare case and you don't need to do that normally.
The PerfView64.exe is optional. It is a small wrapper that launches PerfView as a 64 bit application. If you are dealing with very large traces that cause 'out of memory' errors, this can be used to avoid the problem. Note that you need PerfView.exe to be present next to PerfView64.exe for it to work.
Like all versions of PerfView you can see the specific release notes from the past year by accessing the 'Help -> Release Notes' menu entry.
You can also see detailed informational about what changes went into this release by viewing the Github history.
rollup of bug fixes. See github for details.
Added support for the 'dynamic' keyword to fetch fields from a TraceEvent. (See https://github.com/Microsoft/perfview/pull/630)
Instead of doing
F(TraceEvent myEvent) {
Console.WriteLine("MyField = {0}", myEvent.PayloadByName("MyField"));
}
You can do
F(TraceEvent myEvent) {
dynamic dEvent = (dynamic) myEvent;
Console.WriteLine("MyField = {0}", dEvent.MyField);
}
It is not any faster, bit it is a bit more convenient.
Fixed a bug where native symbol resolution failed on .NET Core (because CustomMarshalers is not supported there).
Fixed errors trying to load Registry or System.Runtime dlls when running on .NET Desktop and collecting ETW data.
Fixed runtime errors trying to load TraceRelogger.dll (which should have been TraceReloggerLib.dll).
Fixed runtime errors trying to load TraceRelogger.dll (which should have been TraceReloggerLib.dll).
Nothing published for this version
Adds Support for Version 3 of the EventPipe file format to the library.
Adds Support for Version 3 of the EventPipe file format to the library.
This is a minor update from the 2.0.2 version.
This is a minor update from the 2.0.2 version.
It contains fixes for problem loading DLLs at runtime (Issue #518 and related). There were also other minor fixes. See the Github history for more.
This is the first OFFICIAL public release of PerfView since July 2016 (a year and a half). Version 2.0.2 has Goto Source working for .NET Core Framewo
This is the first OFFICIAL public release of PerfView since July 2016 (a year and a half).
Version 2.0.2 has Goto Source working for .NET Core Framework code (SourceLink support).
This version of PerfView (unlike the prereleased versions) has been signed with the Microsoft private key.
The copy of PerfView in the Download Center is old and will eventually be removed. Currently there is documenation there that points you to this place.
To get the tool simply download the PerfView.exe executable and use it. I include the PDB files in case you need to debug something, but that is a rare case and you don't need to do that normally.
The PerfView64.exe is optional. It is a small wrapper that launches PerfView as a 64 bit application. If you are dealing with very large traces that cause 'out of memory' errors, this can be used to avoid the problem. Note that you need PerfView.exe to be present next to PerfView64.exe for it to work.
Like all versions of PerfView you can see the specific release notes from the past year by accessing the 'Help -> Release Notes' menu entry. Highlights of this release include
This is the first release of the Microsoft.Diagnostics.Tracing.TraceEvent nuget package in almost 2 years!
Sorry about that but the transition to Git, The new way of signing, and just other priorities (like shipping .NET Native) caused delays. But now we are back and it is relatively easy
This nuget package is published at nuget.org at https://www.nuget.org/packages/Microsoft.Diagnostics.Tracing.TraceEvent/ in the standard way.
However the symbol package (containing any symbol files as well as complete source), is attached below for archival purposes.
TODO: give a summary of the changes.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.