In this post, I describe why you should stop using the diagnostic verbosity in MSBuild and how to use the binary log feature of MSBuild to get the same information in a more efficient way.

Meziantou's resource offers insights, tutorials, and resources for software developers and IT professionals. Readers can learn about .NET development, web technologies, and software engineering best practices. With tutorials, code samples, and articles, Meziantou provides  guidance and expertise for building scalable and reliable software solutions.

Meziantou

Using MSBuild's diagnostic verbosity can slow build times and produce hard-to-read outputs. Switching to MSBuild's binary log feature provides the same detailed information in a more efficient and structured way. This includes a smaller output size, easier searchability with tools, and less impact on build times. The post explains how to generate binary logs, read them using the MSBuildStructuredLog tool, and integrate them into a CI pipeline with GitHub Actions.

Stop using diagnostic verbosity in MSBuild

# Generating the binary log in GitHub Actions