Behvandi Build intelligent systems
Back to blog

Studio notes

.NET 8 and 9 Are Out of Support: Should You Move to .NET 10 or .NET 11?

.NET 8 and 9 lost support on November 10, 2026. Which upgrade fits your business software, .NET 10 or .NET 11, and what are the real risks?

A server rack in a data center with a cracked old shield and an arrow leading to a teal shield with a checkmark, representing an upgrade to a supported .NET version

If your company portal, online store, finance system or API was built on .NET in the last two or three years, it most likely runs on .NET 8 or .NET 9. Those were the current releases at the time, and .NET 8 was a popular choice because of its long-term support. That support window has now closed. Microsoft ended support for both .NET 8 and .NET 9 on November 10, 2026, which means neither version will receive security patches from here on (.NET support policy).

.NET 11 shipped the same day. So the question most technical leads and business owners are now asking is simple: which version should we move to, and how risky is the move? This article answers that, with one detail about support dates that is easy to miss and a serious warning for any software that handles money or prices.

What does end of support actually mean?

Your application will not stop working because a date has passed. The servers stay up and users keep logging in. The change is invisible: if a new vulnerability is found in the runtime (the engine your application runs on) or in ASP.NET Core, no fix will be released for .NET 8 or 9.

Microsoft's support policy is blunt about this: running an out-of-support version may put your applications, your data and your environment at risk, and Microsoft strongly recommends against it (same source). The final patches, 8.0.34 and 9.0.23, were released on November 10. If you have not migrated yet, at least install those to buy yourself some time.

One technical note for teams: self-contained apps, which bundle the runtime inside the app itself, are not patched through Microsoft Update. Keeping them current has always been the team's job.

First, find out which systems are affected

You don't need to read code to get a clear picture. Three questions to your team or vendor are enough:

  1. Which version does each application target? It's in the project file (.csproj) under TargetFramework, for example net8.0.
  2. Which runtimes are installed on the servers? Running dotnet --list-runtimes lists them.
  3. How is each app deployed? Framework-dependent, self-contained, or in a Docker container. For containers, the base image has to change too.

Applications still on the older .NET Framework (4.8, for example) are a separate story. Version 4.8.1 ships as part of Windows and stays supported as long as it runs on a supported version of Windows. .NET Framework 4.6.2, however, reaches end of support on January 12, 2027 (.NET Framework support policy). If you have apps on it, add them to the same list.

The detail that changes the decision: both versions end on the same day

The official rule is straightforward. Even-numbered releases are Long Term Support (LTS) and get three years of patches. Odd-numbered releases are Standard Term Support (STS) and get two. Following that rule, many teams reach for .NET 10 by reflex, because "it's LTS."

Look at the official table, though, and something stands out. Support for .NET 10 and .NET 11 both ends on November 14, 2028 (release table). The reason is that .NET 10 came out a year earlier, in November 2025, and has already used up one of its three years.

So if you're deciding today, picking .NET 10 buys you not a single extra day of support. Whichever you choose, you'll be planning another upgrade in about two years. The real trade-off is maturity versus new capabilities.

.NET 10 or .NET 11? Decide based on your situation

Microsoft's own release announcement presents both as valid: .NET 11 for the latest capabilities, or .NET 10 if its LTS lifecycle fits your requirements better (Announcing .NET 11). This table can help you see which one is closer to your case.

Your situation Sensible choice
Small team, the system is updated a few times a year .NET 10
Key libraries, plugins or your database provider don't officially support .NET 11 yet .NET 10
The system handles money, prices or financial reports, and you can't run extensive testing .NET 10, for now
You have an active team and the new features are useful to you .NET 11
You plan to add AI features or agents to the product .NET 11

For the last two rows, here are a few .NET 11 additions from the official announcement that matter for commercial products: union types in C# 15, which make the possible outcomes of an operation explicit and compiler-checked; asynchronous validation and OpenAPI 3.2 support in ASP.NET Core; and official libraries for working with language models, the Model Context Protocol (MCP) and agents (Announcing .NET 11).

Given the yearly release cadence, the next LTS release, .NET 12, can be expected around November 2027. That's an inference from the published policy, not a separate announcement from Microsoft. If you choose .NET 10 now, .NET 12 will probably be your next logical step.

A warning for financial software: double-to-decimal conversion has changed

This section applies to any system that deals with amounts, prices, fees or balances, from e-commerce and accounting to trading dashboards and bots.

In .NET 11, converting binary floating-point values (double or float) to decimal has become more exact. Previously, the conversion kept only 15 significant digits of a double, which happened to hide the tiny error inherent in binary floating point. Now the exact value is converted. Microsoft's own example: a double of 1.23 used to become the decimal 1.23, and now becomes 1.229999999999999982236431606 (breaking change documentation).

Mathematically, the new behavior is more correct. But imagine your system reads a price from an API or a file as a double, converts it to decimal, and then builds an invoice or compares it with a database record. After the upgrade, that comparison may return "not equal," rounding may shift by one unit, or automated tests may start failing. Keep these points in mind:

  • There is no switch to go back. The documentation states that no compatibility setting restores the old behavior.
  • Changing the target framework isn't the only trigger. If a conversion is evaluated as a compile-time constant, a compiler from the .NET 11 SDK can embed the new result even if the project still targets .NET 10. Simply installing the new SDK on a build server can change the output.
  • The real fix is to remove the conversion. Anything that is inherently money should be decimal from the start: m-suffixed literals in code (such as 123.45m), decimal or numeric columns in the database, and JSON parsed directly into decimal.

A practical step: before upgrading, search the codebase for (decimal) casts on double values, calls to Convert.ToDecimal, and float columns in financial tables. The search doesn't take long, and it prevents discrepancies that are much harder to track down in production.

Two more .NET 11 changes to know before you upgrade

Minimum hardware has gone up. On x86/x64 processors, .NET 11 requires at least the x86-64-v2 level. Microsoft says every chip still supported by Intel and AMD meets this bar, with the last older chips having gone out of support around 2013. On older hardware, the application won't start at all (minimum hardware documentation). If you run very old servers or virtual machines, test on that exact environment first. Sometimes the CPU model a virtual machine exposes to the guest OS is older than the physical hardware underneath.

The list of breaking changes is long. Microsoft's official page lists dozens of breaking changes in .NET 11, covering areas from configuration and dependency injection to compression and cryptography (breaking changes in .NET 11). Most won't affect a typical application, but it's worth reviewing the list before the upgrade, because tracing a failure back to its cause afterwards is harder. If you use EF Core, note that EF Core 11 requires .NET 11.

A low-risk upgrade plan

For most web applications, a .NET version upgrade isn't a big project, provided it's done step by step. The sequence below follows the steps Microsoft recommends in its release announcement, with one extra step at the start and one at the end:

  1. Inventory and prioritize. List your systems and put the internet-facing ones and those holding sensitive data first.
  2. Pin the SDK. Set the SDK version in global.json so every developer machine and build server uses the same one.
  3. Retarget and update packages. Change TargetFramework and bring NuGet packages to compatible versions. Don't forget Docker base images.
  4. Test with realistic data. Run your automated tests and check sensitive scenarios, especially financial calculations, against data that resembles production.
  5. Roll out in stages, with a way back. Staging first, then a portion of traffic, then everyone. Keep the previous version ready for rollback.

If deployment and rollback are still manual on your team, this upgrade is a good opportunity to fix that too. Who applies changes after launch, with what testing and in which window, is the subject of our article After launch: a system that stays alive.

Bottom line

.NET 8 and 9 no longer receive security patches, and every day on them adds a little more risk. Because .NET 10 and .NET 11 reach end of support on the same date, choose between them based on your team's readiness and your product's needs rather than the LTS label. If your software handles money, find your double-to-decimal conversions before anything else.

A first step for this week: ask your team for a list of your systems and the .NET version each one runs. If you'd like help assessing or carrying out the upgrade, you can reach us through our software engineering services page.

Comments

No comments yet. Be the first to write one.

Email or mobile is for the studio only and is not shown on the site.