Workik.

.NET 8 to .NET 10 Migration: An Enterprise Upgrade Guide

.NET 8 End of Support: Why and When to Move to .NET 10

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


The Support Lifecycle: .NET 8, .NET 9, and .NET 10

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.

VersionRelease TypeRelease DateEnd of Support Date
.NET 8LTS14 November 202310 November 2026
.NET 9STS12 November 202410 November 2026
.NET 10LTS11 November 202514 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.


The Real Impact of Reaching End of Support

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:

  • Security compliance: Auditors for standards such as PCI DSS, SOC 2, and ISO 27001 expect you to patch known vulnerabilities, which you cannot do on unsupported software.
  • Vulnerability management: Many container scanners and dependency analyzers flag end-of-life runtimes.
  • Package ecosystem: Microsoft and community package authors align new releases with supported runtimes. Over time, you cannot consume bug fixes in third-party packages without updating the underlying framework.

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.


Why Choose .NET 10 LTS Instead of .NET 11

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:

  • It has had a full year of monthly servicing fixes.
  • Libraries, tools, and hosting platforms have had a year to add .NET 10 support.
  • EF Core 10 is an LTS release supported until 10 November 2028.
  • Moving to .NET 11 adds a third set of breaking changes on top of .NET 9 and .NET 10.

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.


Safe Upgrade Sequence for Distributed Solutions

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.
  • Shared class libraries and internal NuGet packages consumed by all three services.

To minimize disruption, apply upgrades in this order:

  1. Shared class libraries and NuGet packages: Upgrade shared libraries first. If different services upgrade on different schedules, configure your shared libraries to multi-target both net8.0 and net10.0 using their Target Framework Moniker (TFM).
  2. Standalone worker services: Services like Larkfield.Billing.Worker have fewer inbound dependencies and do not expose public HTTP endpoints, making them ideal low-risk starting points.
  3. Customer-facing web applications: Upgrade front-end portals like Larkfield.Portal to verify client assets, routing, and UI rendering.
  4. Core business APIs: Upgrade foundational services like Larkfield.Claims.Api after validating dependencies and shared data models.

The Course Roadmap

This course covers the complete lifecycle of moving an enterprise solution to .NET 10:

  • Plan the .NET 10 Upgrade: Inventory your services, review packages, check your Software Development Kit (SDK) settings, and assess your continuous integration and continuous deployment (CI/CD) pipelines.
  • Upgrade Projects and Libraries: Update project files, migrate to Central Package Management, resolve deprecations, and handle core runtime breaking changes introduced in both .NET 9 and .NET 10.
  • Upgrade ASP.NET Core and EF Core: Modernize static asset handling with MapStaticAssets, configure native OpenAPI documents, adjust authentication redirect behavior, and update EF Core migrations.
  • Ship and Stay Current: Update your Docker container images to Ubuntu 24.04 baselines, pin SDK versions in CI/CD pipelines, and establish a monthly servicing workflow.

Try It Yourself

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:

bash
Copy

Review the output:

  1. Confirm whether you have a .NET 8 SDK or a .NET 10 SDK installed.
  2. Check if multiple runtime versions are present on your machine.
  3. Identify whether your current environment has any STS runtimes, such as .NET 9, currently active.

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?