What problem does it solve? MSBuild build failures often produce console output that is too terse or too noisy to explain the root cause, especially in multi-project builds with cascading errors. This Skill analyzes an existing .binlog file to trace errors, warnings, properties, and target execution without manual log digging. ## Core Features & Use Cases - Structured binlog querying: Uses the binlog MCP server (Microsoft.AITools.BinlogMcp) to inspect errors, warnings, MSBuild properties, items, project evaluation data, and target execution details. - Embedded file retrieval: Reads project files (.csproj, .props, .targets) embedded in the binlog even when sources are not available on disk. - Fallback text replay: Replays the binlog to diagnostic, errors-only, and warnings-only text logs via dotnet msbuild when the MCP server is unavailable. - Use Case: A CI build fails with a vague CS0246 error across several projects. Point the Skill at the captured build.binlog to identify which project failed, which target ran, and what property values caused the failure. ## Quick Start Analyze the attached build.binlog file and explain why the MSBuild build failed, including the failing project, target, and root-cause error.
