End-of-life .NET applications
.NET end-of-life: rescue, upgrade or rebuild?
Upgrade an end-of-life .NET application in place when the code is healthy, migrate it piece by piece when it is large and must stay live, and rebuild when little of the code is worth keeping. If only one developer understands it, write tests and documentation and pair a second engineer with them before any upgrade starts.
Updated
Rescue, upgrade or rebuild: the short answer
Most end-of-life .NET applications should be upgraded, not rebuilt: move to .NET 10, the current long-term support release, in steps you can release one at a time. Stabilize first if releases already break or only one person can ship, and rebuild only the parts that have no path to current .NET.
The right path depends on what the application runs on, how large it is, and whether your team can release it safely today. This table is the short version.
| Path | Fits when | Watch out for |
|---|---|---|
| Stabilize, then upgrade | Releases break, tests are missing, or only one developer can build and ship the application. | Upgrading code nobody can test moves the problems to a new runtime. Fix the tests and the release first. |
| In-place upgrade | The application already runs on .NET Core or .NET 5 or later, or it is a small .NET Framework application with few dependencies. | Breaking changes add up across versions. Read each version's breaking changes, and release after each step. |
| Incremental migration | A large ASP.NET application on .NET Framework that must stay live while it moves, one route or feature at a time. | Two applications run side by side for a while, so sign-in and session state must work across both. |
| Rebuild | Large parts use technology with no equivalent in current .NET, or the product must now do something the design cannot. | A rebuild must reproduce every business rule in the old code, and the old system needs support until it is replaced. |
Which .NET versions are out of support
The current long-term support release is .NET 10. Microsoft supports it until .
As of , these versions no longer get security fixes from Microsoft:
- .NET 9: support ended
- .NET 8: support ended
- .NET 7: support ended
- .NET 6: support ended
- .NET 5: support ended
- .NET Core 3.1: support ended
- .NET Framework 4.5.2, 4.6 and 4.6.1: support ended
- .NET Framework 4, 4.5 and 4.5.1: support ended
.NET and .NET Framework follow different rules. Microsoft supports each .NET release for a fixed time: three years for a long-term support (LTS) release and two years for a standard-term support (STS) release. .NET Framework 4.5.2 and later is a component of Windows, so it is supported for as long as the Windows version it runs on, unless Microsoft sets an earlier date for a specific version.
| Version | Release type | End of support | Status on November 12, 2026 | Source |
|---|---|---|---|---|
| .NET 11 | STS | Supported | .NET policy | |
| .NET 10 | LTS | Supported | .NET policy | |
| .NET 9 | STS | Out of support | .NET policy | |
| .NET 8 | LTS | Out of support | .NET policy | |
| .NET 7 | STS | Out of support | .NET policy | |
| .NET 6 | LTS | Out of support | .NET policy | |
| .NET 5 | STS | Out of support | .NET policy | |
| .NET Core 3.1 | LTS | Out of support | .NET policy | |
| .NET Framework 4.8.1 | None | Follows the Windows version | Supported | .NET Framework policy |
| .NET Framework 4.8 | None | Follows the Windows version | Supported | .NET Framework policy |
| .NET Framework 4.7, 4.7.1 and 4.7.2 | None | Follows the Windows version | Supported | .NET Framework policy |
| .NET Framework 4.6.2 | None | Supported | .NET Framework policy | |
| .NET Framework 4.5.2, 4.6 and 4.6.1 | None | Out of support | .NET Framework policy | |
| .NET Framework 4, 4.5 and 4.5.1 | None | Out of support | .NET Framework policy |
Sources, read on November 12, 2026: Microsoft's .NET and .NET Core official support policy, .NET Framework official support policy and Lifecycle FAQ: .NET Framework. Check them again before you plan: the dates change as Microsoft ships new releases.
What end of life means for security and compliance
When a version reaches its end-of-support date, Microsoft stops releasing security fixes for it. A vulnerability found after that date stays open in your application, however serious it is. The application keeps running, which is why the risk is easy to put off.
The risk shows up in other places first. Security scanners flag the runtime. Customers' security questionnaires ask whether your software runs on supported versions. Audits ask how you keep software patched, and an unsupported runtime has no patches to apply. And packages you depend on stop shipping versions for the old runtime, so even routine fixes get harder.
The longer an upgrade waits, the bigger it gets. Each skipped version adds its own breaking changes, and the people who remember why the code works the way it does move on.
How to take inventory of what you run
Before you choose a path, find out exactly what you have. Most teams find more than one version in the same solution.
Target framework of every project
Each project file names its target: net48 or v4.8 means .NET Framework, netcoreapp3.1 means .NET Core 3.1, and net8.0 means .NET 8. A solution often mixes them.
Runtimes on every server
List the runtimes installed where the application runs, including build agents. An application can target one version and run on another.
The Windows version under .NET Framework
.NET Framework 4.5.2 and later follows the support of the Windows version it is installed on, so an old server can end support for the application too.
NuGet packages
Find packages that are abandoned, or that have no version for current .NET. They often decide the upgrade path more than your own code does.
Parts that do not move as they are
ASP.NET Web Forms, WCF services and code that depends on System.Web need more than a version change. Count them before you choose a path.
Sign-in and secrets
Note how users sign in, and where passwords and keys are stored. IdentityServer4 and custom logins are common upgrade blockers.
Who can build and release it
Write down who can build, test and release the application today, and where those steps are written down, if anywhere.
The three upgrade paths
1. In-place upgrade
Change the target framework, update the packages, fix what breaks, and release. This fits applications already on .NET Core 3.1 or .NET 5 to 9, and small .NET Framework applications. Go one step at a time, and run the tests after each step.
Microsoft has deprecated the .NET Upgrade Assistant, its earlier tool for this work. Its Upgrade Assistant page now points to the GitHub Copilot modernization agent in Visual Studio instead. Treat any tool's output as a first draft: the tests decide whether the upgrade worked.
2. Incremental migration
For a large ASP.NET application on .NET Framework, Microsoft recommends an incremental migration for most production applications, and describes it as an implementation of the Strangler Fig pattern (Microsoft's migration guide). A new ASP.NET Core application sits in front of the old one and forwards requests to it with YARP (Yet Another Reverse Proxy). You move routes and features to the new application one at a time, and the old application shrinks until it can be switched off (Microsoft's getting-started steps).
Users keep working the whole time, and each move is small enough to release on its own. The cost is running two applications for a while, with sign-in and session state shared between them.
3. Rebuild
Rebuild when large parts of the application have no path to current .NET, or when the business now needs something the design cannot do. Even then, rebuild the parts that need it, not always the whole system. A rebuild has costs that are easy to miss: finding every business rule again, moving the data, and supporting the old system until the new one replaces it. Read how to decide between rescue and rebuild before you commit.
An upgrade does not have to mean a rebuild. In the PSIA / SnowPro case study, Briebug upgraded the .NET and Angular stack in place instead of starting over.
When only one developer understands it
Many end-of-life .NET applications have one person who knows how to build, release and fix them. That is the first risk to remove, before the runtime. If that person leaves during an upgrade, you have a half-upgraded system nobody can finish.
Move the accounts first
Put the repositories, pipelines and cloud subscriptions into accounts your company owns, with at least two administrators.
Write down how it is built and released
Record every step to build, configure and deploy the application, then have someone else follow the notes and fix what is missing.
Pair a second engineer
Have a second engineer work beside the one who knows the system, on real changes, until they can make and release a change alone.
Write tests before you change anything
Add tests that record what the application does today, for the features that earn money first. The upgrade is safe when those tests pass on the new version.
Upgrade in small, released steps
Release after each step, so a problem points to one small change, not to a long list.
If the developer has already stopped answering, start with what to do when your developer disappears. If a vendor holds the knowledge, see how a project takeover works.
What a .NET assessment covers
An assessment answers the question this page cannot: which path fits your application. Briebug's fixed-fee Technical Assessment costs $10K, takes about 1 week, and reviews:
- The .NET versions, runtimes and packages in use, and their support dates
- The code and architecture, including the parts that block an upgrade
- Sign-in, secrets and the findings a security review would raise
- The build and release pipeline, and how changes reach production
- Who knows what, and what is written down
- A recommended path (upgrade, migrate or rebuild), a triage report of what to fix in what order, and a milestone-based estimate
The report is yours to take to any team. If you want Briebug to do the work, see .NET project rescue, or how a software project rescue runs from assessment to handback.
.NET end-of-life questions
Which .NET version should we upgrade to?
.NET 10, the current long-term support (LTS) release. Microsoft supports it until November 14, 2028. LTS releases get three years of support and STS releases get two, so an LTS release gives you the longest time before the next upgrade.
Is .NET 8 still supported?
No. Microsoft's support for .NET 8 ended on November 10, 2026. Upgrade to .NET 10, which Microsoft supports until November 14, 2028.
Is .NET Framework 4.8 end of life?
Not on a fixed date. Microsoft supports .NET Framework 4.8 and 4.8.1 for as long as the Windows version they run on is supported. .NET Framework 4.6.2 support ends on January 12, 2027.
Can we upgrade without a rewrite?
Usually, yes. An application on .NET Core or later can often be upgraded in place, one version at a time. A large ASP.NET application on .NET Framework can move route by route while it stays live. A rebuild is for the parts that have no path to current .NET.
Only one developer understands our application. Where do we start?
Move the accounts into your company's name, write down how the application is built and released, and pair a second engineer with the developer. Then write tests for what the application does today, before anyone changes it.
How much does a .NET assessment cost?
Briebug's Technical Assessment is a fixed fee of $10K and takes about 1 week. It ends with a triage report and a milestone-based estimate for the upgrade.
Running an end-of-life .NET version?
Book a short call with a senior engineer. We will scope the assessment and confirm the fixed fee before you commit.