msbuild-modernization Skill
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 implici Published by microsoft in testfx.
What is msbuild-modernization Skill?
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 implici Published by microsoft in testfx. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using testfx
Technical details
- Install or run with Copy skill directory
When to use msbuild-modernization Skill
- Use it for developers using testfx.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/testfx
- Skill file: .agents/skills/msbuild-modernization/SKILL.md
What it does
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 implici
Skill instructions
MSBuild Modernization: Legacy to SDK-style Migration Identifying Legacy vs SDK-style Projects Legacy indicators: - <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" / - Explicit file lists (<Compile Include="..." / for every .cs file) - ToolsVersion attribute on <Project element - packages.config file present - Properties\AssemblyInfo.cs with assembly-level attributes SDK-style indicators: - <Project Sdk="Microsoft.NET.Sdk" attribute on root element - Minimal content — a simple project may be 10–15 lines - No explicit file includes (implicit globbing) - <PackageReference items instead of packages.config Quick check: if a .csproj is more than 50 lines for a simple class library or console app, it is likely legacy format. xml <!-- Legacy: ~80+ lines for a simple library -- <?xml version="1.0" encoding="utf-8"? <Project ToolsVersion="15.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" <Import Project="$(MSBuildExtensionsPath)$(MSBuildToolsVersion)\Microsoft.Com
Explore related resources
Frequently asked questions
What is msbuild-modernization?
msbuild-modernization is a open-source AI agent skill with Copy skill directory. Guide for modernizing and migrating MSBuild project files to SDK-style format.
Who is msbuild-modernization best for?
msbuild-modernization is best for reusing agent instructions, scripts, and references.
How do I install msbuild-modernization?
Install or run msbuild-modernization using Copy skill directory. Check msbuild-modernization for the latest setup command.
Is msbuild-modernization actively maintained?
msbuild-modernization may need a closer maintenance check before production use.
Auto-fetched from GitHub.
