migrate-dotnet10-to-dotnet11

Migrate .NET 10 projects to .NET 11 by updating target frameworks and resolving breaking changes.

5.1k|377|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/dotnet/skills --skill migrate-dotnet10-to-dotnet11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-dotnet10-to-dotnet11
Source: https://github.com/dotnet/skills/tree/main/plugins/dotnet-upgrade/skills/migrate-dotnet10-to-dotnet11
Command: npx skills add https://github.com/dotnet/skills --skill migrate-dotnet10-to-dotnet11

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex process of migrating .NET 10 projects to .NET 11, ensuring all breaking changes are addressed and the project builds and runs correctly.

Core Features & Use Cases

  • Target Framework Migration: Updates project files to target net11.0.
  • Dependency Updates: Upgrades relevant NuGet packages to .NET 11 compatible versions.
  • Breaking Change Resolution: Systematically fixes compilation errors and behavioral changes introduced in .NET 11, C# 15, and related libraries like EF Core.
  • Infrastructure Updates: Modifies Dockerfiles and CI/CD pipelines for .NET 11 compatibility.
  • Use Case: You have a critical .NET 10 application that needs to be upgraded to leverage the latest features and security updates in .NET 11. This Skill will guide you through the entire upgrade process, from updating the target framework to resolving subtle runtime behavioral changes.

Quick Start

Use the migrate-dotnet10-to-dotnet11 skill to upgrade the project located at '/path/to/your/project.csproj'.

Frequently Asked Questions about migrate-dotnet10-to-dotnet11

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

FAQPage Schema
How do I upgrade my .NET 10 project to .NET 11?

Migrating .NET 10 to .NET 11 involves updating the target framework to net11.0, upgrading NuGet packages, and resolving C# 15 compiler errors. You must also address behavioral changes in core libraries, EF Core, and cryptography, while updating Dockerfiles and CI/CD pipelines.

What breaking changes do I need to fix when migrating to .NET 11?

When migrating to .NET 11, you must resolve breaking changes across core libraries, EF Core, cryptography, and the JIT compiler. Additionally, you need to fix C# 15 compilation errors and adapt to .NET 11 runtime behavioral changes to ensure a clean build and functional application.

Does migrating to .NET 11 require updating my Dockerfiles and CI/CD pipelines?

Yes, migrating to .NET 11 requires updating your Dockerfiles and CI/CD pipelines. Beyond changing the project target framework to net11.0, your infrastructure must be modified to support the .NET 11 SDK and runtime environment to ensure successful deployments.

How do I resolve C# 15 compiler errors during a .NET 11 upgrade?

Resolving C# 15 compiler errors during a .NET 11 upgrade requires systematically applying fixes for breaking changes introduced in the new language version. You must update your codebase to align with C# 15 syntax and rules while upgrading related NuGet packages to compatible versions.

What is the best way to handle EF Core breaking changes in .NET 11?

Handling EF Core breaking changes in .NET 11 involves systematically applying fixes for library updates and runtime behavioral changes. Upgrading your relevant NuGet packages to .NET 11 compatible versions ensures your Entity Framework Core implementation builds cleanly and functions correctly.