Skills

Migrate Dotnet10 To Dotnet11

Migrate a .NET 10 project or solution to .NET 11 and resolve all breaking changes.

Install

npx skills add managedcode/dotnet-skills --skill migrate-dotnet10-to-dotnet11 -g -a claude-code -y
Category
DevOps
Updated
6d ago
License
MIT
Context cost
Mediumabout 3,000 tokens
Runs scripts
No, instructions only

What it does

Migrate a .NET 10 project or solution to .NET 11 and resolve all breaking changes. This is a MIGRATION skill, use it when upgrading from .NET 10 to .NET 11, NOT for writing new programs. USE FOR: upgrading TargetFramework from net10.0 to net11.0, fixing build errors after updating the .NET 11 SDK, resolving source-breaking and behavioral changes in .NET 11 runtime, C# 15 compiler, and EF Core 11, adapting to updated minimum hardware requirements (x86-64-v2, Arm64 LSE), and updating CI/CD pipelines and Dockerfiles for .NET 11. DO NOT USE FOR: .NET Framework migrations, upgrading from .NET 9 or earlier, greenfield .NET 11 projects, or cosmetic modernization unrelated to the upgrade. NOTE: .NET 11 is in preview. Covers breaking changes through Preview 3.

.NET 10 → .NET 11 Migration

Migrate a .NET 10 project or solution to .NET 11, systematically resolving all breaking changes. The outcome is a project targeting net11.0 that builds cleanly, passes tests, and accounts for every behavioral, source-incompatible, and binary-incompatible change introduced in .NET 11.

Note: .NET 11 is currently in preview. This skill covers breaking changes documented through Preview 3.

When to Use

  • Upgrading TargetFramework from net10.0 to net11.0
  • Resolving build errors or new warnings after updating the .NET 11 SDK
  • Adapting to behavioral changes in .NET 11 runtime, ASP.NET Core 11, or EF Core 11
  • Updating CI/CD pipelines, Dockerfiles, or deployment scripts for .NET 11
  • Fixing C# 15 compiler breaking changes after SDK upgrade

When Not to Use

  • The project already targets net11.0 and builds cleanly, migration is done
  • Upgrading from .NET 9 or earlier, address the .NET 9→10 breaking changes first
  • Migrating from .NET Framework, that is a separate, larger effort
  • Greenfield projects that start on .NET 11 (no migration needed)

Inputs

InputRequiredDescription
Project or solution pathYesThe .csproj, .sln, or .slnx entry point to migrate
Build commandNoHow to build (e.g., dotnet build, a repo build script). Auto-detect if not provided
Test commandNoHow to run tests (e.g., dotnet test). Auto-detect if not provided
Project type hintsNoWhether the project uses ASP.NET Core, EF Core, Cosmos DB, etc. Auto-detect from PackageReferences and SDK attributes if not provided

Workflow

Read the whole SKILL.md on GitHub

More in DevOps