.NET 8 and .NET 9 reach end of support on November 10: what to do now
On November 10, 2026, Microsoft ends support for both .NET 8 and .NET 9. Those were the newest versions of .NET between November 2023 and November 2025, so a web app, API, background service or mobile app that was built or upgraded in that window probably runs on one of them.
Nothing breaks on November 10; what stops is the flow of security fixes. This post is for owners, IT leads and product owners who did not build their apps in-house: what end of support means, how to find out what you run, and how to plan the move to .NET 10.
What “end of support” means
Microsoft’s announcement (June 29, 2026) is direct about it:
- Your app keeps running. Apps built on .NET 8 or .NET 9 continue to work after November 10.
- No more security updates. Microsoft stops releasing patches for either version. A vulnerability found after that date stays open in your app.
- No more technical support. Microsoft no longer helps with issues on these versions.
- One last patch is possible. November 10 is a Patch Tuesday, and each version may get one final update that day if there is a known critical issue.
The .NET support policy puts the risk plainly: “Your use of out-of-support .NET versions may put your applications, application data, and computing environment at risk.”
Both end on the same day because .NET 8 is a Long Term Support (LTS) release with three years of support, and .NET 9 is a Standard Term Support (STS) release, which Microsoft now supports for 24 months.
Step 1: find out what you run
You do not need to read code for this. Ask whoever maintains each app (your vendor, a freelancer or your IT team) three questions.
1. Which .NET version does the app target? Every .NET project has a project file (usually ending in .csproj) with a TargetFramework line. It looks like this:
<TargetFramework>net8.0</TargetFramework>
net8.0 means .NET 8 and net9.0 means .NET 9. Both are affected. net10.0 means the app is already on .NET 10. Mobile and Windows projects add a platform to the value, as in net9.0-android, net9.0-ios or net8.0-windows (Microsoft reference). A project with a TargetFrameworks line builds for several versions at once (more on that below); check each one.
2. Which .NET runtime is installed where the app runs? On a server or virtual machine, the command dotnet --list-runtimes lists the installed runtimes, and dotnet --info shows the SDKs and runtimes together (Microsoft guide). If the app runs in a container, the FROM line of its Dockerfile names the version, for example mcr.microsoft.com/dotnet/aspnet:8.0. On a cloud service such as Azure App Service, the .NET version is part of the app’s configuration.
3. Who owns the upgrade, and by when? Write down a name and a date, even if the date is after November 10.
Put the answers in one table: the app, what it does, its .NET version, where it runs, which shared libraries it uses, and who maintains it. That table is the first version of your upgrade plan.
Step 2: choose the target: .NET 10
Microsoft recommends .NET 10, an LTS release from November 11, 2025. Its support policy lists end of support on November 14, 2028, so an app moved to .NET 10 now keeps getting security updates until then.
Step 3: plan the upgrade
Microsoft’s upgrade guide says the only required change in the code is the TargetFramework value, for example from net8.0 to net10.0. That is where the work starts: built with the new SDK, the project reports warnings and errors that guide the remaining changes.
These are the parts to ask your team or vendor about:
- Breaking changes. Someone should check Microsoft’s list of breaking changes in .NET 10 against your app.
- Web apps and APIs. For ASP.NET Core, Microsoft has step-by-step migration guides, including .NET 8 to .NET 9 and .NET 9 to .NET 10. An app on .NET 8 needs the changes in both.
- Libraries. Ask whether every library the app uses has a version that works with .NET 10.
- Build pipelines. Continuous integration pipelines usually need only a version number change, according to Microsoft.
- Hosting. If the server has the .NET runtime installed, the .NET 10 runtime must be installed there. Containers need new version numbers in their
FROMlines. On Azure App Service, a configuration change is needed. - Tools. The .NET Upgrade Assistant and the GitHub Copilot modernization agent can automate part of the work.
- Testing. Microsoft expects large apps to need a few fixes after a major upgrade, and says to retest the app afterwards.
The effort depends on each app’s size, libraries, tests and hosting, so ask for an estimate per app once these points are checked.
When you cannot move everything at once
Some companies run several apps that share internal libraries or private NuGet packages, often kept by different teams or vendors. They do not all have to move on the same day.
Apps can move before their libraries. Microsoft’s versioning guide says an app upgraded to a newer .NET version “can reference libraries and NuGet packages that target older .NET Runtime versions.” A .NET 10 app can keep using a shared library built for net8.0.
The reverse does not work. A .NET 8 app cannot use a library built only for net10.0; the build fails with a “not compatible” error (NU1202 for NuGet packages). Moving a shared library to net10.0 alone blocks every app still on .NET 8.
Multi-targeting covers that gap. A project can build for several .NET versions at once by listing them in TargetFrameworks (plural):
<TargetFrameworks>net8.0;net10.0</TargetFrameworks>
The build produces one output per version. A NuGet package carries all of them, and NuGet picks the best match for each app (Microsoft library guidance): apps still on .NET 8 get the net8.0 build, and apps on .NET 10 get the net10.0 build. Where the code must differ, conditional compilation such as #if NET10_0_OR_GREATER keeps both paths in one code base. The .NET 10 SDK builds both targets, because each SDK can build for its own version or any lower one. If .NET Framework apps also use the library, Microsoft suggests adding a netstandard2.0 target. Applications can multi-target too, but Microsoft notes that this is more common for libraries.
It is a bridge, not a place to stay. Apps that use the net8.0 build still run on .NET 8 and lose security updates like any other, and each target must be built and tested. Remove net8.0 once the last app that needs it has moved.
If you have a .NET MAUI app
.NET MAUI is Microsoft’s cross-platform framework for native mobile and desktop apps. Its own support policy works differently because MAUI depends on outside tools such as Xcode and the Android SDK.
- MAUI 8 has been out of support since May 14, 2025.
- MAUI 9 has been out of support since May 12, 2026.
- MAUI 10 is supported until May 11, 2027.
So a MAUI app on .NET 8 or .NET 9 is already out of MAUI support. Each major MAUI version is supported for at least six months after the next one ships. For mobile apps, plan a framework update every year, not every three years.
If you cannot upgrade before November 10
This is a risk decision, not an outage. Microsoft’s support policy recommends installing the latest patch and speeding up your plans to move off the old version. Install the latest .NET 8 or .NET 9 patch, including any final update on November 10, and move apps that face the internet or handle customer data first.
Checklist
- List every .NET app (web apps, APIs, background services, mobile apps) and the libraries they share.
- Get each one’s
TargetFrameworkvalue and runtime. - Mark every app on
net8.0ornet9.0, and every MAUI app below MAUI 10. - Target .NET 10, with an owner and a date per app.
- Review breaking changes, libraries, pipelines and hosting.
- Multi-target shared libraries that must serve apps on both versions.
- Test, deploy, then remove
net8.0targets and runtimes you no longer use. - Add the next dates to your calendar: May 11, 2027 (MAUI 10) and November 14, 2028 (.NET 10).
If you are not sure what your apps run, or you want a second opinion on the plan, get in touch.
Sources
- .NET 8 and .NET 9 reach end of support (Microsoft .NET blog, June 29, 2026)
- .NET and .NET Core support policy
- .NET MAUI support policy
- Upgrade to a new .NET version
- How the .NET Runtime and SDK are versioned
- Select which .NET version to use
- Cross-platform targeting for .NET libraries
- Target frameworks in SDK-style projects
- NuGet error NU1202
- Check installed .NET versions
- Breaking changes in .NET 10
- Migrate from ASP.NET Core in .NET 8 to .NET 9
- Migrate from ASP.NET Core in .NET 9 to .NET 10