Series 20 · 8 Parts· 1h 25m

.NET Legacy Modernization

Moving .NET Framework apps onto modern .NET — Web Forms, WCF and ASMX, VB6/VB.NET, and monoliths — slice by slice, parity-proven, with the platform move kept separate from the architecture decision.

Start reading · Part 1
Contents
  1. 01 .NET Framework vs Modern .NET: Why the Platforms Split 10 min read .NET Framework and modern .NET are two different platforms, not two versions of one. Here is what diverged, what it means for an app still on Framework, and why this is a slow liability rather than a panic.
  2. 02 .NET Framework to Modern .NET: The Migration Guide 11 min read How to migrate a .NET Framework application onto modern .NET — assess the estate, sort what ports cleanly from what must be rebuilt, and move it slice by slice with each slice proven before cutover.
  3. 03 Migrating ASP.NET Web Forms to Modern .NET 11 min read ASP.NET Web Forms has no forward port to modern .NET — it must be rebuilt. Here is how to move a Web Forms app to Blazor, Razor Pages, or MVC slice by slice, without losing the logic buried in the code-behind.
  4. 04 Migrating WCF and ASMX Services to Modern .NET 10 min read Server-side WCF and ASMX web services have no forward port to modern .NET. Here is how to choose between gRPC, REST, and CoreWCF, and how to move a service contract without breaking the callers that depend on it.
  5. 05 VB6 and Legacy VB.NET Modernization 12 min read VB6 and legacy VB.NET carry a lot of myth. Here is the accurate support picture, the VB6 runtime is supported, the IDE is not, and VB on .NET is stable but frozen, and how to modernize that code onto modern .NET.
  6. 06 .NET Modernization Tools: What They Do and Where They Stop 10 min read The .NET Upgrade Assistant and the converters genuinely accelerate the mechanical parts of a migration — and stop at the architectural rebuilds. Here is an honest map of what tooling does, and the line past which judgment takes over.
  7. 07 .NET Monolith to Microservices: When (and When Not) 10 min read Landing on modern .NET does not make a monolith well-architected. Here is how to decide whether a .NET monolith should be decomposed into services — and why a modular monolith is often the better destination.
  8. 08 A .NET Modernization, End to End 11 min read A composite walkthrough of a real-shaped .NET modernization — Framework, Web Forms, WCF, a VB.NET service, and a tangled monolith — taken from first assessment to a retired Framework app, slice by slice.