Light at the end of the tunnel: Your options for migrating from Silverlight
Reading time: 3 minutes
For companies still using Microsoft Silverlight, you may be concerned that a migration will put your teams way out of their depth. But there are several paths forward for your Silverlight application, and the options open to you don’t necessarily have to sacrifice the current expertise of your staff, or your legacy codebase.
Let’s start where you are in your decision journey.
Silverlight reaches end-of-support on October 12, 2021. That gives companies approximately 16 months to complete their migration to a new platform, which can be ample time if you make some key decisions up front. First, you know that Silverlight is only compatible with Internet Explorer versions 10 & 11, limiting your potential user base. Ideally, your application would be accessible on any desktop or mobile device, to increase your users and expand your reach. Opening up to new users could have far-reaching implications for your business and bottom line. What are your business goals for 2021 and beyond? You can tie those goals to your migration to give it weight and greater impact across the company.
Identifying larger business goals that a migration can help to achieve will make the process an exciting challenge for your teams, rather than a mad scramble not to get left behind. The potential for reinvigorating your people shouldn’t be ignored.
Let’s do a classic compare and contrast.
You may have heard of Microsoft’s new open-source front end framework, Blazor. One of the key benefits of using this system is that you can potentially reuse parts of your existing codebase—a major consideration for many companies with legacy systems. The program is .NET running on WebAssembly, so you can re-use code and libraries from server-side parts of your application. Using WebAssembly will also ensure that your current developers who are experienced with .NET will be able to work in the new environment without extensive retraining.