migrate-dotnet10-to-dotnet11

Migrate .NET 10 projects to .NET 11 and resolve all breaking changes.

Updated Sep 22, 2026
One-click install
npx skills add https://github.com/bytecakelake/Nurse-Scheduler --skill migrate-dotnet10-to-dotnet11-bytecakelake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-dotnet10-to-dotnet11
Source: https://github.com/bytecakelake/Nurse-Scheduler/tree/main/.agents/plugins/dotnet-upgrade/skills/migrate-dotnet10-to-dotnet11
Command: npx skills add https://github.com/bytecakelake/Nurse-Scheduler --skill migrate-dotnet10-to-dotnet11-bytecakelake

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Upgrading a project from .NET 10 to .NET 11 introduces dozens of source-breaking, behavioral, and binary-incompatible changes across the runtime, C# 15 compiler, ASP.NET Core, and EF Core 11. This Skill provides a systematic workflow to update the target framework, fix every build error, address silent behavioral changes, and update infrastructure so the migrated project builds cleanly and passes tests. ## Core Features & Use Cases - Guided Migration Workflow: Six-step process covering project assessment, TFM update, compilation fixes, behavioral changes, infrastructure updates, and verification. - Technology-Specific References: Detailed breaking change documents for C# 15 compiler, core libraries, SDK/MSBuild, ASP.NET Core, EF Core, cryptography, and runtime/JIT, loaded only when relevant to the project. - Use Case: You updated to the .NET 11 SDK and your solution now fails with SYSLIB0063 errors, EF Core Cosmos sync I/O exceptions, and Microsoft.OpenApi compile errors. This Skill walks through each failure with concrete fixes and updates your Dockerfiles and CI/CD pipelines to .NET 11. ## Quick Start Migrate the solution at ./src/MyApp.sln from .NET 10 to .NET 11 and fix all resulting build errors and behavioral changes.

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 migrate a .NET 10 project to .NET 11?▼

Update TargetFramework from net10.0 to net11.0 in each .csproj, bump Microsoft package references to 11.0.x versions, then run dotnet restore and dotnet build. Work through the resulting errors using the breaking change references for the C# 15 compiler, core libraries, and any frameworks your project uses.

What are the breaking changes in .NET 11?▼

.NET 11 breaking changes include C# 15 span collection expression safe-context rules, NamedPipeClientStream constructor obsoletion (SYSLIB0063), EF Core Cosmos sync I/O removal, Microsoft.OpenApi v3 API changes, DSA removal on macOS, and updated minimum hardware requirements (x86-64-v2, Arm64 LSE).

Does .NET 11 run on older CPUs?▼

.NET 11 raises the x86/x64 baseline from x86-64-v1 to x86-64-v2, requiring SSE4.2, POPCNT, and related instruction sets, and Windows Arm64 now requires LSE. CPUs from roughly 2013 or later meet the new x86-64-v2 requirement; older hardware will fail to start.

Why does EF Core Cosmos throw on ToList after upgrading to .NET 11?▼

EF Core 11 fully removed synchronous I/O for the Azure Cosmos DB provider, so calls like ToList() and SaveChanges() always throw with no opt-in. Convert all synchronous calls to async equivalents such as ToListAsync() and SaveChangesAsync().

When should I not use this .NET 11 migration skill?▼

Do not use it for .NET Framework migrations, upgrades from .NET 9 or earlier (handle the .NET 9 to 10 changes first), greenfield .NET 11 projects, or projects already targeting net11.0 that build cleanly.

How do I fix Microsoft.OpenApi compile errors after upgrading to .NET 11?▼

Microsoft.AspNetCore.OpenApi in .NET 11 depends on Microsoft.OpenApi 3.x, which has breaking API changes from v2. If your code uses OpenApiDocument or OpenApiSchema types directly, follow the Microsoft.OpenApi v3 upgrade guide; integration-only usage like MapOpenApi() needs no changes.