skills.rest
ojrojas
ojrojasCOMMUNITY
Explore all skills by this author →
GitHub

resolve-project-references

Differentiate ResolveProjectReferences wall-clock time from CPU work time in MSBuild.

Updated May 28, 2026
Search Tags:#performance optimization#.NET#MSBuild#task self-time#build efficiency
One-click install
npx skills add https://github.com/ojrojas/AgentsInstructions --skill resolve-project-references-ojrojas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-project-references
Source: https://github.com/ojrojas/AgentsInstructions/tree/main/.claude/skills/dotnet-msbuild/skills/resolve-project-references
Command: npx skills add https://github.com/ojrojas/AgentsInstructions --skill resolve-project-references-ojrojas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MSBuild performance issues, particularly with 'ResolveProjectReferences', are often misoptimized. This skill guides developers to focus on real CPU work.

Core Features & Use Cases

  • Misleading Target Optimization: Clarifies why 'ResolveProjectReferences' should not be directly optimized.
  • Task Self-Time Analysis: Directs users to use task self-time data for effective performance analysis.
  • Use Case: When 'ResolveProjectReferences' appears as a major performance bottleneck in a .NET project build, this skill helps identify the true causes of slow builds and directs optimization efforts to the correct tasks.

Quick Start

Analyze the MSBuild build performance and focus optimization on the tasks indicated in the Task Performance Summary instead of 'ResolveProjectReferences'.

Frequently Asked Questions about resolve-project-references

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

FAQPage Schema
Why does ResolveProjectReferences show high wall-clock time in MSBuild but isn't the actual bottleneck?▼

ResolveProjectReferences shows high wall-clock time because it waits for child projects to build, but its actual CPU work time is minimal. The target acts as an orchestrator rather than the true source of slow .NET builds.

How do I find real MSBuild performance bottlenecks using task self-time?▼

Analyze MSBuild task self-time data to isolate actual CPU execution per task. Focus your optimization efforts on the tasks indicated in the Task Performance Summary instead of targets with high wall-clock wait times.

What is the best way to optimize .NET build efficiency when project references appear slow?▼

The best way to optimize .NET build efficiency is to redirect optimization from ResolveProjectReferences to the specific tasks consuming high CPU self-time, addressing the underlying workload rather than the project reference target itself.

Do I need to understand MSBuild build performance metrics to use this analysis approach?▼

Yes, you need familiarity with MSBuild build performance metrics and .NET build tooling. This approach targets experienced users who can differentiate between wall-clock time and CPU work time to identify true task optimizations.

What should I look at in the MSBuild Task Performance Summary to improve build times?▼

Look at the Task Performance Summary to identify tasks with high CPU self-time. These tasks represent the true performance bottlenecks in your .NET build and should be the direct targets for optimization.

Related Skills

Explore More Software Engineering Skills→
1k-off1k-off
1

binlog-generation

Generate MSBuild binary logs for .NET build diagnostics and performance analysis.

Community
Intermediate
ps-carvalhops-carvalho

performance-optimization

Profile CPU and memory usage to identify and fix performance bottlenecks.

Community
Advanced
sayedihashimisayedihashimi
2

build-perf-diagnostics

Analyze MSBuild binlogs to identify build performance bottlenecks.

Community
Advanced
ojrojasojrojas

binlog-generation

Automate MSBuild binary log generation with the /bl flag.

Community
Intermediate