dev-dotnet-build

Diagnose MSBuild configurations and optimize .NET SDK-style project builds.

7|3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill dev-dotnet-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-dotnet-build
Source: https://github.com/eriklieben/agentic-dev-workflow/tree/main/.claude/skills/dev-dotnet-build
Command: npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill dev-dotnet-build

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill resolves complex .NET build failures, slow compilation times, and broken incremental build cycles by providing deep diagnostic capabilities for MSBuild.

Core Features & Use Cases

  • Binlog Analysis: Generate and inspect binary logs to identify property reassignments, target execution order, and task failures.
  • Build Optimization: Fix broken incremental builds and resolve MSBuild antipatterns in Directory.Build.props/targets.
  • Use Case: When a project rebuilds entirely on every run, use this skill to analyze the binlog, identify the file or target triggering the invalidation, and apply a targeted fix to restore fast incremental builds.

Quick Start

Use the dev-dotnet-build skill to generate a binary log for the current project and analyze it for build performance bottlenecks.

Frequently Asked Questions about dev-dotnet-build

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

FAQPage Schema
Why does my .NET project rebuild entirely on every run instead of using incremental builds?

Broken incremental builds in .NET are usually caused by MSBuild antipatterns or invalid file inputs triggering target invalidation. Generating and analyzing a binary log helps identify the specific file or target causing the rebuild so you can apply a targeted fix.

How do I diagnose slow MSBuild compilation times in a complex multi-project solution?

To diagnose slow MSBuild compilation, generate a binary log for your .NET SDK-style projects and inspect it to identify property reassignments, target execution order, and task failures that cause performance bottlenecks.

What is MSBuild binlog analysis and when do I need it for .NET build optimization?

MSBuild binlog analysis is the inspection of binary logs to trace property evaluations, target execution order, and task failures during .NET builds. You need it to perform deep build inspection and resolve complex compilation failures or slow performance.

Can I use this approach to fix MSBuild property evaluation issues in Directory.Build.props?

Yes, you can resolve MSBuild property evaluation issues and antipatterns in Directory.Build.props or Directory.Build.targets by inspecting the binary log to trace property reassignments and applying .NET build best practices.

What's the best way to identify which target is triggering invalidation in a broken .NET incremental build?

The best way to identify the target triggering invalidation is to generate a binary log and analyze the task execution sequence. This deep build inspection reveals the exact file or target breaking the incremental build cycle.

Does this MSBuild diagnostic method work for all .NET SDK-style projects?

Yes, this diagnostic method applies to .NET SDK-style projects, including complex multi-project solutions. It handles deep build inspection, binlog analysis, and adherence to .NET build best practices across these project types.