What problem does it solve? Multi-project .NET repositories accumulate duplicated properties, package versions, and build logic across every .csproj file, making updates error-prone and inconsistent. This Skill guides the centralization of shared build settings into Directory.Build files and NuGet Central Package Management. ## Core Features & Use Cases - Centralized Build Settings: Move shared properties like Nullable, TreatWarningsAsErrors, and assembly metadata into Directory.Build.props, with correct guidance on props vs targets evaluation order. - Central Package Management (CPM): Set up Directory.Packages.props with ManagePackageVersionsCentrally, PackageVersion entries, and GlobalPackageReference for repo-wide analyzers. - Multi-Level Hierarchies: Chain nested Directory.Build.props files for src/ and test/ folders using GetPathOfFileAbove, plus Directory.Build.rsp for default CLI arguments. - Pitfall Detection: Avoid the silent failure where $(TargetFramework) conditions in .props files never match for single-targeting projects. - Use Case: A solution with 20 projects each repeating the same Nullable, LangVersion, and analyzer PackageReference settings can be refactored so each .csproj contains only its TargetFramework and unique package references. ## Quick Start Ask the assistant to audit all .csproj files in the solution and centralize the duplicated properties and package versions into Directory.Build.props and Directory.Packages.props.
