Bruce Gilham Jr.
Dead · support ended October 2021

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

Where you are

Microsoft ended Silverlight support on 12 October 2021 and no current browser loads the plug-in. So the app is frozen on an old machine with an old browser, or someone is rewriting it, and rewrites go wrong because the people who knew what the app actually did have usually left and the code is all that is left to read.

How the move goes

I have written Silverlight and I have migrated it. The move is a Blazor or ASP.NET Core front end over the same database, one screen at a time, old and new side by side until the new screen has proved itself in production. If the app came out of LightSwitch or WCF RIA Services, I know what the generated code looks like and what it was doing, which is what makes this tractable instead of a rewrite from a blank page.

Other platforms

Dead · retired with Visual Studio 2015

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

Dying · no new development since 2000

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

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.