resolve-project-references
Guide for interpreting ResolveProjectReferences time in MSBuild performance summaries. Activate when ResolveProjectReferences appears as the most expensive target and developers are trying to optimize it directly. Explains that the reported time includes wait time for dependent project builds and is misleading. Guides users to focus on task self-time instead. Do not activate for general build performance -- use build-perf-diagnostics instead.
Profile →npx skills add dotnet/skills --skill resolve-project-references --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 | Input | Required | Description | |-------|----------|-------------| | Build log or binlog | Yes | A diagnostic build log or binlog containing the Target Performance Summary | ## Workflow ### Step 1: Confirm the misleading symptom Verify that `ResolveProjectReferences` appears as the top target in the **Target** Performance Summary. This is the misleading metric. ### Step 2: Explain why it is misleading The reported time includes **waiting for dependent projects to build** whil
- When to Use
- When Not to Use
- Inputs
- Workflow
- Step 1: Confirm the misleading symptom
- Step 2: Explain why it is misleading
- Step 3: Redirect to task self-time
- Validation
dotnet msbuild build.binlog -noconlog -fl "-flp:v=diag;logfile=full.log;performancesummary" grep "Task Performance Summary" -A 50 full.log
What does the resolve-project-references skill do?
Guide for interpreting ResolveProjectReferences time in MSBuild performance summaries. Activate when ResolveProjectReferences appears as the most expensive target and developers are trying to optimize it directly. Explains that the reported time includes wait time for dependent project builds and is misleading. Guides users to focus on task self-time instead. Do not activate for general build performance -- use build-perf-diagnostics instead.
How do I install it?
Run `npx skills add dotnet/skills --skill resolve-project-references --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dotnet/skills, a repository with 4,927 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.