Terminal
Terminal/Skill
Explains why ResolveProjectReferences looks slow in MSBuild timing reports, and points to the task that actually costs the time.
By Microsoft
Works with
npx skills add dotnet/skills --skill resolve-project-referencesPrevent misguided optimization of ResolveProjectReferences by explaining that its reported time is wall-clock wait time, not CPU work.
ResolveProjectReferences appears as the most expensive target in the Target Performance SummaryResolveProjectReferences directlybuild-perf-diagnostics instead)Csc, ResolveAssemblyReference)| Input | Required | Description |
|---|---|---|
| Build log or binlog | Yes | A diagnostic build log or binlog containing the Target Performance Summary |
Verify that ResolveProjectReferences appears as the top target in the Target Performance Summary. This is the misleading metric.
The reported time includes waiting for dependent projects to build while the MSBuild node is yielded (see dotnet/msbuild#3135). During this wait, the node may be doing useful work on other projects. The target itself does very little work.
Use the Task Performance Summary to identify the real bottleneck.
Use the binlog MCP server expensive_tasks tool to get task self-time rankings directly from the binlog.
dotnet msbuild build.binlog -noconlog -fl "-flp:v=diag;logfile=full.log;performancesummary"
grep "Task Performance Summary" -A 50 full.log
Focus on self-time of actual tasks:
build-perf-diagnostics skill (Section 2: Roslyn Analyzers)build-perf-diagnostics skill (Section 1: RAR)build-perf-diagnostics skill (Section 4: File I/O)build-parallelism skillResolveProjectReferences was not set as the optimization targetCsc, Copy, ResolveAssemblyReference) was identified as the true bottleneck