migrate-dotnet10-to-dotnet11

Migrates .NET 10 projects to .NET 11 and resolves all breaking changes.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/D1ssolve/craft-agents --skill migrate-dotnet10-to-dotnet11-d1ssolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-dotnet10-to-dotnet11
Source: https://github.com/D1ssolve/craft-agents/tree/main/skills/migrate-dotnet10-to-dotnet11
Command: npx skills add https://github.com/D1ssolve/craft-agents --skill migrate-dotnet10-to-dotnet11-d1ssolve

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, step-by-step migration workflow that identifies which breaking changes apply to your project and fixes them, so the result builds cleanly and passes tests on net11.0. ## Core Features & Use Cases - Guided six-step migration workflow: Assess the project, update the TargetFramework to net11.0, fix compilation errors, address behavioral changes, update infrastructure (Dockerfiles, CI/CD, global.json), and verify with clean builds and tests. - Technology-aware reference loading: Loads only the relevant breaking-change references (C# compiler, core libraries, SDK/MSBuild, ASP.NET Core, EF Core, cryptography, runtime/JIT) based on detected SDK attributes, PackageReferences, and API usage. - Concrete fixes for known breaking changes: Covers C# 15 span collection expression safe-context, EF Core Cosmos sync I/O removal, SYSLIB0063 NamedPipeClientStream obsoletion, Microsoft.OpenApi v3, BackgroundService exception propagation, new minimum hardware requirements, and more. - Use Case: You updated to the .NET 11 SDK and your solution now fails to build with new C# 15 compiler errors and EF Core warnings. This Skill walks through each error, applies the documented fix, updates your Dockerfile base images to 11.0, and verifies the migration with a clean build and test run. ## Quick Start Migrate my solution at ./src/MyApp.sln from .NET 10 to .NET 11 and fix all resulting build errors and breaking 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 the TargetFramework from net10.0 to net11.0 in each .csproj, bump Microsoft package references to 11.0.x, run dotnet restore and dotnet build, then fix the resulting errors. This Skill guides that process step by step, covering compiler, runtime, EF Core, and ASP.NET Core breaking changes.

What are the breaking changes in .NET 11?

Key changes include C# 15 span collection expression safe-context rules, EF Core Cosmos sync I/O removal, NamedPipeClientStream isConnected obsoletion (SYSLIB0063), Microsoft.OpenApi v3, BackgroundService exceptions stopping the host, and new x86-64-v2 minimum hardware requirements. The Skill's references document each change with fixes.

Does this skill work for upgrading from .NET 9 or .NET Framework?

No. It only covers .NET 10 to .NET 11 migrations. Upgrading from .NET 9 or earlier requires addressing the .NET 9-to-10 breaking changes first, and .NET Framework migration is a separate, larger effort outside this Skill's scope.

Why does my build fail with SYSLIB0063 after installing the .NET 11 SDK?

The NamedPipeClientStream constructor overload accepting a bool isConnected parameter is obsoleted in .NET 11, and projects with TreatWarningsAsErrors fail to build. Remove the isConnected argument and use the new three-parameter constructor taking PipeDirection, isAsync, and SafePipeHandle.

Will .NET 11 run on my older hardware?

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

How do I fix EF Core Cosmos DB errors after upgrading to EF Core 11?

EF Core 11 fully removed synchronous I/O for the Cosmos DB provider, so calls like ToList() and SaveChanges() always throw. Convert them to async equivalents such as await ToListAsync() and await SaveChangesAsync(); there is no opt-in to restore the old behavior.