Skip to content

.NET Framework and Web Forms Upgrades

Microsoft ends support for .NET Framework 4.6.2 on 12 January 2027. An application still running on 4.6.2 after that date receives no security fixes for the runtime underneath it. Versions 4.5.2, 4.6 and 4.6.1 lost support on 26 April 2022.

For most applications the deadline itself is cleared without a rewrite: Microsoft describes 4.8 and 4.8.1 as in-place updates that existing 4.x applications are expected to run on. The larger decision is what follows, because Web Forms, WCF services and Windows Workflow exist only on .NET Framework. We do both jobs: the runtime update now, and the move to modern .NET where it is worth making.

Support dates

Where each .NET version stands

Dates from Microsoft's .NET Framework and .NET support policy pages, checked on 14 November 2026.

.NET Framework 4.0 to 4.6.1

Out of support. Versions 4.0, 4.5 and 4.5.1 ended on 12 January 2016; versions 4.5.2, 4.6 and 4.6.1 ended on 26 April 2022.

.NET Framework 4.6.2

Support ends on 12 January 2027. It is the oldest 4.x version Microsoft still supports, and the one this deadline is about.

.NET Framework 4.7 to 4.8.1

No end date published. Microsoft supports these as part of Windows, so they follow the support dates of the Windows version they are installed on. Check the server's Windows version as well as the runtime.

.NET Framework 3.5 SP1

Support ends on 9 January 2029 where it is installed on Windows 10 version 1809, Windows Server 2019 or later.

Modern .NET 8 and 9

Both went out of support on 10 November 2026. An application moved off .NET Framework a few years ago may now be behind again.

Modern .NET 10 and 11

Both supported until 14 November 2028. .NET 10 is the long-term support release and the usual target for a move made now.

Scope

What an upgrade covers

The runtime number is one line in a project file. These are the parts that decide how much work sits behind it.

  • The target framework of every project in the solution, and the runtime installed on every server
  • The Windows Server and IIS versions underneath, since .NET Framework support follows Windows
  • NuGet packages and third-party controls, with replacements for those no longer maintained
  • Web Forms pages, user controls, view state and session use, counted and grouped by how they are used
  • WCF services, Windows services and scheduled jobs that the application calls or that call it
  • SQL Server version, stored procedures and reports that the application depends on
  • Automated tests for sign-in, payments and document output, written before the first change
  • A staging copy where your team checks the upgraded system, and a written way back for the release
Order of work

How an upgrade runs

  1. Inventory

    We read the solution and the servers: target frameworks, installed runtimes, Windows and IIS versions, every package and every system the application talks to. You receive a written list of what blocks each route and what it costs to clear.

  2. A safety net

    Before changing anything, we add tests around the paths the business cannot lose. Where tests are impractical, we record how each path behaves today so the upgraded version can be compared with it.

  3. The runtime update

    The application is moved to .NET Framework 4.8 or 4.8.1 on staging and checked there. This clears the January deadline and is a separate, small release.

  4. The route after that

    Staying on 4.8.1 is a legitimate choice for a system that works. Where modern .NET is worth it, the new application runs beside the old one and takes over one group of screens or one service at a time, so the system stays in use throughout.

  5. Your check and release

    Your staff work through their real daily tasks on staging. Each release happens at a time agreed with you, with the previous version ready to return to, and we watch errors and logs for the following days.

Judgement

When a move to modern .NET is not the answer

Moving to modern .NET suits

  • The application is under active development and will be for years
  • You want to leave Windows Server licences or run in containers
  • Packages you depend on have stopped releasing versions for .NET Framework
  • Hiring for Web Forms work has become difficult

Staying on .NET Framework 4.8.1 may suit better

  • The system is stable, changes rarely and runs on a supported Windows Server
  • It is built on Web Forms and has hundreds of pages; that is a rebuild of the interface, which needs its own business case
  • It is being retired within a year or two; the runtime update and hardening may be enough
  • What the application must keep doing is not written down anywhere; an assessment comes before any upgrade
Questions

Common questions

Does our application have to be rewritten before January 2027?

Usually not. Microsoft describes .NET Framework 4.6.2 and later versions as compatible in-place updates, and states that recompiling is not necessary. The work is to install 4.8 or 4.8.1 on a staging server, test the application there and release. A small number of behaviour changes exist between versions, which is why it is tested first.

Is Web Forms going away?

Web Forms is part of .NET Framework, and .NET Framework 4.8.1 has no published end date; Microsoft supports it for as long as it runs on a supported version of Windows. Web Forms was not carried into modern .NET, so an application built on it either stays on .NET Framework or has its screens rebuilt.

Can Web Forms pages be converted automatically?

Not to a standard we would release. Tools can move project files, class libraries and some code. Pages that rely on view state, server controls and postbacks are rebuilt, usually as Razor Pages or Blazor components, while the business logic behind them is kept.

How long does an upgrade take?

It depends on the route. The runtime update is small when the dependencies allow it. A move to modern .NET depends on the number of screens, the packages and the services around the application. The inventory gives you a range for each route before you commit to one.

We are already on .NET 8. Does this page apply to us?

A different deadline does: .NET 8 and .NET 9 both went out of support on 10 November 2026. Moving from .NET 8 to .NET 10 is a far smaller job than leaving .NET Framework, and we do that as well.

Our server runs an old Windows Server too. Does that matter?

Yes. .NET Framework 4.x is supported as part of Windows, so a supported runtime on an unsupported Windows Server is still unsupported. The inventory records both, and the server move is planned with whoever runs your hosting.

For enterprise buyers

What your procurement team will ask, answered before the call

  • Your paper or oursNDA, data-processing agreement, master agreement and statement of work.
  • Named peopleThe statement of work names the delivery lead and the escalation contact above them.
  • Your code, your accountsWork is committed to your repository and assigned to you on final payment.
  • Local sales teamsSales teams in the UAE and Singapore; engineering in Rajkot and Ahmedabad, India.
Next step

Tell us your .NET version and what the application is built on

The .NET Framework version, whether the application is Web Forms, MVC, a Windows service or a desktop program, the Windows Server version if you know it, and roughly how many people use the system. Not sure of the versions? Tell us that instead; the inventory starts by finding them. We reply within one business day.

Discuss a .NET upgrade

Goes straight to our team on WhatsApp and email. We reply within one business day.