directory-build-organization Skill

Source

• Creator: microsoft
• Repository: microsoft/testfx
• Skill file: .agents/skills/directory-build-organization/SKILL.md

What it does

Guide for organizing MSBuild infrastructure with Directory.Build.props, Directory.Build.targets, Directory.Packages.props, and Directory.Build.rsp. USE FOR: structuring multi-project repos, centralizing build settings, implementing NuGet Central Package Management (CPM) with ManagePackageVersionsCentrally, consolidatin

Skill instructions

Organizing Build Infrastructure with Directory.Build Files Directory.Build.props vs Directory.Build.targets Understanding which file to use is critical. They differ in when they are imported during evaluation: Evaluation order: Directory.Build.props → SDK .props → YourProject.csproj → SDK .targets → Directory.Build.targets | Use .props for | Use .targets for | |---|---| | Setting property defaults | Custom build targets | | Common item definitions | Late-bound property overrides | | Properties projects can override | Post-build steps | | Assembly/package metadata | Conditional logic on final values | | Analyzer PackageReferences | Targets that depend on SDK-defined properties | Rule of thumb: Properties and items go in .props. Custom targets and late-bound logic go in .targets. Because .props is imported before the project file, the project can override any value set there. Because .targets is imported after everything, it gets the final say—but projects cannot override .targets values