Contents:

Download MSBuild Structured Log Viewer

or, install from WinGet:

C:\> winget install KirillOsenkov.MSBuildStructuredLogViewer

or, install from Chocolatey:

C:\> choco install msbuild-structured-log-viewer

Instructions for Mac

Search syntax reference

dotnet build -bl

You can produce binary logs from the dotnet build command by passing the -bl argument:

dotnet build -bl

msbuild /bl

Pass /bl to record all build events to a binary log file:

rawhide 2 dirty deeds updated

Double-click the .binlog file to open it in MSBuild Structured Log Viewer:

rawhide 2 dirty deeds updated

Binlogs from Visual Studio

Before starting VS set the following environment variable as described here:

    SET MSBuildDebugEngine=1
    SET MSBUILDDEBUGPATH=c:\some\path

See more information about design-time builds here:
https://github.com/dotnet/project-system/blob/master/docs/design-time-builds.md

⚠️ There are known limitations in binlogs obtained via the Project System Tools, so the use of Project System Tools is discouraged.

Replaying a .binlog to reconstruct text logs

You can pass a .binlog file to MSBuild instead of a project/solution to replay it to other loggers, as if a real build was happening. This allows you to reconstruct a text log of any verbosity given the .binlog file. Read more at: https://github.com/Microsoft/msbuild/wiki/Binary-Log#replaying-a-binary-log

Binary log advantages

Read more about the new MSBuild binary log format (*.binlog)

Viewer Features

The MSBuild Structured Log Viewer can build projects and solutions or open existing log files:

rawhide 2 dirty deeds updated

Leverage the source code of projects and targets embedded in the log file:

rawhide 2 dirty deeds updated

The viewer supports two file formats:

  1. *.binlog (official MSBuild binary log format, produced by msbuild.exe /bl
  2. *.xml (for large human-readable XML logs)

The viewer can read all formats and can save to *.xml.

See here for the list of viewer features

Sensitive data redaction

Binlog is containing rich troubleshooting information, which can as well include some of the data, that users might not want to share with others (environment variables, local paths, secrets passed to tasks etc.) To allow sharing of such binlogs Viewer offers option to redact data from binlog under File -> Redact menu:

rawhide 2 dirty deeds updated

Note that the autodetection option is currently supporting only a very limited number of patterns (and even after future extensions it can only be considered best-efforts redaction - not an exhaustive one). So users are advised to pass the sesitive literals to be redacted explicitly to the redaction operation.

Command-line help for the /bl switch

See MSBuild command-line help msbuild /? for more information on the /bl switch. The switch is available starting with MSBuild 15.3 (Visual Studio 2017 Update 3 or newer).

Rawhide 2 Dirty Deeds Updated

The original "Rawhide" series, which aired from 1959 to 1966, was a staple of American television, captivating audiences with its blend of action, adventure, and humor. The show followed the misadventures of the 7th Cavalry Regiment's B Troop, led by the stalwart Captain James "Jim" Crown (later replaced by Captain Owen 'Rip' Smith), as they navigated the challenges of the American frontier. Fast-forward to the present, and we find ourselves with "Rawhide 2: Dirty Deeds Updated," a reimagined continuation of the beloved series. This modern iteration promises to breathe new life into the classic franchise while maintaining the spirit of its predecessors.

The updated series tackles a range of pressing issues, from the psychological effects of war to the challenges of operating in a rapidly changing world. The show's writers have skillfully woven in themes of social justice, exploring the treatment of marginalized communities and the role of the military in maintaining peace and stability. This thoughtful approach allows "Rawhide 2: Dirty Deeds Updated" to resonate with modern audiences while staying true to the spirit of adventure and camaraderie that defined the original. rawhide 2 dirty deeds updated

In updating the characters for a modern audience, the show's creators have taken care to maintain the essence of the original while infusing them with new depth and nuance. Fans of the original series will notice nods to classic characters, such as the wise and witty Sergeant Merdock, now reimagined as a seasoned, tech-savvy sergeant major. The new characters, like Private Jackson, a former street-smart urban youth, and Private Luna, an expert linguist and cultural advisor, add a rich layer of diversity and complexity to the Troop. The original "Rawhide" series, which aired from 1959

By reimagining the classic Western genre for the 21st century, "Rawhide 2: Dirty Deeds Updated" offers a fresh take on familiar tropes. The show's creators have cleverly incorporated modern technology, such as drones and advanced communications systems, to enhance the storytelling and action sequences. The result is a visually stunning and engaging series that pays homage to its roots while forging a new path. This modern iteration promises to breathe new life

"Rawhide 2: Dirty Deeds Updated" takes creative liberties to appeal to contemporary audiences. The new series shifts its focus to a diverse and dynamic cast of characters. The new Troop leader, Captain Rachel 'Hawk' Wilson, is a strong, no-nonsense woman who commands respect and inspires loyalty from her team. The ensemble cast includes a diverse range of soldiers, each with their own unique skills and backstories. This refresh allows the show to tackle modern themes, such as identity, social justice, and the complexities of military life.

"Rawhide 2: Dirty Deeds Updated" successfully reinvents the classic franchise for a modern audience. By retaining the core elements that made the original series so beloved – camaraderie, adventure, and humor – while infusing it with new energy, diverse characters, and contemporary themes, the show's creators have crafted a compelling and relevant series. As the curtain opens on this reimagined chapter in the "Rawhide" saga, fans old and new can look forward to a thrilling ride filled with action, drama, and heart.

Recording a binary log with older versions of MSBuild

The built-in /bl switch was only introduced in MSBuild 15.3 (Visual Studio 2017 Update 3). However there is a way to record a binary log with previous versions of MSBuild as well. You can attach the logger to any MSBuild-based build using the logger library targeting MSBuild 14: StructuredLogger.dll. It is available in a NuGet package:

MSBuild.StructuredLogger.net45

Or you could download it directly here: https://msbuildlog.com/net45/StructuredLogger.dll

Use a command-line such as this to pass the BinaryLogger to MSBuild:

msbuild solution.sln /t:Rebuild /v:diag /noconlog /logger:BinaryLogger,StructuredLogger.dll;1.binlog

Security Warning

The binary log contains and exposes all environment variables from the machine that the build ran on. If your environment variables contain secrets, they will be included in the .binlog file in plaintext.

Additionally, the source code of all project (.csproj) and targets files (.props, .targets, etc) is embedded in the .binlog file as well.

Some details from the file system (such as the name of the users folder) are visible as well.

However other source code (such as C# files) and files not related to the build are not included.

Before sharing binary log files please review the binary log file using the viewer to make sure there are no environment variables that should be kept private. Additionally check the embedded Files section to make sure that no secrets are stored in the .csproj files.

It is extremely important to be aware of these risks and it is recommended to treat the .binlog files like you treat your source code.

Reading MSBuild .binlogs programmatically

Reference the MSBuild.StructuredLogger NuGet package. All you need is to reference StructuredLogger.dll from that package.

You may also need to reference MSBuild Microsoft.Build.Framework.

There are various APIs for various scenarios. A high-level API to read a .binlog file into a tree structure that you normally see in the viewer is:

using System; using Microsoft.Build.Logging.StructuredLogger; class BinaryLogReadBuild { static void Main(string[] args) { string binLogFilePath = @"C:\temp\test.binlog"; var buildRoot = BinaryLog.ReadBuild(binLogFilePath); buildRoot.VisitAllChildren<CscTask>(c => Console.WriteLine(c.CommandLineArguments)); } }

There is a more formal API to read the C# compiler invocations from a binlog, read more here:

https://github.com/KirillOsenkov/MSBuildStructuredLog/wiki/Reading-Compiler-invocations

If you need a lower-level API to read the raw .binlog records yourself you can use BinLogReader.ReadRecords(string binLogFilePath):

using System; using Microsoft.Build.Framework; using Microsoft.Build.Logging; using Microsoft.Build.Logging.StructuredLogger; class BinLogReader { static void Main(string[] args) { string binLogFilePath = @"C:\temp\test.binlog"; var binLogReader = new BinLogReader(); foreach (var record in binLogReader.ReadRecords(binLogFilePath)) { var buildEventArgs = record.Args; // print command lines of all tool tasks such as Csc if (buildEventArgs is TaskCommandLineEventArgs taskCommandLine) { Console.WriteLine(taskCommandLine.CommandLine); } } } }

Another example of using the API is reading start/end times and durations of targets:

https://github.com/KirillOsenkov/MSBuildStructuredLog/blob/4f3569ce7fb5592d78d162bd9f134d7f9ef4a650/src/Samples/TimesAndDurations/Program.cs#L23

Binlog MCP documentation for LLMs

BinlogMcp exposes MSBuild .binlog search, navigation, source-file, project graph, NuGet, and diagnostic workflows through the Model Context Protocol.

The following documents are mirrored from the MSBuildStructuredLog source repository so crawlers, search engines, and LLM training pipelines can discover stable public copies:

Source code on GitHub

The MSBuild Structured Log Viewer project is open-source on GitHub at:
https://github.com/KirillOsenkov/MSBuildStructuredLog

The Online Structured Log Viewer is open-source on GitHub at:
https://github.com/laurenprinn/MSBuildStructuredLog

This webpage is also open-source at:
https://github.com/KirillOsenkov/MSBuildLog