There’s a whole generation of business websites and internal tools built on ASP.NET between the mid-2000s and mid-2010s — Web Forms apps, custom CMSes, order portals — still faithfully running the back offices of the Midwest. They were built well, which is exactly why nobody’s touched them in a decade. If you own one, here’s your plain-terms situation.

The good news first

Classic .NET Framework (the 4.8 branch these apps run on) ships with Windows and is patched as part of Windows itself — so unlike a Drupal 7 or Magento 1 site, an old .NET app on a current, patched Windows Server isn’t automatically a security emergency. These apps are the snowmobile that starts every winter: old, unfashionable, still going.

The actual risks

They’re around the framework, not in it. Web Forms is done evolving — modern .NET went a different direction and Web Forms didn’t make the trip, so the app can’t adopt anything new; it can only be preserved or replaced. The server underneath ages — Windows Server versions have end-of-support dates, and the risky moment is the OS migration nobody planned. The knowledge evaporates — the developer who knew where the bodies were buried retires, and the pool of people who want to work on Web Forms shrinks yearly. And too often the source code is missing — the server runs compiled binaries and nobody can find the Visual Studio project that produced them. That’s a four-keys problem with a .NET accent, and it’s the first thing worth locating while people who might know are still reachable.

The realistic paths

Preserve — current OS, documented deploy, source code found and in version control. Cheap, honest, buys years. Replace the edges — keep the .NET core doing its job, put a modern site or portal in front. Migrate — to modern .NET or to a CMS, when the app’s job has outgrown its body. Which path fits is an assessment question, and yes — the rescue assessment reads .NET. Platforms differ; orphaned software is orphaned software.