Silverlight developers runtime6/29/2023 Microsoft already explains in the EOL page that the runtime installer will be available only up to October 2021. EOL means the vendor has no obligation to keep anything online. I had proposed Silverlight for a new project only a few months earlier, so I remember the embarrassment.ĭisappearing SDK links? That's to be expected and may even be on purpose. It wasn't even a sudden change back in 2012, when Microsoft announced they'd discontinue Silverlight. The APIs are very different from SL, instead of XAML you work with HTML, but that means you also get the latest browser features and Web technologies out of the box.įinally, one could completely rewrite the application in a modern SPA JavaScript framework like React, Angular or Vue. This is perhaps the easiest option, requiring minimal rewrite but also not offering all the benefits of a modern platform.Īnother option is to move to Blazor and specifically Blazor WASM. This means it can run on all modern browsers and OS.NET Rocks show 1698 discusses OpenSilver and how to migrate. One option is to migrate to OpenSilver, an open-source implementation of Silverlight on WASM that doesn't require plugins. You may be able to use them to keep your application alive for a while but you really have to start migrating. The answer to this possibly duplicate question shows where to find the SL 5 Developer runtime and links to the SL Releases page which includes the last SL 5 download from January 2019. No other browser supports the plugins required for SL5 (or plugins in general) The reason you can't find Silverlight tools in VS 2015 and later is they were never released.īy now, SL 5 only runs on IE 10/11 on Windows 7. It already reached End-Of-Support in January 2020. Silverlight was discontinued in 2012 and reaches End-Of-Life in one year+1 week (October 12, 2021). No matter where you find the tooling, you have to migrate. StackOverflow still delivers, fixes my Rollup.js problem.Remote Desktop on Mac failes to connect with 0x207 error.The tension behind this is that ultimately developers and designers need to work on the same applications, so this remains a fascinating contest. No, not the one in AIR (nice idea though): Adobe only includes Flash support and the PDF plug-in. Actually the whole Silverlight on the desktop story is confused, since you can also do Silverlight Mesh-Enabled Web Applications, or stick Silverlight content in a desktop gadget or other embedded browser. Developers need a way to have these run with more local permissions, subject to user consent, otherwise they will turn to Adobe AIR. Microsoft does have a problem with Silverlight out of the browser. That’s going to be further reinforced by Visual Studio 2010 which gets full visual designer support, plus of course Silverlight 3.0. NET runtime is Silverlight’s big advantage and this time the tools tip the balance towards Microsoft (Visual Studio) – not for everyone, but for the substantial Microsoft platform community. ![]() The tools: Adobe’s designer tools are a de facto standard, target Flash, and run on the Mac.ĭeveloper is another matter. Flash is already good enough so why bother?ģ. Designers are pragmatic and target the runtime that is already deployed most broadly, ie. There are several reasons why Silverlight struggles to get designer attention, including:ġ. I posed this question in a post over on itjoblog.
0 Comments
Leave a Reply. |