migrate-dotnet10-to-dotnet11

Migrate .NET 10 projects to net11.0 with targeted breaking-change fixes.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill migrate-dotnet10-to-dotnet11-1k-off
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-dotnet10-to-dotnet11
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/migrate-dotnet10-to-dotnet11
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill migrate-dotnet10-to-dotnet11-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you migrate a .NET 10 project to .NET 11 by systematically resolving the build-breaking and runtime-behavior changes introduced by the .NET 11 SDK, C# 15 compiler, and key framework components.

Core Features & Use Cases

  • Framework migration workflow: updates TargetFramework to net11.0, restores packages, and runs a clean build and tests as a validation loop.
  • Breaking-change resolution by technology area: applies targeted fixes for ASP.NET Core/OpenAPI v3, EF Core 11 (including Cosmos async-only constraints), runtime/JIT constraints, compiler safe-context changes, and security-relevant cryptography behaviors.
  • Infrastructure updates: updates Dockerfiles/CI/CD references and validates hardware minimum requirements to prevent deployment-time failures.

Use Case: You update your repo SDK to a .NET 11 preview version, then your solution fails to compile and fails tests due to OpenAPI, compiler syntax, EF Core Cosmos sync I/O usage, or runtime/hardware constraints; use this Skill to drive the upgrade to a clean, tested net11.0 state.

Quick Start

Tell the Skill: "Migrate ./MySolution.sln from net10.0 to net11.0, run dotnet build and dotnet test, and fix every .NET 11 breaking change until it builds and tests cleanly."

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 net11.0 and fix build breaking changes?▼

To migrate .NET 10 to net11.0, update the TargetFramework, restore packages, and apply targeted compile and runtime fixes across the SDK, C# 15, ASP.NET Core, and EF Core until clean builds and tests pass.

Why does my EF Core Cosmos DB code fail after the .NET 11 upgrade?▼

EF Core Cosmos DB code fails after the .NET 11 upgrade due to new async-only requirements, requiring you to replace synchronous I/O usage with asynchronous calls to resolve the build-breaking changes.

What ASP.NET Core OpenAPI v3 breaking changes do I need to fix for .NET 11?▼

For .NET 11, you need to apply targeted fixes to resolve ASP.NET Core OpenAPI v3 breaking changes, updating your solution or project codebase until it compiles and tests cleanly.

Do I need to update Dockerfiles and CI infrastructure for a net11.0 migration?▼

Yes, a net11.0 migration requires updating Dockerfiles and CI/CD references, alongside validating hardware minimum constraints, to prevent deployment-time failures and ensure successful builds.

Can I use this .NET 11 migration workflow without checking external web sources?▼

Yes, the .NET 11 migration workflow operates without using external web sources, applying technology-area-specific compile and runtime fixes directly from loaded reference documents to verify clean builds.

What C# 15 compiler safe-context changes cause build failures in .NET 11?▼

C# 15 compiler safe-context changes cause build failures in .NET 11 by altering runtime and JIT constraints, requiring targeted syntax and behavioral fixes to achieve a clean tested state.