OSSeva Blog
MigrationUpgrade to .NET 10 or Stay on .NET 8: Migration Options for Unsupported .NET
Migration options for unsupported .NET
Upgrade to .NET 10 wherever the application can move, and cover the rest with third-party patches while it does. .NET 8 and .NET 9 ended on 10 November 2026, so there are four routes: upgrade to .NET 10, move to .NET 11, stay on .NET 8 or 9 with patches from a provider, or run unpatched. Decide per application, not per estate. The offer for the stay route is .NET 8 extended support.
| Route | Microsoft support | Choose it when |
|---|---|---|
| Upgrade to .NET 10 (LTS) | Until 14 November 2028 | The default. Dependencies support it and tests exist |
| Move to .NET 11 (STS) | Until 14 November 2028 | You want its features. It ends the same day as .NET 10 |
| Stay on .NET 8 or 9, patched by a provider | None; fixes come from the provider | A dependency, a validation cycle or a change freeze blocks the move |
| Stay unpatched | None | Isolated workloads with no external exposure and a documented risk acceptance |
Dates: Microsoft's .NET support policy, read 17 November 2026. .NET 9 is not a route: it ended on the same day as .NET 8.
Running .NET in production? OSSeva patches and supports it, end-of-life versions included.
.NET extended support: what is coveredHow to decide, per application
Ask five questions in order; the first "no" tells you the route.
- Do all NuGet packages and vendor SDKs support .NET 10? If not, the slowest dependency sets your date, and a patched .NET 8 covers the gap.
- Is the application on Windows-only surface? WCF client code, System.Web shims and Windows Forms or WPF interop are where a straight upgrade stops being simple. The .NET 8 to .NET 10 upgrade guide lists the breaking changes.
- Is it self-contained or single-file? Each such app carries its own runtime and needs its own rebuild and redeploy.
- Does a validation or certification cycle have to re-run? Common in healthcare and finance; patched .NET 8 holds the line while it does.
- Will the application be retired soon? If the date is near and the exposure is low, patches until retirement can cost less than the move.
Upgrade to .NET 10 or .NET 11?
Take .NET 10 unless you need something .NET 11 adds. .NET 10 is the LTS release; .NET 11 shipped on 10 November 2026 as STS. Under Microsoft's two-year STS window both end on 14 November 2028, so .NET 11 gives no extra time and the same second move after it. See .NET LTS vs STS.
When staying on .NET 8 is reasonable
Staying is reasonable when a third party patches it and a dated move plan exists. Without those two, it is just delay. Record the owner, the target date and who accepted the risk; auditors for PCI DSS and SOC 2 ask for exactly that. Compare what providers publish in the provider comparison, and do not buy support for an application with no move date.
What to do this week
- Install the final patches, 8.0.34 and 9.0.23, on every host that stays.
- List every 8.0 and 9.0 runtime, image and cloud app: the 15-step checklist gives the commands.
- Sort each workload into move now, move later or cannot move.
Frequently asked questions
What are my options if my .NET version is unsupported?
Upgrade to a supported version, buy patches from a third party, isolate the workload, or accept the risk in writing. Microsoft sells no extension for .NET; see why there is no ESU for .NET.
Can I skip .NET 9 and go from .NET 8 to .NET 10?
Yes, and you should. .NET 9 ended with .NET 8, and the move covers the breaking changes of both .NET 9 and .NET 10.
Is it safe to keep running .NET 8 for now?
The app keeps running, but vulnerabilities found after 10 November 2026 are not fixed by Microsoft. Safe depends on exposure and on whether someone patches it.
How long does the upgrade take?
It depends on the estate, not the version number: dependencies, Windows-only surface, test coverage and the count of self-contained apps. Count those before you set dates.
Where OSSeva fits
For the applications that land in "cannot move yet", .NET 8 extended support keeps the runtime patched while the move runs on its own schedule.
Sources
Read 17 November 2026: Microsoft .NET support policy and endoflife.date. Dates and final releases are on the .NET 8 end of life page.
Tags
Related articles
.NET 8 to .NET 10 Upgrade Guide: Breaking Changes, SDK Steps and a Test Plan
September 28, 2026SecurityDoes Microsoft Offer Extended Security Updates (ESU) for .NET?
November 17, 2026SecurityNovember 2026 Patch Tuesday: the last .NET 8 and .NET 9 updates
November 11, 2026Operations.NET 8 End of Support Checklist: What to Do Now Support Has Ended
November 4, 2026OperationsWhat to Look for in a .NET Extended Support Provider
November 17, 2026Operations.NET Framework 4.8 End of Life vs .NET 8: Why the Support Rules Differ
November 17, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?