binlog-generation

Generate MSBuild binary logs for .NET build diagnostics and performance analysis.

1|Updated May 21, 2026

Search Tags:#dotnet #performance analysis #msbuild #ci debugging #build diagnostics #binary logging

Ready to run

npx skills add https://github.com/1k-off/umbraco-observability-playground --skill binlog-generation-1k-off

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: binlog-generation
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/binlog-generation
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill binlog-generation-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of diagnosing slow builds and build failures when you cannot easily see what MSBuild actually executed.

Core Features & Use Cases

Generates MSBuild binary logs (/bl): Captures a complete build execution trace you can inspect later without re-running.
Ensures unique, non-overwriting artifacts: Uses the {} placeholder (MSBuild 17.8+ / .NET 8+ required) to avoid collisions between builds.
Supports CI and local debugging workflows: Enables follow-on analysis skills like failure analysis and build performance diagnostics.

Quick Start

Run your MSBuild-based command with the binary log switch, for example: dotnet build /bl:{}.

Frequently Asked Questions about binlog-generation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I capture an MSBuild trace to diagnose a slow .NET build?▼

Capture MSBuild binary logs by adding the /bl:{filename} switch to your dotnet build or test command. This records the entire build execution trace for post-build diagnostics and performance analysis of your .NET build execution.

What is an MSBuild binary log and when do I need it?▼

An MSBuild binary log is a complete execution trace of your build process. You need it when troubleshooting build failures or performance regressions where you cannot easily see what MSBuild actually executed and require detailed post-build analysis.

Can I generate binary logs for dotnet test and dotnet publish commands?▼

Yes, binary log generation applies to dotnet build, test, pack, publish, and restore commands. It also works with direct msbuild invocations, ensuring comprehensive build diagnostics across your entire MSBuild and .NET build workflow.

How do I prevent MSBuild binary logs from overwriting each other in CI?▼

Use the /bl:{} placeholder switch to generate unique, non-overwriting binary log artifacts. This feature requires MSBuild 17.8+ or .NET 8+ and prevents file collisions during concurrent or continuous integration build workflows.

Does MSBuild binary logging work with non-MSBuild build systems?▼

No, MSBuild binary logging is exclusively for MSBuild and .NET build contexts. It cannot be used for non-MSBuild build systems, nor is it intended for analyzing existing binary logs after generation.