.NET Releases

How to upgrade from .NET 8 to .NET 10 or .NET 11: a step-by-step guide

.NET 8 and .NET 9 reached end of support on 10 November 2026, so apps on them no longer get security fixes. This guide helps you choose between .NET 10 (LTS) and .NET 11 (STS), then walks through the upgrade: SDK, target framework, packages, breaking changes, Docker images, CI pipelines and hosting.

Why you should upgrade now From the source

Microsoft ended support for .NET 8 (LTS) and .NET 9 (STS) on 10 November 2026. Their last updates were 8.0.34 and 9.0.23. From now on they get no security fixes, and security scanners and auditors will flag them.

Two supported versions remain, and both are supported until 14 November 2028: .NET 10, an LTS release from November 2025, and .NET 11, an STS release from 10 November 2026.

At a glance · .NET release

8.0

Why you should upgrade now.NET 10 or .NET 11?Before you startStep by stepBreaking changes to checkUpdate Docker, CI and hostingAfter the upgrade

.NET 10 or .NET 11? Analysis

  • Pick .NET 10 if you want the fewest upgrades: it is LTS, it has been in production for a year, and almost every library supports it.
  • Pick .NET 11 if you want C# 15 (union types, closed hierarchies), the faster CLI and the newest ASP.NET Core and EF Core features. You will then upgrade to .NET 12 in a year or two.
  • Because both end on the same day, there is no support-length reason to prefer .NET 10 right now. The difference is library readiness and how much change your team wants.
  • Moving straight from .NET 8 to .NET 11 is fine; you do not need to stop at .NET 9 or .NET 10 first, but you must review the breaking changes of every version you skip.

Before you start Analysis

  • List every project, its target framework and the NuGet packages it uses. Check that each third-party package has a version for your target.
  • Make sure your tests run and pass on .NET 8 first, so you can tell upgrade problems from old ones.
  • Note where the app runs: Docker image, App Service or Functions runtime stack, IIS hosting bundle or Linux packages, and the SDK version on your build agents.
  • Work on a branch and upgrade one small service first.

Step by step From the source

  • Install the .NET 10 or .NET 11 SDK, and Visual Studio 2026 if you use Visual Studio. Run dotnet --list-sdks to check.
  • If the repository has a global.json, change its SDK version to the new one, or the old SDK keeps being used.
  • In each project file, change TargetFramework from net8.0 to net10.0 or net11.0. If you use a Directory.Build.props file, change it there once.
  • Update every Microsoft package to the matching major version: for example Microsoft.AspNetCore.* and Microsoft.EntityFrameworkCore.* version 10.x for .NET 10 or 11.x for .NET 11. Update the dotnet-ef tool to the same version.
  • Update third-party packages to versions that support your target.
  • Run dotnet build and fix errors, then read the new warnings: obsolete APIs usually warn before they are removed.
  • Run your unit and integration tests, then test the app by hand, especially sign-in, file uploads, date handling and background jobs.
  • Commit, deploy to a test environment, watch logs and metrics, then deploy to production.

Breaking changes to check From the source

Read the official breaking-change lists for every version you skip: .NET 9, .NET 10 and, if you target it, .NET 11. For .NET 11, these are the changes general apps are most likely to notice:

  • Math.Round and MathF.Round now return correctly rounded results, and decimal and BigInteger conversions from floating point are correctly rounded.
  • DateOnly and TimeOnly TryParse methods throw for invalid input.
  • Reading ZIP entries validates CRC32, and TAR readers verify header checksums, so corrupt archives that used to load now fail.
  • IHost.RunAsync and IHost.StopAsync throw when a BackgroundService fails, and disposing a DI scope aggregates exceptions.
  • An empty string in a later configuration provider now overrides earlier providers.
  • Named mutexes default to user scope on Unix.
  • Floating-point conversions to small integer types now saturate.
  • The minimum hardware requirements were raised.
  • EF Core 11: UseSqlServer assumes SQL Server compatibility level 160 by default. Set the level explicitly if your database is older.
  • ASP.NET Core has its own list of breaking changes for version 11.

Update Docker, CI and hosting From the source

  • Docker: change base images from the 8.0 tags to 10.0 or 11.0, for example mcr.microsoft.com/dotnet/sdk:11.0 for the build stage and mcr.microsoft.com/dotnet/aspnet:11.0 for the runtime stage.
  • GitHub Actions: set dotnet-version to 10.0.x or 11.0.x in actions/setup-dotnet. Azure Pipelines: update the UseDotNet task version.
  • Azure App Service and Azure Functions: change the runtime stack in the configuration, then redeploy. Functions apps must use the isolated worker model.
  • IIS: install the ASP.NET Core Hosting Bundle for the new version on every server before deploying.
  • Linux servers: install the new runtime packages and remove the old ones once nothing uses them.

After the upgrade Analysis

Compare response times, memory and error rates with the old version for a few days. Most apps get faster without code changes, but a slow query or a changed default shows up here first.

Then plan the next step: on .NET 10 you can stay until November 2028; on .NET 11, plan the move to .NET 12 when it is released. Our .NET release dates page lists the support dates for every version.

Which .NET versions are still supported? See .NET release dates and end of support for every version.

Sources and further reading

Original: “Announcing .NET 11 (upgrade guidance)”, .NET Blog, published 10 Nov 2026, retrieved 14 Nov 2026. This article was generated from the official source using our structured templates and passed automated quality checks. Spotted a mistake? See our corrections policy.