Bruce Gilham Jr.
Dying · no new development since 2000

Classic ASP still runs. That is the problem.

Where you are

IIS still ships the Classic ASP runtime, so a twenty-five-year-old VBScript application keeps limping along: no debugger, no tests, no dependency management, and a security surface from another century. Because it never quite dies, it never gets budget, until the one person who understood it leaves.

How I get you off it

I migrated a music-rights royalty system and a twenty-year Billboard chart archive off Classic ASP, the second one to Blazor on Azure, with the business publishing throughout. The approach is the same every time: get the database somewhere safe first, stand the new application up beside the old one, and switch pages over one at a time. Where the old code has no documentation, an LLM-assisted pass with a confidence score on every record finds what the code actually does faster than reading it.

Other platforms

Dead · support ended October 2021

Silverlight has no runtime left. The exit is screen by screen, not a rewrite.

Dead · retired with Visual Studio 2015

LightSwitch generated your app. The tooling to regenerate it is gone.

Dying · VB6 IDE unsupported since 2008

The VB6 runtime survives on Windows. The developers do not.

Orphaned · the developers are retiring

Delphi is alive. Your Delphi 5 codebase is not.

Dead · support ended January 2015

FoxPro. Yes, still. The data comes out first.

Orphaned · HCL owns it; nobody is hiring for it

Your records are in Notes databases. Getting them out is the job.