.NET 8, .NET 9 and .NET Framework 4.6.2: an upgrade and a rewrite in a deal
Support for .NET 8 and .NET 9 ended on 10 November 2026, and .NET Framework 4.6.2 follows on 12 January 2027. The names are close, the work behind them is not: one is usually a contained upgrade, the other can be a platform to rewrite. What a reviewer reads, how each turns into deal terms, and what a seller can still do.
On 10 November 2026 Microsoft ended support for two versions of .NET on the same day: .NET 8, a long-term release, and .NET 9, a standard-term one. Two months later, on 12 January 2027, support ends for .NET Framework 4.6.2, the oldest 4.x version of the classic Windows framework still supported. Both carry the name .NET. For a deal they mean very different things.
This note is for owners preparing a sale, buyers reading a target and the advisors between them. It explains why one of these findings is usually contained work and the other can be a rewrite, and how each reads in a deal.
The dates
| Date | What happens | What it affects |
|---|---|---|
| 10 November 2026 | Support ends for .NET 8 (LTS) and .NET 9 (STS). .NET 11 is released the same day. | APIs, web applications and services on those two versions. |
| 12 January 2027 | Support ends for .NET Framework 4.6.2. Windows Server 2016 reaches the end of its extended support on the same day. | Older Windows business software: internal systems, portals, desktop tools. |
| 14 November 2028 | Support ends for .NET 10 (LTS) and .NET 11 (STS). | The current versions. Today's upgrade target. |
| No date announced | .NET Framework 4.7, 4.7.1, 4.7.2, 4.8 and 4.8.1 follow the lifecycle of the Windows version they run on. | Classic .NET applications on a later 4.x version. |
The modern .NET dates come from the .NET support policy (long-term releases get three years of support, standard-term releases two). The .NET Framework dates come from Microsoft's .NET Framework lifecycle page and its lifecycle FAQ: from 4.5.2 on, the framework is a component of Windows and follows the lifecycle of the Windows it runs on. The Windows Server 2016 date is on its lifecycle page. We keep all of them, with other dates that matter to owners, on our page of technology deadlines for owners. To see which of them apply to your own software, drop your project files into our stack check; nothing leaves your browser.
Two different problems under one name
Modern .NET and .NET Framework are separate platforms. A move inside either one is a different kind of work from a move between them, and a review has to say which of the three it is looking at.
Modern .NET 8 or 9 to .NET 10
Microsoft's own upgrade overview describes moves between modern versions as usually smaller in scope: mostly the target framework, the dependencies and the breaking changes between the versions crossed. That is the usual picture, not a promise. What decides the size is the list of breaking changes in .NET 10 that touch the product, third-party packages without a .NET 10 version, test coverage that can show nothing broke, and how the product is built and deployed. A product that has taken every release on time is in a much better position than one that skipped several.
.NET Framework 4.6.2 to 4.8
The lifecycle FAQ says 4.6.2 and later are compatible, in-place updates, and that applications built on earlier 4.x versions are expected to keep running without recompiling. It also notes a small number of breaking changes and a set of fixes that take effect only after retargeting. So the move to 4.8 or 4.8.1 is usually small, but it still needs a test pass in a pre-production environment, as Microsoft itself recommends. It also ties the software to Windows: because the framework is a Windows component, 4.8 is supported only as long as the Windows version under it is. And 4.8.1 is listed only for Windows Server 2022 and 2025 among server versions.
.NET Framework to modern .NET
This is the move that changes the size of a finding. Microsoft's porting overview says libraries, console tools and desktop apps often need little change, while projects that need a new app model, such as moving from ASP.NET to ASP.NET Core, need more work. Its ASP.NET migration guide calls that move non-trivial for the majority of production apps and recommends an incremental migration, part by part, for large ones. Some parts of the old framework do not exist in modern .NET at all: application domains, remoting, code access security, COM+ services and Windows Workflow Foundation. For a classic web application with years of business logic inside, price this move as a staged rewrite.
Why it reaches a deal
For modern .NET, the question is timing. A product still on .NET 8 or 9 gets no further fixes from Microsoft. It works as before, but any weakness found from now on stays without an official patch. For a deal that signs in early 2027, that is a dated item for the buyer's first months, unless the seller closes it first.
For .NET Framework, the question is depth. A finding that reads ".NET Framework 4.6.2" can mean three things: a contained move to 4.8, a Windows Server move that comes with it, or a platform the business will one day have to replace. Each has a very different cost. A buyer who prices the first and inherits the third has a problem that no version number in the appendix warned about.
What a reviewer looks at
Most of these can be answered from the code, the build files and the servers:
- Target frameworks: the target framework of every project in every solution, not only the main application. A product often mixes modern .NET services with older .NET Framework parts.
- Servers and Windows versions: which Windows Server versions run the software, and whether any of them is Windows Server 2016, which loses support on the same day as 4.6.2.
- Patch level: whether the runtime in production has taken the latest patches. The last .NET 8 patch, 8.0.34, shipped on 10 November 2026.
- App model: for classic .NET, whether the web front end is ASP.NET MVC, Web API or Web Forms, and whether the product uses WCF services, Workflow Foundation, remoting or COM+.
- Packages and tests: third-party controls and libraries without a modern .NET version, and automated tests that can show an upgrade broke nothing.
- The plan and the people: whether an upgrade is scoped, dated and staffed, and whether the people who know the old code will stay through it.
How it turns into deal terms
A modern .NET upgrade is normally a contained finding. It goes into the review with a severity, an estimate and a date. It reaches the deal as a line in the first hundred days, a condition to finish it before closing, or a disclosure with the plan. How severity is set is on our approach page.
A .NET Framework platform that will need to move to modern .NET is a different scale. It can reach the price, a holdback until a defined stage is done, or a specific disclosure the buyer accepts as known. The choice belongs to the parties and their lawyers. The reviewer gives them the facts: what runs on what, what a move takes, how long, roughly what it costs, and the risk in the meantime. Assessment and repair stay separate: the review sizes the work, and whoever does it is chosen afterward.
A hypothetical example shows the gap. Two targets both report ".NET in production". One is an API on .NET 8 with good tests and current packages: a dated upgrade item. The other is a customer portal on ASP.NET Web Forms targeting 4.6.2 on Windows Server 2016: a Windows move now, and a staged rewrite to price before signing.
What a seller can do now
- List the versions. Every project's target framework, every server's Windows version, the runtime patch level.
- Move modern .NET to .NET 10. Often the cheapest finding to close before a buyer sees it, when the tests and packages allow it.
- Move .NET Framework 4.6.2 to 4.8 or 4.8.1 and plan the move off Windows Server 2016. Test it in pre-production first. This takes the January date off the list.
- Get an honest estimate for the larger move. If the platform will one day need to leave .NET Framework, a scoped estimate with stages turns an open question into a known number.
- Put it in the data room. Versions, plan, dates and people, ready before the questions. This is the kind of work our exit readiness program runs month by month.
What a buyer can do
Ask for the target frameworks and Windows versions before the full review, so the difference between an upgrade and a rewrite is in the model before the price is. Test any seller estimate for a move off .NET Framework against the size of the code and the app model. A red-flag memo early in the process, or a full technical due diligence, puts it on the table while it can still be priced.
A short checklist
- Every project's target framework, modern .NET and .NET Framework.
- Windows Server versions in production, with Windows Server 2016 flagged.
- Runtime patch level.
- App model of classic web applications, and any WCF, Workflow Foundation, remoting or COM+.
- Third-party packages and controls without a modern .NET version.
- A plan with dates, budget and named people for each move.
- How each item will appear in the data room and the disclosure.
Questions
Does a .NET application stop working when its version loses support?
No. It runs the day after the deadline as it did the day before. What stops are Microsoft's fixes: any weakness found later in that version stays without an official patch. The risk grows over time, and the gap to current versions widens, which makes the eventual upgrade larger the longer it waits.
Is moving from .NET 8 to .NET 10 a small job?
Often it is contained, because both are modern .NET and Microsoft describes such moves as mostly the target framework, dependencies and breaking changes. What decides the size is which breaking changes touch the product, whether every third-party package has a .NET 10 version, whether tests can show nothing broke, and how many releases were skipped.
What is the difference between .NET Framework 4.8 and modern .NET?
They are separate platforms. .NET Framework 4.8 and 4.8.1 are Windows components with no announced end date, supported as long as the Windows version under them is. Modern .NET, such as .NET 10, is the platform that gets new releases. Moving from 4.6.2 to 4.8 is usually small; moving from .NET Framework to modern .NET can be a staged rewrite.
How does an old .NET Framework platform show up in deal terms?
A contained upgrade usually becomes a dated item in the first months, a condition before closing or a disclosure with a plan. A platform that has to leave .NET Framework is a larger item: it can affect the price, a holdback until a stage is done, or a specific disclosure. The parties and their lawyers choose; the reviewer gives them scope, time and cost.
Where are the dates for other technologies?
On our page of technology deadlines for owners, which lists end of support, major releases and new rules for languages, frameworks, databases and platforms, each with its official source. Both .NET dates in this note are there, next to the Windows Server 2016 date and the other deadlines that tend to land inside a deal timeline in the coming months.
