migrate-dotnet9-to-dotnet10
Migrate a .NET 9 project or solution to .NET 10 and resolve all breaking changes. USE FOR: upgrading TargetFramework from net9.0 to net10.0, fixing build errors after updating the .NET 10 SDK, resolving source and behavioral changes in .NET 10 / C# 14 / ASP.NET Core 10 / EF Core 10, updating Dockerfiles for Debian-to-Ubuntu base images, resolving obsoletion warnings (SYSLIB0058-SYSLIB0062), adapting to SDK/NuGet changes (NU1510, PrunePackageReference), migrating System.Linq.Async to built-in AsyncEnumerable, fixing OpenApi v2 API changes, cryptography renames, and C# 14 compiler changes (field
npx skills add dotnet/skills --skill migrate-dotnet9-to-dotnet10 --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 9 → .NET 10 Migration Migrate a .NET 9 project or solution to .NET 10, systematically resolving all breaking changes. The outcome is a project targeting `net10.0` that builds cleanly, passes tests, and accounts for every behavioral, source-incompatible, and binary-incompatible change introduced in the .NET 10 release. ## When to Use - Upgrading `TargetFramework` from `net9.0` to `net10.0` - Resolving build errors or new warnings after updating the .NET 10 SDK - Adapting to behavioral changes in .NET 10 runtime, ASP.NET Core 10, or EF Core 10 - Updating CI/CD pipelines, Dockerfiles, or deployment scripts for .NET 10 - Migrating from the community `System.Linq.Async` package to the built-in `System.Linq.AsyncEnumerable` ## When Not to Use - The project already targets `net10.0` and builds cleanly — migration is done - Upgrading from .NET 8 or earlier — use the `migrate-dotnet8-to-dotnet9` skill first to reach `net9.0`, then return to this skill for the `net9.0` → `net10.0` migration - Migrating from .NET Framework — that is a separate, larger effort - Greenfield projects that start on .NET 10 (no migration needed) ## Inputs | Input | Required | Description | |-------|---------
- When to Use
- When Not to Use
- Inputs
- Workflow
- Step 1: Assess the project
- Step 2: Update the Target Framework
- Step 3: Resolve build errors and source-incompatible changes
- Step 4: Address behavioral changes
- Step 5: Update infrastructure
- Step 6: Verify
- Reference Documents
What does the migrate-dotnet9-to-dotnet10 skill do?
Migrate a .NET 9 project or solution to .NET 10 and resolve all breaking changes. USE FOR: upgrading TargetFramework from net9.0 to net10.0, fixing build errors after updating the .NET 10 SDK, resolving source and behavioral changes in .NET 10 / C# 14 / ASP.NET Core 10 / EF Core 10, updating Dockerfiles for Debian-to-Ubuntu base images, resolving obsoletion warnings (SYSLIB0058-SYSLIB0062), adapting to SDK/NuGet changes (NU1510, PrunePackageReference), migrating System.Linq.Async to built-in AsyncEnumerable, fixing OpenApi v2 API changes, cryptography renames, and C# 14 compiler changes (field
How do I install it?
Run `npx skills add dotnet/skills --skill migrate-dotnet9-to-dotnet10 --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.