All 15 .NET CLI, SDK & Project Structure (csproj) questions
More in .NET CLI, SDK & Project Structure (csproj)
What is the difference between framework-dependent deployment (FDD) and self-contained deployment (SCD)? How do you add, remove, and list NuGet package references using the dotnet CLI? What is the difference between dotnet build, dotnet publish, and dotnet run? What are MSBuild properties and items, and how do they control the build process? What is Native AOT (Ahead-of-Time) compilation, and what are its benefits and constraints? How do project references (<ProjectReference>) differ from package references, and how do they affect build order?
Advertisement
Back to results for “.NET CLI”
.NET › .NET CLI, SDK & Project Structure (csproj)

What is Directory.Build.props, and how does it help manage shared MSBuild settings across multiple projects in a repository?

Advanced

Answer

Directory.Build.props is an MSBuild file automatically imported by every project in and below the directory it resides in, letting you centralize common properties (like LangVersion, Nullable, common package versions, or company copyright metadata) without repeating them in every individual .csproj file, reducing duplication and drift across a multi-project solution.
<!-- Directory.Build.props at repo root -->
<Project>
  <PropertyGroup>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
    <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
  </PropertyGroup>
</Project>
Real-world example A monorepo with 40 microservice projects uses a single Directory.Build.props to enforce nullable reference types and warnings-as-errors consistently across every project without editing each csproj individually.

Common follow-ups: How does Directory.Build.targets differ in import order from Directory.Build.props?;How do you override a shared property in one specific project?

Assemblies & NuGet;CI/CD Publishing & Deployment
All 15 .NET CLI, SDK & Project Structure (csproj) questions