It is impossible to run your ASP.NET Web Forms applications using .NET Core runtime.
Web Forms – like Windows Communication Framework and Windows Workflow Foundation – aren’t dead yet, just in suspended animation as it awaits their real EOL when their respective operating system is no longer supported.
What does that mean for your Web Forms applications? Will you spruce them up, maintaining them every year, maybe migrating them to microservices…or will you let them limp along and only address them when problems crop up?
Now is the time to act; Microsoft has increased its release cadence with the .NET series. Since .NET 5 in 2020, they will release a new .NET every year for the foreseeable future.
In this article, I’ll explain how you can keep your ASP.Net Web forms running safely in .NET 8 and future .NET releases.
Consider Security Risks
Good news: if your Web Forms application is not exposed to the public Internet, there’s little risk in maintaining it.
Still, internal applications can be compromised. Rewriting or patching an application after a vulnerability is discovered becomes more and more expensive as time passes.
Use this opportunity to do a security check on your legacy applications and take inventory of which internal and external applications are at risk.
If your web application requires an old browser, you will need control of the desktop too. Although not a huge barrier, it will add cost and friction to using the application.
Train Generations Ahead
Now is the time to document what Web Forms features your applications leverage and how they use (or abuse) those features.
Eventually (if not already), team members who built, or are greatly familiar with, your team’s Web Forms applications will move on, and their personal understanding of the application will leave with them.
Plan for the Future
There is no immediate need to rewrite your Web Forms applications, but the lack of urgency doesn’t mean we can’t plan ahead. Some actions today to help future team members or set up foundations for future projects can have great ROIs.
Did you find this article helpful? Are you using NuGet to make your .NET packages? Learn how to optimize your NuGet in the Enterprise; sign up for our free NuGet guide: