What problem does it solve? Multi-project .NET repositories accumulate duplicated properties, package versions, and build logic across every .csproj file, making changes error-prone and inconsistent. This Skill guides the centralization of shared build settings into Directory.Build files so each project file contains only what is unique to it. ## Core Features & Use Cases - Centralized build settings: Move shared properties (Nullable, TreatWarningsAsErrors, metadata) into Directory.Build.props and late-bound logic into Directory.Build.targets, with correct evaluation-order guidance. - Central Package Management: Set up Directory.Packages.props with ManagePackageVersionsCentrally, PackageVersion entries, and GlobalPackageReference for repo-wide analyzers. - Multi-level hierarchies and pitfalls: Chain nested Directory.Build files with GetPathOfFileAbove, configure Directory.Build.rsp defaults, and avoid the silent failure of $(TargetFramework) property conditions in .props files. - Use Case: A solution with 20 projects each repeating the same PropertyGroup and package versions is refactored into a root Directory.Build.props, Directory.Packages.props, and src/test-level overrides, leaving each .csproj with only its TargetFramework and unique references. ## Quick Start Ask the assistant to centralize the duplicated build settings and NuGet package versions across the .csproj files in your solution using Directory.Build.props and Central Package Management.
