![]() ![]() NET code in the browser without the need for a plugin. NET Framework and run-time into WebAssembly, then running your native. Blazor accomplishes this in a different way by compiling a micro version of the. NET and use it seamlessly across current web browsers. Blazorīlazor and WebAssembly are still in their infancy, but I’ll mention it here because it has similar aims that Silverlight had: the ability to develop with. This choice greatly limits your deployment options when compared to web or cross-platform mobile, but for applications that only need to run on Windows, Xamarin or Universal Windows Platform (UWP) will give your development team a familiar XAML design language with vast improvements from the Silverlight era. Some Silverlight apps were really just as well suited to be a Windows application. Again, you have the capability to upfit your existing data services to work with a new mobile application or build a modern data layer that uses your existing database. In these cases, we often build a cross-platform mobile application (iOS, Android, Windows) using Xamarin Native or Xamarin Forms along with Telerik UI for Xamarin. ![]() Xamarin Mobileįor others, even though their application was built as a desktop web application with Silverlight, it was really best suited as a mobile application. If you want to update your back-end services to the latest technologies, such as ASP.NET Core, this could be done all at once, or in phases if time and budget don’t allow for a full rewrite before the Silverlight end-of-life. There are various approaches to upfitting your data services to support web applications so you can retain a good portion of your back-end logic while you replace the front-end with a modern web application. ![]() This still gives you a feature-rich user experience with the added benefit of responsive design that can support tablets or mobile phones–something Silverlight was never able to fully offer.Įven with this approach, it doesn’t require you to throw away all layers of your Silverlight application. Modern WebĪt Trailhead, we have worked with many clients to help them migrate their application from Silverlight, and the most common choice is to develop the application with modern web platforms: Angular or React, often paired with Telerik Kendo UI and built with corresponding REST APIs, typically built with ASP.NET or ASP.NET Core. Although unlike other deprecated development platforms, Silverlight doesn’t leave many options to salvage all of your existing code, but we’ll identify some ways to make a migration less painful. It is time to move on, and fortunately, there are a wealth of modern development platforms to choose from. Even with time left on the support clock, the only remaining browser that runs Silverlight without browser modifications is Internet Explorer. XAML provided precise and flexible layout, the Silverlight plugin alleviated most browser compatibility issues, MVVM and data binding allowed you to reduce coupling, and WCF RIA Services made it easy to rapidly build data services with corresponding client-side models.īut as HTML tooling improved and browser plugins fell out of favor, Microsoft made the decision to sunset Silverlight and end its mainstream support window in October 2021. A decade ago, Silverlight was king and I loved every minute of it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |