Migrating Your ASP.NET Web Forms Application to .NET Core
Tons of business applications have been written in .NET and its most famous project type – the ASP.NET Web Forms, which some 20 years ago helped organizations migrate their legacy Windows Forms applications to the web and thus open to global markets.
.NET Core (and its latest version, .NET 5) is the exciting new future for .NET and, along with its announcement, Microsoft made it clear that ASP.NET Web Forms will not be ported to .NET Core.
While your ASP.NET Web Forms applications will remain functional as long as you have the talent to support them, just like Classic ASP applications, they will become increasingly brittle and outdated over the years.
.NET 5 is here. What does it bring along?
.NET 5 is the new step forward with .NET Core, the platform where all future Microsoft investments in .NET will converge. When compared to .NET Framework, .NET Core has a lot to offer that resonates with modern application development principles:
- The code you write will build upon the same shared framework components APIs, regardless of the type of app you are building.
- You will be able to reuse more code across app types, platforms and devices C# updates move in lockstep with .NET 5. Developers will have access to the latest C# version and features.
- You will be using the same languages across application types, operating systems, and chip architectures.
- You will have the ability to choose the runtime experience (CoreCLR or Mono).
- Objective-C and Swift interoperability will be supported on multiple operating systems.
With .NET 5+, Microsoft builds on its promise to make .NET more universal and offer broader capabilities.
Why should you migrate to .NET Core?
While Microsoft confirmed they would be supporting existing ASP.NET Web Forms applications, for the time being, there are many good reasons for you to consider migrating to the latest .NET project.
Key concerns to consider:
Still running ASP.NET Web Forms or Classic ASP.NET applications?
These are your options:
The Resolute Way
Web development is moving fast. Web applications need to be lightweight and performant to deliver business value. Further, they need to be secure, responsive, and operational across browsers, platforms, and devices. You might want to focus on planning for the not-so-distant future, weighing the pros and cons of staying with obsolete technology.
Choosing to modernize your application using MVC, Razor or Blazor would require rewriting the entire application, retraining your team while fixing UI glitches, and handling customer dissatisfaction that inevitably stems from such updates. If your organization does not have the resources to dedicate to manage all this, a partner may be the way to go.
At Resolute Software, we take the time to assess your application‘s architecture, interdependencies with other applications and databases, separation of the business logic from the UI before proposing a plan of action.
The Steps We Take
A quick rundown of the ASP.NET Web Forms application modernization steps we take: