.NET 8 and .NET 9 both lost support on November 10, 2026. .NET Framework 4.6.2 ends with Windows Server 2016 on January 12, 2027. What to do with each, what ports cleanly to .NET 10 and what does not (Web Forms, WCF, Workflow Foundation), and how AWS Transform changes the cost.
Moving from .NET 8 to .NET 10 is a normal upgrade: change the target framework, update packages, fix breaking changes, test. Plan days per application, not months. Microsoft now supports STS releases for 24 months, but even releases (LTS) remain the right default for production.
Moving off .NET Framework is a port. Most class libraries, ASP.NET MVC and Web API code move with moderate work. Three technologies do not exist in modern .NET and need replacing: ASP.NET Web Forms (Blazor or Razor Pages), WCF server-side (CoreWCF or gRPC) and Windows Workflow Foundation (a rewrite, often onto Step Functions or durable functions).
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Linux. Modern .NET runs on Linux containers and Graviton, which removes the Windows licence from every instance, often a third or more of its hourly price.
Lambda and ECS. Modern .NET runs on Lambda and in small containers; .NET Framework needs Windows hosts.
One lifecycle. Annual releases with predictable dates, instead of a framework tied to the Windows Server version underneath it.
Performance. Each modern .NET release has been faster than the last; teams moving from .NET Framework commonly need fewer, smaller instances.
AWS Transform ports .NET Framework applications (3.1 and later) to cross-platform .NET, now including .NET 10, analysing dependencies across repositories and producing changes for review. The full-stack Windows agent adds database conversion and Web Forms to Blazor. The AWS Transform .NET CLI, generally available since September 2026, includes 50,000 free agent minutes a month, so sizing a port costs little. It handles the mechanical majority of a port. Plan your time for what it cannot decide: replacing Windows-only dependencies, choosing what to do with WCF and Workflow, and testing.
Move everything still on .NET 8 and 9 to .NET 10 now: neither has had security patches since November 10, 2026. Include Lambda functions on the dotnet8 runtime.
Move anything on .NET Framework 4.6.2 to 4.8.1 before January 12, 2027 if it cannot be ported in time. It is an in-place framework change with high compatibility.
Port .NET Framework applications to .NET 10 in order of value: the ones changed most often and the ones on the largest Windows instances first.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Windows Server 2012 R2's Last Security Updates Ended in October 2026: What to Do This Quarter
The third and final year of Extended Security Updates for Windows Server 2012 and 2012 R2 ended on October 13, 2026. There is nothing left to buy. How to contain the servers still running it, and the fastest ways off: in-place upgrade, rebuild, AWS's End-of-Support Migration Program, or retirement.
Read
Microsoft End of Support (EOS) 2026 and 2027: Windows Server, SQL Server and Every Server Product
Windows Server 2016, .NET Framework 4.6.2, IIS 10 on 2016, BizTalk 2016, System Center 2016 and TFS 2017 all end support in January 2027. SQL Server 2017 follows in October, after SQL Server 2016, SharePoint 2016 and 2019 and .NET 8 in 2026. The full list for server teams, and what each ending actually means.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.