Playbook · Migrations

Updated

How do you do a Silverlight to Angular migration?

A Silverlight to Angular migration is a rewrite of the screens, not a port: XAML and C# don’t run in a modern browser. Silverlight support ended on 12 October 2021, so the job is to rebuild the UI in Angular and keep as much of the server side as you can.

Silverlight reached end of support on 12 October 2021. In its last years it was supported only on Internet Explorer 10 and 11, with no support for Chrome, Firefox or any browser on Mac.
Source: Microsoft, 10 Jul 2019

Why this one cannot wait

The browser it needs is gone too. The Internet Explorer 11 desktop app ended support on the Windows 10 semi-annual channel on 15 June 2022. Microsoft points customers to Edge with IE mode, which it supports through at least 2029. If users still open a Silverlight app today, it runs on a setup someone keeps alive on purpose, outside Microsoft’s support for Silverlight. That person deserves a thank-you and a way out.

What carries over and what doesn’t

  • The UI does not. Silverlight screens are XAML with C# or Visual Basic code behind them. Every screen is rebuilt as Angular components.
  • The services often do. Silverlight apps talked to WCF, SOAP or ASP.NET AJAX services. If those still run, Angular can call them through a thin REST or JSON layer while the backend stays.
  • LINQ queries in the client move to the API or into TypeScript.
  • Out-of-browser features, such as local files or running as a desktop app, need a new answer: a web feature, or a desktop shell.

Steps for a Silverlight to Angular migration

  • List every screen and who still uses it. Old line-of-business apps often have screens nobody opens. Those are the cheapest ones to migrate.
  • Document the business rules hidden in the C# code behind, before anyone deletes it. A click handler is sometimes the only place a rule was ever written down.
  • Put a REST layer over the existing services.
  • Rebuild screens in Angular, starting with the most used.
  • Run both until the last user moves, then switch the old app off. Expect the last user to take a while.

What drives the cost

The number of screens, how much logic sits in the code behind rather than the services, and whether the services can stay. There is no published market range worth quoting for this kind of rewrite. An estimate needs someone to read the code.

First step

In its first 5 business days, the 14-day Trial ($995) gives you the screen and service map and the rebuild order. I then make the first fixes that fit in the 14 days, and it ends with a written plan for the rest. The Trial fee is credited to your first month if you start a monthly plan within 14 days of the Trial ending.

Read next

Sources

Start

Tell me where the product is stuck.

In 30 minutes we look at where things stand, what you need from a CTO right now, and which option fits. Either way, you leave with a clear next step.

How the call goes

  1. 01You tell me about the product, the team and the next 6 months.
  2. 02I ask about the code, the stack and what keeps breaking.
  3. 03We pick the option that fits, or agree that none does.

09:00 to 20:00 CET

Founding rate: the first 3 clients get 20% off, in return for a named testimonial and a case study. On a monthly plan, the 20% applies to the first month.