BDG Software · Bruce Gilham Jr. · writing code since 1996, incorporated 2000
If you have inherited a Silverlight, LightSwitch, Classic ASP, VB6, FoxPro or Delphi codebase and nobody left can tell you what it does, that is the job I do. I read the code and the schema, document what actually happens, and move it piece by piece to C# and .NET while the old one keeps running. You get a stack you can work in every day, and documentation you did not have to write.
Your Silverlight app has no browser to run in. The code still says what it does. I have written Silverlight and I have migrated it.
LightSwitch generated your app. You cannot regenerate it, but you can read it. I built four production systems on LightSwitch, payroll, used-car wholesale, right-of-way appraisal and a food plant, and I have moved off it.
Classic ASP still runs. No debugger, no tests, and it is your problem now. 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 VB6 runtime still ships with Windows. The IDE and the developers are gone. I have shipped WinForms desktop systems for a bond-pricing desk, an industrial fastener-measurement fixture, an investment back office and a food plant, and moved desktop systems to the web.
Delphi is alive. Your Delphi 5 codebase, on components that no longer compile, is not. I learned Delphi in the 1990s in my father's shop and never stopped.
FoxPro. Yes, still. Someone has to open it. I moved a chart-data publisher's FoxPro archive and book-generation tools onto Azure SQL, and kept the FoxPro tools running against the new database until their replacements were ready.
Your records are in Notes databases. Someone has to read the Notes data model to get them out. I spent thirteen years inside one firm's Lotus Notes estate, first building inside it in LotusScript so their investment was not thrown away, then lifting the records into SQL Server when the time came to put a client portal on top.
Also on the list: WCF and WCF RIA Services, WPF, Entity Framework 6, SQL Server 7, Microsoft Access back ends, Silverlight-era Dynamics CRM customisations, and the ArcGIS Silverlight SDK. When the migration hits legacy C or C++, I read that as well.
I take the code, the schema and whoever is left, and write down what the system actually does — usually different from what anyone thinks, and different from the comments. That specification gets signed off before I write a line of the new one.
Old and new run side by side against the same database. Each screen or feature crosses over on its own, gets verified in production, and only then does the old one get switched off. Nobody has to stop using the system while it happens.
You end on C#, .NET and Azure or SQL Server, with documentation and a codebase your team can work in. I am not trying to become the one person who understands it.
Five acquired healthcare products, nine programming languages, one gRPC data access layer, all migrating onto Azure under HIPAA, HITECH, HITRUST and SOC 2 without a big-bang cutover.
SQL Server 7 backups restored into Azure SQL, a Classic ASP app rebuilt in Blazor, and the Visual FoxPro book tools pointed at the new database until their replacements shipped.
Thirteen years as the only developer on one firm's system: LotusScript inside their Notes estate, then Silverlight, then LightSwitch, then Esri ArcGIS cloud sites over SQL Server, each rebuild done while the previous one stayed live.
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.
Forty hand-edited flat files replaced with direct Bloomberg BLPAPI calls, futures screens with automatic rollover, and a years-old 'mouse flicker' bug traced to unreleased pointers in the vendor's .NET wrapper.
SQL Server replication repaired, a row-losing data warehouse fixed, and an Access front end replaced with a LightSwitch client over a web-service layer, with Twilio SMS and record locking.
A developer or team that has inherited a system that runs the business and cannot read it. You need someone who has worked in these codebases before, not another job posting. Very often the migration is the second problem: the first is that nobody knows what the old system does any more. I handle both.
Not for: greenfield apps any agency could build, staff augmentation by the hour, or anything I would not put my name on. Thirty-five years of building what could not be built or fixing what other people broke is the work I take.
Say what the system does, what it is written in, and what breaks when it goes down. I will tell you straight whether I can help and roughly what it takes. No sales call, no deck.
Start here