Bruce Gilham Jr.
Dying · no new development since 2000

Classic ASP still runs. No debugger, no tests, and it is your problem now.

Where you are

IIS still ships the Classic ASP runtime, so a twenty-five-year-old VBScript application keeps limping along with 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 the move goes

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. Same pattern every time: get the database somewhere safe first, put the new application 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 line by line.

Other platforms

Dead · support ended October 2021

Your Silverlight app has no browser to run in. The code still says what it does.

Dead · retired with Visual Studio 2015

LightSwitch generated your app. You cannot regenerate it, but you can read it.

Dying · VB6 IDE unsupported since 2008

The VB6 runtime still ships with Windows. The IDE and the developers are gone.

Orphaned · the developers are retiring

Delphi is alive. Your Delphi 5 codebase, on components that no longer compile, is not.

Dead · support ended January 2015

FoxPro. Yes, still. Someone has to open it.

Orphaned · HCL owns it; nobody is hiring for it

Your records are in Notes databases. Someone has to read the Notes data model to get them out.