domains / families / devops / msbuild-modernization

msbuild-modernization

separate

Guide for modernizing and migrating MSBuild project files to SDK-style format. USE FOR: converting legacy .csproj/.vbproj with verbose XML to SDK-style, migrating packages.config to PackageReference, removing Properties/AssemblyInfo.cs in favor of auto-generation, eliminating explicit Compile Include lists via implicit globbing, consolidating shared settings into Directory.Build.props. Indicators of legacy projects: ToolsVersion attribute, an Import of Microsoft.CSharp.targets via $(MSBuildToolsPath), .csproj files over 50 lines for simple projects. DO NOT USE FOR: projects already in SDK-style format, non-.NET build systems (npm, Maven, CMake), .NET Framework projects that cannot move to SDK-style.

When to use

• converting legacy .csproj/.vbproj with verbose XML to SDK-style
• migrating packages.config to PackageReference
• removing Properties/AssemblyInfo.cs in favor of auto-generation
• eliminating explicit Compile Include lists via implicit globbing
• consolidating shared settings into Directory.Build.props

When not to use

• projects already in SDK-style format
• non-.NET build systems (npm, Maven, CMake)
• .NET Framework projects that cannot move to SDK-style

Skill page

Source