build-perf-diagnostics

To diagnose slow .NET MSBuild build times, you analyze a generated binlog file to pinpoint bottlenecks. This process identifies expensive targets, tasks, and Roslyn analyzer overhead through timeline analysis and critical path identification.

MSBuild binlog files reveal bottlenecks such as slow ResolveAssemblyReference tasks, Roslyn analyzer overhead, and serialization bottlenecks. Analyzing the binlog timeline and node utilization identifies these specific expensive targets and tasks causing delays.

You analyze a dotnet build binlog to find expensive targets by replaying it to text logs for data-driven analysis. This reconstructs the build timeline to evaluate node utilization and isolate the critical path tasks consuming the most time.

Yes, you can measure Roslyn analyzer impact on MSBuild performance using a binlog. The analysis detects analyzer overhead by evaluating task execution times within the build timeline to determine if specific analyzers are causing significant delays.

The best way to identify the critical path in a slow .NET build is through binlog timeline analysis. By replaying the binlog to text logs, you can trace task dependencies and node utilization to isolate the sequential tasks extending build duration.

Yes, you need to generate a binlog before diagnosing MSBuild performance issues. The Skill requires an attached build.binlog file as input to perform timeline analysis and detect slow targets, tasks, and analyzer overhead.