Frasco Inc.
ASP.NET Core over OData into a Delphi/InterBase back office: self-service ordering, Stripe payments with per-state fee rules, single sign-on, and a thirty-project .NET estate pulled into one solution.
Embarcadero still ships Delphi. That is not the problem. The problem is a Delphi 5 or Delphi 7 application written twenty years ago by someone who has since left, on components that no longer compile, with the only person under sixty who can read Object Pascal already booked. Job postings for Delphi maintainers stay open for a year.
I learned Delphi in the 1990s in my father's shop and never stopped. I built a manufacturing execution product in it that is still sold twenty-five years later, and I have spent fourteen years building modern .NET on top of a Delphi/InterBase back office that the client rightly refused to throw away. Sometimes the right answer is to keep the Delphi and put a modern front on it. Sometimes it is a staged move to C#. I can read the Object Pascal well enough to tell you which.
Your Silverlight app has no browser to run in. The code still says what it does.
LightSwitch generated your app. You cannot regenerate it, but you can read it.
Your records are in Notes databases. Someone has to read the Notes data model to get them out.