SkillsAdd

smithery.ai

dotnet-sdk-style-upgrade

Converts legacy .NET project files (.csproj, .fsproj, .vbproj) to modern SDK-style format. Use when asked to modernize, upgrade, migrate, or convert .NET projects, or when encountering non-SDK-style project files that need updating to current .NET standards.

First seen Apr 6, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

azure-upgrade Similar name
microsoft/azure-skills

Assess and upgrade Azure workloads between plans, tiers, or SKUs, or modernize Azure SDK depend…

428.3K installs
prisma-upgrade-v7 Similar name
prisma/skills

Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes.

258.1K installs
prisma-mongodb-upgrade Similar name
prisma/skills

Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path …

252.1K installs
upgrade-stripe Similar name
stripe/ai

Guide for upgrading Stripe API versions and SDKs

64.9K installs
remotion-upgrade Similar name
remotion-dev/skills

Upgrade Remotion, and related packages

57.4K installs
expo-upgrade Similar name
expo/skills

Framework (OSS). Guidelines for upgrading Expo SDK versions and fixing dependency issues

14.6K installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0
More metadata
author
microsoft-foundry-jumpstart
version
1.0
reference
https://learn.microsoft.com/en-us/dotnet/core/project-sdk/overview

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,131 B
  • docs SUMMARY.md 290 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Upgrading to SDK-Style Projects

Required Reference: Before proceeding, consult the .NET SDK-style project documentation for authoritative guidance on SDK-style projects.

SDK Selection Guide

Analyze project files to recommend the appropriate SDK:

Project Type SDK Indicators
Console/Library Microsoft.NET.Sdk No web/UI references
ASP.NET Core/Web API Microsoft.NET.Sdk.Web Microsoft.AspNetCore.*, Startup.cs, Controllers
Razor Class Library Microsoft.NET.Sdk.Razor .razor files, Razor components
Blazor WebAssembly Microsoft.NET.Sdk.BlazorWebAssembly Microsoft.AspNetCore.Components.WebAssembly
Worker/Background Service Microsoft.NET.Sdk.Worker IHostedService, BackgroundService
WinForms Microsoft.NET.Sdk + <UseWindowsForms> System.Windows.Forms
WPF Microsoft.NET.Sdk + <UseWPF> PresentationFramework, .xaml files
MSTest MSTest.Sdk Microsoft.VisualStudio.TestTools.UnitTesting
.NET Aspire AppHost Aspire.AppHost.Sdk Aspire orchestration project

Analysis Checklist

Before upgrading, analyze and review:

  • Project type: Console, library, web, test, desktop, or worker
  • Target framework: Current TFM and desired target (e.g., net9.0, net48)
  • Package references: Check packages.config or <Reference> with HintPath
  • Assembly references: GAC or local assemblies that need conversion
  • Conditional compilation: #if directives, DEBUG/RELEASE configurations
  • Build configurations: Custom configurations beyond Debug/Release
  • Pre/Post build events: Scripts in <PreBuildEvent> or <PostBuildEvent>
  • Custom targets/props: .targets or .props file imports
  • AssemblyInfo.cs: Attributes to migrate or auto-generate
  • Resources: .resx files, embedded resources, content files
  • Project references: Other projects in solution
  • COM references: ActiveX/COM interop dependencies
  • WCF/ASMX references: Service references requiring migration
  • Project GUIDs: Solution file references (update if changing)
  • Output paths: Custom OutputPath, IntermediateOutputPath
  • Signing: Strong name keys, delay signing settings
  • Platform target: x86, x64, AnyCPU, ARM settings

Upgrade Process

  1. Identify SDK: Analyze references and file patterns to determine SDK
  2. Create minimal project file:

``xml <Project Sdk="SELECTED_SDK"> <PropertyGroup> <TargetFramework>net9.0</TargetFramework> <Nullable>enable</Nullable> <ImplicitUsings>enable</ImplicitUsings> </PropertyGroup> </Project> ``

  1. Add OutputType if executable: <OutputType>Exe</OutputType> or <OutputType>WinExe</OutputType>
  2. Migrate PackageReferences: Convert packages.config or HintPath references
  3. Remove redundant elements: SDK-style auto-includes .cs, .resx, etc.
  4. Add desktop properties for WinForms/WPF:

``xml <UseWindowsForms>true</UseWindowsForms> <!-- or --> <UseWPF>true</UseWPF> ``

Key Differences from Legacy

  • No <Compile Include="**/*.cs" /> needed (auto-included)
  • No assembly info file needed (<GenerateAssemblyInfo>true</GenerateAssemblyInfo> default)
  • PackageReference replaces packages.config
  • No ProjectGuid, ProjectTypeGuids required
  • No explicit SDK imports needed

Validation

After upgrade, run:

dotnet build
dotnet msbuild -preprocess:output.xml  # View expanded project