resolve-project-references

Explain ResolveProjectReferences wait time in MSBuild Target Performance Summary.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill resolve-project-references-1k-off
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-project-references
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/resolve-project-references
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill resolve-project-references-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents developers from wasting time optimizing ResolveProjectReferences when the reported time is largely wall-clock waiting for dependent project builds rather than the target doing real CPU work.

Core Features & Use Cases

  • Explains the misleading metric: Clarifies that ResolveProjectReferences time in the Target Performance Summary reflects dependency build wait time, not direct task execution.
  • Guides correct investigation: Redirects optimization efforts to the Task Performance Summary to identify true bottlenecks (e.g., Csc, ResolveAssemblyReference, Copy).
  • Improves analysis workflow: Helps users validate assumptions by checking that ResolveProjectReferences is truly the top target and that a performance summary was captured from a diagnostic build log/binlog.

Quick Start

Ask your agent to analyze your diagnostic build binlog’s Target Performance Summary and tell you whether ResolveProjectReferences is a misleading wait-time bottleneck and what Task Performance Summary items likely represent the real bottleneck.

Frequently Asked Questions about resolve-project-references

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why is ResolveProjectReferences the most expensive target in my MSBuild performance summary?

ResolveProjectReferences appears expensive because it reflects wall-clock wait time for dependency builds, not direct CPU work. Check the Task Performance Summary self-time to find actual bottleneck tasks like Csc or Copy.

How do I find the real build bottleneck in an MSBuild binlog?

To find the real bottleneck in an MSBuild binlog, review the Task Performance Summary self-time instead of target timings. This redirects optimization to actual bottleneck tasks like Csc or ResolveAssemblyReference.

How do I optimize ResolveProjectReferences in MSBuild?

Do not optimize ResolveProjectReferences directly. The reported time is dependency build wait behavior. Redirect optimization efforts to the Task Performance Summary to select actual bottleneck tasks.

Does ResolveProjectReferences time include waiting for dependent project builds?

Yes, ResolveProjectReferences time includes waiting for dependent project builds. The target performance metric reflects dependency build wait behavior rather than direct task execution work.

When should I investigate Task Performance Summary self-time instead of Target Performance Summary?

Investigate Task Performance Summary self-time when ResolveProjectReferences is the top target in MSBuild diagnostics. This ensures you optimize actual CPU work instead of misleading dependency wait times.