Dying · no new development since 2000

Classic ASP still runs. That is why it never gets fixed.

Where the business is

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.

What I do about 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 pattern is the same 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, which keeps the read phase short and bounded.

Tell me what it runs on All Classic ASP work