sdk-style-conversion

Convert legacy .NET projects to SDK-style format without changing target frameworks.

19|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill sdk-style-conversion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdk-style-conversion
Source: https://github.com/microsoft/upgrade-agent-plugins/tree/main/plugins/upgrade-agent/extenders/upgrade-dotnet/upgrade/skills/scenarios/sdk-style-conversion
Command: npx skills add https://github.com/microsoft/upgrade-agent-plugins --skill sdk-style-conversion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the need to modernize legacy .NET projects by converting them to the SDK-style format, enhancing project file management and compatibility.

Core Features & Use Cases

  • Legacy Project Conversion: Converts existing .NET projects to the SDK-style format without altering target frameworks.
  • Modernization: Streamlines project files and modernizes project structure for better long-term maintainability.
  • Use Case: If you are looking to upgrade a legacy .NET application and want to modernize its project structure for better tooling and maintainability, this Skill is designed for you.

Quick Start

Run the skill with the command 'convert-to-sdk-style <path-to-project>'.

Frequently Asked Questions about sdk-style-conversion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a legacy .NET project to SDK-style format?

You can convert a legacy .NET project to SDK-style format by running the conversion script with your project path. This modernizes the project file structure without changing the target framework.

What is SDK-style csproj format and why should I use it?

SDK-style csproj format is a streamlined way to define .NET projects. You should use it to modernize legacy project files, improving tooling compatibility and long-term maintainability.

Does converting to SDK-style format change my target framework?

No, converting to SDK-style format does not change your target framework. The transformation focuses solely on modernizing the project file structure while preserving existing framework targets.

Can I use this .NET project conversion for modernizing large legacy applications?

Yes, you can use this .NET project conversion to modernize large legacy applications. It parses your csproj files and applies SDK-style transformations to streamline project management.

What are the limitations of automated csproj file conversion?

Automated csproj file conversion focuses on applying SDK-style transformations without altering target frameworks. It improves tooling compatibility but requires parsing existing legacy project files accurately.

What's the best way to modernize .NET project files for better tooling compatibility?

The best way to modernize .NET project files for better tooling compatibility is converting them to the SDK-style format. This streamlines project structure and enhances maintainability without changing target frameworks.