Analyze MSBuild binary logs to diagnose build failures.
MSBuild troubleshooting
Use only for MSBuild failure investigation, build-performance analysis, or review of existing build XML/extension contracts. A plan to convert a working legacy/non-SDK project to SDK style or migrate packages.config is a project-system migration, NOT a build-file review: do not activate, even to check scope. Framework/API upgrades are also excluded. Activate for advisory Import/Exists hook and NuGet packed-import questions even without a checkout or failed build; .csproj/.fsproj/.vbproj/.props/.targets conditions; custom-target inputs/outputs; .binlog capture/replay; failing dotnet build/restore/pack/publish or MSBuild-based test builds; slow evaluation, compilation, copying, or no-change builds; and controlled timing comparisons. Exclude SDK installation alone, C# refactoring, runtime profiling, assertions after successful builds, and non-MSBuild builds.
Related skills
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis.
Analyze an MSBuild solution, solution filter, or Build.proj that schedules multiple project files.
Building AI agents on .NET?
Managed Code builds production AI agents in C# and .NET.