Microsoft announced .NET 11 on November 10, 2026. For an application that already runs on .NET 10, the better default is to stay there until a specific .NET 11 feature is worth a regression pass, and to decide on purpose which software development kit (SDK) builds it in the meantime.
.NET 10 and .NET 11 share one published end-of-support date
As of November 22, 2026, Microsoft's .NET support policy, last updated November 10, 2026, lists November 14, 2028 as the end of support for both versions. .NET 10 is a Long Term Support (LTS) release and .NET 11 is a Standard Term Support (STS) release, and each label counts from that version's own release, a year apart. On the currently published dates they have the same remaining support deadline, so an upgrade buys no supported time: either way the application has to be on a later release by that day.
Microsoft can revise these dates, so recheck the page before a budget depends on them. Our earlier article on planning a .NET 10 upgrade explains how the two support terms work.
What changes underneath an invoice total
Take a hypothetical invoice validation job. Each night it recomputes every line total from a quantity and a unit price held as a double, rounds to cents with Math.Round, and writes any mismatch with the stored total to an exception report for accounts receivable.
Two documented .NET 11 changes can move its numbers. The first is in the runtime. Microsoft's breaking-change note on Math.Round gives Math.Round(655.925, 2, MidpointRounding.AwayFromZero) as its example: earlier versions returned 655.93 and .NET 11 returns 655.92. An application that targets .NET 10 stays on the .NET 10 runtime by default and keeps the earlier result. Moved to .NET 11, the job can flag a line stored last month at 655.93 although nobody edited the invoice.
The second can reach an application that never leaves .NET 10. Converting a double to decimal now keeps more of the stored binary value, so a price held as a double can arrive in a decimal a hair off the amount it was meant to hold. While the application runs, that follows the runtime too. Constants are the exception: Microsoft's note on decimal and floating-point conversions says that when the compiler evaluates the conversion as a constant, a compiler from the .NET 11 SDK can embed the new result on a rebuild whatever framework the project targets, and that no compatibility switch brings the old conversion back. In the validation job, that is a tolerance or tax rate typed as a double literal and cast to decimal. Microsoft's fix is a decimal literal.
Neither change reaches every money calculation. Microsoft says "Most code needs no change" and lists Math.Round on a decimal as unaffected, so code that keeps amounts as decimal throughout sits outside both. Where a double is involved, we would run last month's invoices through the current build and the candidate build and give accounts receivable every total that differs, with both values, before release.
Staying on .NET 10 still means choosing an SDK
The compiler comes from the SDK on the build machine, and the project's target framework is a separate setting. Microsoft's releases and support guidance for .NET says to "Upgrade to the latest SDK version, even if it's an STS release", and the global.json documentation says that with no global.json file "the highest installed SDK version is used". Read together, they mean that where no applicable global.json is found, installing the .NET 11 SDK on a build machine makes it the default compiler for a .NET 10 project, with no commit to show for it.
We would make the choice explicit. A global.json names the SDK version the application builds with and a roll-forward policy that still accepts servicing updates, so the pin does not hold the build on an unpatched SDK. Keep both the SDK and the runtime on current servicing patches. The move to the .NET 11 SDK then happens in a reviewed commit, after the affected calculations have been checked.
Does the feature you want need the new runtime?
Entity Framework (EF) Core 11 does. Microsoft's .NET 11 announcement states "EF Core 11 requires .NET 11", and the EF Core 11 breaking changes list is part of the cost: it includes SQL Server changes that an existing database has to be checked against.
Microsoft.Extensions.AI does not. On November 22, 2026 the NuGet listing for Microsoft.Extensions.AI showed version 11.0.1 as compatible with net10.0, so a chat or document-summary feature built on that package fits an application that stays on .NET 10. The listing speaks for that one package. Any other library the feature depends on needs the same check.
How IKRC would decide for an application on .NET 10
In our .NET development work we would settle it in this order:
- Write the SDK choice into global.json.
- If the code rounds
doubleorfloatvalues or converts them todecimal, compare the current and candidate builds on the workflow that depends on them. Invoices are one case, and other applications have their own. - Name the .NET 11 feature the business wants. If there is none, or it ships as a package that runs on .NET 10, stay.
- If it is EF Core 11, review its breaking changes with whoever runs Microsoft SQL Server, and make the upgrade its own release.
Before any upgrade, reread Microsoft's list of breaking changes in .NET 11, which on November 22, 2026 still called itself "a work in progress".
Related Reading
.NET 8 and .NET 9 end of support and NuGet Audit in .NET 10 cover the move to .NET 10 that came before this decision.