Guide for interpreting ResolveProjectReferences time in MSBuild performance summaries. Only activate in MSBuild/.NET build context. Activate when…
Misleading ResolveProjectReferences Time Prevent misguided optimization of ResolveProjectReferences by explaining that its reported time is wall-clock wait time, not CPU work. When to Use ResolveProjectReferences appears as the most expensive target in the Target Performance Summary A developer is trying to optimize ResolveProjectReferences directly Build performance analysis shows a single target consuming 50-80% of total build time When Not to Use General build performance optimization (use build-perf-diagnostics instead) The bottleneck is clearly a different target (e.g., Csc, ResolveAssemblyReference) The user has not yet captured a binlog or performance summary Inputs
don't have the plugin yet? install it then click "run inline in claude" again.