BestPaid guides · .NET
.NET 8 and .NET 9 reached end of support on November 10, 2026. Here is the upgrade checklist for .NET 10.
Microsoft shipped the last patches, 8.0.34 and 9.0.23, on November 10, 2026. From then on, a vulnerability in the runtime or ASP.NET Core stays open on every server that runs them. .NET 10 is the long-term support release, supported until November 14, 2028.
Sources: the
.NET support policy, the breaking-change lists for
.NET 9 and
.NET 10. This page is our own summary; follow the official documentation for every detail.
1. Find everything that still runs on .NET 8 or 9
- Projects: search the repositories for
<TargetFramework>net8.0, net9.0 and multi-targeting lists (TargetFrameworks), including Directory.Build.props.
- SDK pins:
global.json files that pin an 8.x or 9.x SDK.
- Containers: Dockerfiles that start
FROM mcr.microsoft.com/dotnet/aspnet:8.0, runtime:8.0, sdk:8.0 or the 9.0 tags.
- Hosting: Azure App Service and Azure Functions apps whose stack is .NET 8 or 9; Azure Functions apps still on the in-process model (separate guide).
- Servers:
dotnet --list-runtimes on each VM or IIS box shows what is installed.
2. Move the build to .NET 10
- Install the .NET 10 SDK on developer machines and build agents; update
global.json.
- Change
TargetFramework to net10.0 (one place if you use Directory.Build.props).
- Update every
Microsoft.AspNetCore.*, Microsoft.EntityFrameworkCore.* and Microsoft.Extensions.* package to its 10.x version. Mixed major versions are a common source of odd runtime errors.
- Update third-party packages; for any that never shipped a .NET 10-compatible version, find the replacement now.
- Build with warnings visible: new analyzers and obsoletion warnings point at the code most likely to break.
3. Go through the breaking changes that apply to you
Coming from .NET 8, read both lists: the .NET 9 changes and the .NET 10 changes. Two that often hit real apps when they leave .NET 8:
- BinaryFormatter no longer works in .NET 9 and later: any code or library that still serializes with it throws at runtime.
- EF Core 9 and later throws when you apply migrations while the model has changes that no migration covers (
PendingModelChangesWarning became an error). Add the missing migration instead of hiding the warning.
4. Update containers, CI and hosting
- Docker: move base images to the
10.0 tags and rebuild; check the image's OS packages your app relies on.
- CI: GitHub Actions
actions/setup-dotnet or Azure DevOps UseDotNet@2 with 10.0.x.
- Azure App Service: switch the stack to .NET 10 in the app's configuration, ideally on a staging slot first.
5. Test and roll out
- Run the full test suite on .NET 10; add smoke tests for serialization, authentication and database access, where upgrades usually bite.
- Deploy to staging, watch logs and performance, then swap to production.
- Remove the .NET 8 and 9 runtimes from servers once nothing uses them.
Microsoft's upgrade tooling (the .NET Upgrade Assistant and GitHub Copilot app modernization for .NET) can do part of the mechanical work; review every change it makes.
Many apps, little time? We upgrade .NET 6, 7, 8 and 9 apps (and .NET Framework 4.x) to .NET 10 LTS at a fixed price, one pull request per step, tests green at every step. It starts with a $490 audit and a fixed quote within 3 business days.
See the .NET 10 upgrade offer