domains / families / software-engineering / msbuild

msbuild

separate

Use only for MSBuild failure investigation, build-performance analysis, or review of existing build XML/extension contracts. A plan to convert a working legacy/non-SDK project to SDK style or migrate packages.config is a project-system migration, NOT a build-file review: do not activate, even to check scope. Framework/API upgrades are also excluded. Activate for advisory Import/Exists hook and NuGet packed-import questions even without a checkout or failed build; .csproj/.fsproj/.vbproj/.props/.targets conditions; custom-target inputs/outputs; .binlog capture/replay; failing dotnet build/restore/pack/publish or MSBuild-based test builds; slow evaluation, compilation, copying, or no-change builds; and controlled timing comparisons. Exclude SDK installation alone, C# refactoring, runtime profiling, assertions after successful builds, and non-MSBuild builds.

When to use

• MSBuild failure investigation
• build-performance analysis
• review of existing build XML/extension contracts
• advisory Import/Exists hook questions
• NuGet packed-import questions
• .csproj/.fsproj/.vbproj/.props/.targets conditions
• custom-target inputs/outputs
• .binlog capture/replay

When not to use

• project-system migration
• Framework/API upgrades
• SDK installation alone
• C# refactoring
• runtime profiling
• assertions after successful builds
• non-MSBuild builds

Skill page

Source