Last updated: November 10, 2026
Short answer: Microsoft support for .NET 8 (including ASP.NET Core 8 and EF Core 8) ended on November 10, 2026. .NET 8 no longer receives security patches or bug fixes. Your applications keep running, but every new vulnerability found from now on stays unpatched. The recommended path is to upgrade to .NET 10, the current long-term support (LTS) release, supported until November 2028. For most .NET 8 applications this is a manageable upgrade, not a rewrite: Three Circle estimates a few days to 2 weeks for a single well-tested application.
.NET support timeline at a glance
| Version | Release type | End of support | Status |
|---|---|---|---|
| .NET 6 | LTS | November 2024 | Unsupported |
| .NET 7 | STS | May 2024 | Unsupported |
| .NET 8 | LTS | November 10, 2026 | Ended November 10, 2026 |
| .NET 9 | STS | November 10, 2026 | Ended November 10, 2026 |
| .NET 10 | LTS | November 2028 | Recommended |
Microsoft extended support for standard-term (STS) releases to 24 months, so .NET 9 reached end of support on the same day as .NET 8. See the official Microsoft announcement: .NET 8 and .NET 9 end of support.
What “end of support” really means
- No security patches: new vulnerabilities in the runtime or ASP.NET Core will not be fixed for .NET 8.
- No bug fixes or technical support from Microsoft.
- Your app keeps running: nothing switched off on November 10, but risk grows every month.
- Compliance risk: security audits, cyber insurance and frameworks such as SOC 2, ISO 27001, HIPAA or PCI DSS usually expect supported software.
- Library support fades: NuGet packages and cloud SDKs gradually drop older versions.
Who needs to act
- Any web app, API, background service or function running on .NET 8 or .NET 9.
- Teams using Docker images based on .NET 8 or 9 tags.
- Azure App Service, Azure Functions or AWS workloads on the .NET 8 or 9 runtime.
- Desktop apps (WPF, WinForms) built on .NET 8 or 9.
Still on .NET Framework 4.x? That is a different situation. .NET Framework 4.8 continues to receive security fixes as part of Windows, but it gets no new features, and technologies such as ASP.NET WebForms cannot move to modern .NET without a migration. See our WebForms to ASP.NET Core migration guide.
How to check if your app runs on .NET 8 or .NET 9
You can confirm the version in a few minutes:
- Project file: open the .csproj and look for
<TargetFramework>net8.0</TargetFramework>ornet9.0. - Server or build agent: run
dotnet --list-runtimes. Entries such asMicrosoft.AspNetCore.App 8.0.xmean .NET 8 is installed. - Docker: check base images such as
mcr.microsoft.com/dotnet/aspnet:8.0or:9.0. - Azure App Service or Functions: check the runtime stack and version in the app’s configuration settings.
Your options
| Option | What it means | When it fits |
|---|---|---|
| Upgrade to .NET 10 (recommended) | Move to the current LTS release, supported until November 2028 | Almost every active application |
| Stay on .NET 8 temporarily | Accept unpatched risk for a short, planned period | Only with a firm upgrade date and extra security monitoring |
| Retire or replace the app | Decommission, or rebuild on a modern platform | Apps that are no longer used or need major redesign anyway |
How to upgrade from .NET 8 to .NET 10: step by step
- Inventory: list every app, service, function and container on .NET 8 or 9, with owners and hosting.
- Check dependencies: confirm your NuGet packages, ORMs, authentication libraries and third-party SDKs support .NET 10.
- Review breaking changes: read Microsoft’s breaking-change notes for .NET 9 and .NET 10, especially ASP.NET Core and EF Core.
- Update the target framework: change
net8.0tonet10.0, update the SDK in global.json and update packages such as EF Core. - Update hosting: switch Docker base images, Azure App Service or Functions runtime stacks and CI/CD build agents to .NET 10.
- Test thoroughly: run unit, integration and regression tests, plus a performance and security check.
- Deploy in stages: release to a staging environment first, then production, with a rollback plan.
How long and how much will it take?
Moving from .NET 8 to .NET 10 is usually far smaller than migrating from .NET Framework. A single, well-tested application can often be upgraded in days to a few weeks. Larger estates with many services, older libraries or limited test coverage take longer. The main cost drivers are the number of applications, outdated dependencies, missing automated tests and hosting changes. Our ASP.NET development cost guide explains typical rates.
| Situation | Typical upgrade effort |
|---|---|
| One application, up-to-date packages, good automated tests | A few days to 2 weeks |
| Several apps or services, some outdated packages | 2 to 6 weeks |
| Large estate, old libraries, limited tests | 1 to 3 months, delivered in phases |
These are typical ranges. We confirm the scope and price in a written estimate after a free assessment. Rates start from $35 per hour and projects from $1,000.
Benefits of moving to .NET 10
- Security patches and support until November 2028.
- Performance improvements across the runtime, ASP.NET Core and EF Core.
- Latest C# language features and tooling.
- Continued support from libraries, cloud platforms and hosting providers.
- A cleaner base for adding new features and AI capabilities.
Common upgrade pitfalls
- Rushing the upgrade with no time to test.
- Forgetting background services, Azure Functions or containers.
- Old NuGet packages with no .NET 10 version.
- Not updating CI/CD pipelines and build servers.
- Skipping performance and security testing after the upgrade.
Still on .NET 8 or .NET 9 after November 10? What to do now
If your applications are still on .NET 8 or .NET 9, do not panic: they keep running. Microsoft’s November 2026 servicing update is the last patch for both versions, so from December onward every newly found vulnerability stays open. Use this order to reduce risk while you upgrade:
- Install the final November 2026 update so you are on the last patched build of .NET 8 or .NET 9.
- Upgrade the highest-risk apps first: public websites and APIs, and anything handling payments, health data or personal data.
- Add extra protection in the meantime: a web application firewall, tighter network access and closer security monitoring.
- Set a firm upgrade date for every remaining app and record it for your auditors or cyber insurer.
- Upgrade to .NET 10, supported until November 2028, following the steps above.
Get help with your .NET upgrade
Three Circle is an ASP.NET development company registered in Texas and working with clients across the US. We upgrade .NET 8 and .NET 9 applications to .NET 10, migrate legacy .NET Framework and WebForms systems, and provide ongoing support. See our .NET migration services, software maintenance services, hire dedicated .NET developers or request a free upgrade assessment. Rates start from $35 per hour, and every upgrade starts with a written estimate.
Get a Free .NET Upgrade Assessment
Frequently asked questions
.NET 8 reached end of support on November 10, 2026. Microsoft no longer provides security updates or bug fixes for it.
No. It will keep running, but new security vulnerabilities will not be patched, which increases risk over time.
Upgrade to .NET 10. It is the current long-term support release, while .NET 9 reached end of support on the same day as .NET 8.
For most applications it is a manageable upgrade: update the target framework, packages and hosting, then test. Effort depends on dependencies and test coverage.
No. .NET Framework 4.8 follows a different support policy tied to Windows, but it receives no new features, so modern .NET is still recommended for active applications.
Your application keeps running, but it no longer receives security patches or bug fixes. Install the final November 2026 update, protect and monitor public-facing apps, and plan the upgrade to .NET 10 as soon as possible.
It depends on the number of applications, outdated packages and test coverage. A single well-tested application can often be upgraded in days to a few weeks. Three Circle rates start from $35 per hour, with a written estimate after a free assessment.



