converting-to-sdk-style Skill
Converts legacy non-SDK-style .NET project files (.csproj, .vbproj, .fsproj) to modern SDK-style format while preserving target frameworks, dependencies, and build behavior. Use when converting old-format .NET projects, migrating from packages.config to PackageReference, or modernizing project files. Also triggers for Published by microsoft in upgrade-agent-plugins.
What is converting-to-sdk-style Skill?
Converts legacy non-SDK-style .NET project files (.csproj, .vbproj, .fsproj) to modern SDK-style format while preserving target frameworks, dependencies, and build behavior. Use when converting old-format .NET projects, migrating from packages.config to PackageReference, or modernizing project files. Also triggers for Published by microsoft in upgrade-agent-plugins. 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 upgrade-agent-plugins
Technical details
- Install or run with Copy skill directory
When to use converting-to-sdk-style Skill
- Use it for developers using upgrade-agent-plugins.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/upgrade-agent-plugins
- Skill file: plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/lazy/common/converting-to-sdk-style/SKILL.md
What it does
Converts legacy non-SDK-style .NET project files (.csproj, .vbproj, .fsproj) to modern SDK-style format while preserving target frameworks, dependencies, and build behavior. Use when converting old-format .NET projects, migrating from packages.config to PackageReference, or modernizing project files. Also triggers for
Skill instructions
SDK Style Conversion Overview Guide the step-by-step conversion of legacy (non SDK-style) project files to SDK-style while preserving existing target frameworks, behavior, and build output. This is a structural-only conversion — no target framework changes or functional refactors. Hard Constraints - Do not change, add, remove, or upgrade TargetFramework/TargetFrameworks values — this conversion is format-only, not an upgrade - Do not introduce new package versions unrelated to conversion — package drift causes subtle runtime issues - Only convert the project format using the provided tools and fix build issues directly caused by the conversion Available Tools - Project ordering tool: Use a tool capability to obtain the topological (dependency) order. Do not hand-compute and stop if unsuccessful - SDK style conversion tool: Use the dedicated conversion tool for each project. Do not manually rewrite XML and stop if unsuccessful Workflow Execution Use appropriate tools (not direct file re
Explore related resources
Frequently asked questions
What is converting-to-sdk-style?
converting-to-sdk-style is a open-source AI agent skill with Copy skill directory. Converts legacy non-SDK-style .NET project files (.csproj, .vbproj, .fsproj) to modern SDK-style format while preserving target frameworks, dependencies, and build behavior.
Who is converting-to-sdk-style best for?
converting-to-sdk-style is best for reusing agent instructions, scripts, and references.
How do I install converting-to-sdk-style?
Install or run converting-to-sdk-style using Copy skill directory. Check converting-to-sdk-style for the latest setup command.
Is converting-to-sdk-style actively maintained?
converting-to-sdk-style may need a closer maintenance check before production use.
Auto-fetched from GitHub.
