3/13/2023 0 Comments Microsoft silverlight end of life![]() ![]() My personal opinion is that, if you’re moving to HTML, you’d be better off moving to some client-side environment. However, because ASP.NET is a server-side environment, the lack of an interactive event model will force you to significantly restructure your application. If you do decide to move your XAML to HTML, you could migrate your application to ASP.NET. And there are consulting companies ready to help. There is at least one XAML to HTML conversion tool worth considering (complete with a step-by-step tutorial). You can do it by hand (you might want to check out Colin Eberhardt’s experience from 2011)… but there are tools out there to help you. The obvious choice is HTML, if only because your users have been getting your Silverlight applications through a web browser.Ĭonverting XAML to HTML is, clearly, not a trivial task. If you’re going to have to make some conversion effort, you should (at least) be considering converting your XAML to some other format. This means that, even if you want to keep your XAML, you’re going to have to deal with some conversion effort. Windows Presentation Foundation/.NET Framework 3.0.However, part of the problem you’ll face in keeping your XAML is that there are several different versions out there: You don’t have to abandon XAML-there are, at least, two good options that will let you keep some of your XAML. Going to HTML?īut, of course, the elephant in this particular virtual living room is XAML. NET 4.8 and (as of this posting) it had no end-of-life date. The latest/greatest version is Framework. NET Core replacement exists and, if it doesn’t, how much work is required to move to equivalent functionality. For each of those libraries, you’ll need to assess whether a. NET Framework libraries your application references. NET Core as “the current platform with the longest future” (no sense recreating the “abandoned tech” problem you’re facing now). NET?Īssuming you want to stick with Microsoft technologies, you’ll want to move to. There are ways to reduce the pain, however. But, as Silverlight reaches its end of life on October 12, 2021, recreating those applications may be becoming unavoidable for you, no matter how much work is involved. I’m not here to tell you there’s a “no effort/no cost” solution. Well, you’re not wrong: Moving from Silverlight to any other platform isn’t going to be a trivial task. Or, it may be that you’ve been avoiding the problem because you recognize the amount of work required to recreate those applications. If you still have Silverlight applications around, it may be because you haven’t seen the need to make any changes to those applications. Leaving Silverlight: Converting to WPF.Leaving Silverlight: Converting to the Web.Note: This post is part of a series on options for leaving Silverlight as it approaches its end of life. None of those options are perfect so there are trade-offs you’ll have to make. You have several choices when it comes to migrating away from Silverlight-probably more than you realize. ![]() In this post we'll discuss your best options for migrating from Silverlight, and their associated costs and benefits. Migrating from Silverlight is neither easy nor fun, but there are ways to reduce the pain.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |