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.

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.

Tell me what it runs on All Classic ASP work