A product's vendor has to release security fixes for any vulnerabilities found throughout a product's lifetime.Īny company that wanted to keep working with Silverlight had ample time to download all the tooling before it was removed. More importantly, Silverlight creates a security burden. Silverlight makes it possible to dynamically load Extensible Markup Language (XML) content that can be manipulated through a Document Object Model (DOM) interface, a technique that is consistent with conventional Ajax techniques.
Those downloads and docs have to be migrated or even rewritten each time the web site changes, and take storage and bandwidth. Anyone out there have a suggestion I gather this has become a problem with Firefox, so Im late to the game. It's not just that maintaining downloads and docs isn't free. I want to use Silverlight 64-bit with a mapping program that requires it, but have not been able to get Silverlight to work with Firefox (I have 64-bit Firefox v59.x and W10). Microsoft really did phase Silverlight's removal over 8 years. That's 4 years after SL was discontinued. Even in 2016 the SDK was still available. There's no mention about the SDK, and in fact, removing the SDK download would be a great way to stop people from creating new Silverlight projects. 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.
#GET SILVERLIGHT HOW TO#
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.
#GET SILVERLIGHT WINDOWS#
No other browser supports the plugins required for SL5 (or plugins in general) Download Microsoft Silverlight for Windows now from Softonic: 100 safe and virus free. 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.
0 kommentar(er)
