Learn what .NET 8 end of support on 10 November 2026 means, compare LTS and STS releases, and plan a safe multi-service upgrade to .NET 10.
Official support for .NET 8 ended on 10 November 2026. If your organization still runs production services on .NET 8, those services no longer receive security patches, and moving to .NET 10 is the way to get them back. This course guides you through upgrading your entire stack step by step, covering project files, breaking changes, data access, containers, and deployment automation.
Next lesson: Assess Your .NET 8 Solution Before Upgrading
Microsoft releases a new version of .NET every November. Even-numbered releases receive Long Term Support (LTS), which provides support for three years. Odd-numbered releases receive Standard Term Support (STS), which provides support for two years. Both release types undergo the same quality testing and share the same engineering standards. The only difference is the length of the support window.
Because .NET 8 (LTS) launched on 14 November 2023 and .NET 9 (STS) launched on 12 November 2024, both reached end of support on the exact same date: 10 November 2026. The final patches, 8.0.34 and 9.0.23, shipped that day.
.NET 10 (LTS) launched on 11 November 2025 and remains supported until 14 November 2028. Moving from .NET 8 to .NET 10 provides your applications with active support and patches for three full years from its initial release date.
| Version | Release Type | Release Date | End of Support Date |
|---|---|---|---|
| .NET 8 | LTS | 14 November 2023 | 10 November 2026 |
| .NET 9 | STS | 12 November 2024 | 10 November 2026 |
| .NET 10 | LTS | 11 November 2025 | 14 November 2028 |
Common Mistake: Targeting .NET 9 as an intermediate milestone. .NET 9 lost support on the same day as .NET 8, so upgrading to it gains you nothing. Target .NET 10 directly.
When a .NET release reaches end of support, Microsoft stops providing security hotfixes, reliability patches, and technical support. Existing binaries continue to run, but any vulnerability found from now on in the runtime, base class libraries, or ASP.NET Core stays unpatched in .NET 8.
For enterprise environments like the running example, Larkfield Insurance, running unpatched frameworks introduces operational and compliance risks:
Pro Tip: While the upgrade is in progress, make sure every .NET 8 service runs the final patch, 8.0.34. It closes every vulnerability fixed up to the end of support.
Microsoft released .NET 11 on 10 November 2026 at .NET Conf 2026. It is an STS release, and because STS releases now get two years of support, .NET 11 is supported until 14 November 2028, the same day as .NET 10.
So why choose .NET 10? Both give you the same support runway, but .NET 10 is the lower-risk target for an enterprise migration:
Think of LTS releases like the stops on an express train line. Riding from one LTS stop to the next keeps your teams on a predictable schedule, and you only get off when a new LTS release has proven itself.
Teams that want the newest features can still target .NET 11. The upgrade steps in this course are the same.
Upgrading enterprise applications requires a methodical sequence. Upgrading everything simultaneously often causes dependency conflicts that are difficult to isolate.
Consider the Larkfield Insurance architecture, which represents a typical enterprise estate:
Larkfield.Claims.Api: An ASP.NET Core web API using controllers, minimal API endpoints, Entity Framework Core (EF Core), and SQL Server.Larkfield.Portal: A Blazor Web App used by policyholders.Larkfield.Billing.Worker: A background worker service processing queue messages.To minimize disruption, apply upgrades in this order:
net8.0 and net10.0 using their Target Framework Moniker (TFM).Larkfield.Billing.Worker have fewer inbound dependencies and do not expose public HTTP endpoints, making them ideal low-risk starting points.Larkfield.Portal to verify client assets, routing, and UI rendering.Larkfield.Claims.Api after validating dependencies and shared data models.This course covers the complete lifecycle of moving an enterprise solution to .NET 10:
MapStaticAssets, configure native OpenAPI documents, adjust authentication redirect behavior, and update EF Core migrations.Verify the currently installed .NET SDK and runtime versions on your development environment to understand your starting baseline.
Open your terminal and run the following commands:
bashCopy
Review the output:
In the next lesson, Assess Your .NET 8 Solution Before Upgrading, you will audit your repositories, discover outdated packages, and inventory your deployment configurations.
Was this lesson helpful?