binlog-failure-analysis

Analyze .NET MSBuild binary logs to diagnose build failures.

5|4|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/ViktorHofer/dotnet-skills --skill binlog-failure-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: binlog-failure-analysis
Source: https://github.com/ViktorHofer/dotnet-skills/tree/main/msbuild-skills/skills/binlog-failure-analysis
Command: npx skills add https://github.com/ViktorHofer/dotnet-skills --skill binlog-failure-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic and deep analysis of .NET/MSBuild build failures, preventing users from misinterpreting console output and ensuring efficient problem resolution.

Core Features & Use Cases

  • Mandatory Failure Analysis: Ensures build failures are analyzed using binary logs before any fixes are attempted.
  • Comprehensive Diagnostics: Extracts errors, warnings, and detailed build information from binary logs.
  • Performance Profiling: Identifies slow targets, tasks, and Roslyn analyzers to optimize build times.
  • Use Case: When a dotnet build command fails with an "error CSxxxx", this skill will be invoked to analyze the generated msbuild.binlog file, pinpoint the exact cause, and suggest a solution.

Quick Start

When a build fails, re-run it with the /bl flag and then use the binlog-failure-analysis skill to load and analyze the generated log file.

Frequently Asked Questions about binlog-failure-analysis

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

FAQPage Schema
How do I diagnose obscure dotnet build failures using an MSBuild binlog?

To diagnose dotnet build failures, generate an MSBuild binlog using the `/bl` flag and parse it to extract detailed build events, pinpointing exact errors and warnings.

What does the /bl flag do in MSBuild and when do I need it?

The `/bl` flag in MSBuild generates a binary log file that records detailed build event data. You need it when a `dotnet build` fails with obscure errors, allowing systematic analysis of targets, tasks, and Roslyn analyzer issues.

How can I identify performance bottlenecks and slow targets in a dotnet build?

Identify dotnet build performance bottlenecks by analyzing the generated binary log file to profile slow targets, tasks, and Roslyn analyzers.

Can I troubleshoot Roslyn analyzer issues from a dotnet build binary log?

Yes, you can troubleshoot Roslyn analyzer issues by parsing the MSBuild binary log file. The binlog contains detailed build event data necessary for diagnosing analyzer errors and warnings within the build process.

What's the best way to find the root cause of an MSBuild error CSxxxx?

The best way to find the root cause of an MSBuild error CSxxxx is to re-run the failed build with the `/bl` flag and analyze the resulting binary log file to pinpoint the exact failure and suggest a targeted solution.