migrate-dotnet10-to-dotnet11
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
npx skills add dotnet/skills --skill migrate-dotnet10-to-dotnet11 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# .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 | Input | Required | Description | |-------|----------|-------------| | Project or sol
- When to Use
- When Not to Use
- Inputs
- Workflow
- Step 1: Assess the project
- Step 2: Update the Target Framework
- Step 3: Fix source-breaking and compilation changes
- Step 4: Address behavioral changes
- Step 5: Update infrastructure
- Step 6: Verify
- Reference Documents
What does the migrate-dotnet10-to-dotnet11 skill do?
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
How do I install it?
Run `npx skills add dotnet/skills --skill migrate-dotnet10-to-dotnet11 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dotnet/skills, a repository with 4,927 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.