domains / families / devops / directory-build-organization

directory-build-organization

separate

USE ONLY for (1) two or more projects with repeated MSBuild policy, targets, or package versions, or (2) an existing Directory.Build.props/targets/rsp hierarchy with an import, placement, or layering defect. A one-project repo without an existing Directory.Build file is outside scope; do not load this skill. Covers centralizing shared policy and targets, Directory.Packages.props across projects, parent hierarchy/import structure, props-versus-targets placement, and folder/project exceptions. An existing hierarchy defect remains in scope when only one project is affected. For property value or condition semantics use property-patterns. Exclude legacy-to-SDK migration and non-MSBuild systems.

When to use

• two or more projects with repeated MSBuild policy
• existing Directory.Build.props/targets/rsp hierarchy with import defect
• centralizing shared policy and targets
• Directory.Packages.props across projects
• parent hierarchy/import structure
• props-versus-targets placement
• folder/project exceptions
• existing hierarchy defect affecting one project

When not to use

• one-project repo without an existing Directory.Build file
• property value or condition semantics
• legacy-to-SDK migration
• non-MSBuild systems

Skill page

Source