Silverlight made its debut in 2006 with the confusing acronym WPF/E (that’s Windows Presentation Foundation, Everywhere). Indeed the original dream was that a slimmed down version of the .NET Framework could run as a plugin in any browser (including smart phones) and enable developers to wield their weapons of XAML, data-binding, and C# to write line of business apps that would run everywhere. Although it took a few versions to mature, in May of 2011 version 5.0 was released with the features most requested by enterprise users. That was also the year I wrapped up my book about building business applications with Silverlight, titled Designing Silverlight Business Applications (Addison-Wesley, 2012).
In the forward of that book I discussed how the refusal of certain vendors to include the plugin on their smartphones didn’t necessarily mean the demise of Silverlight, but would relegate it to the domain of rich enterprise business applications. HTML5 was still f
At the time I was adamant that Silverlight could still be useful. In hindsight it was mainly due to my frustration with the poor tooling available for building HTML5-based applications. C# and XAML were mature platforms that I could successfully use to scale developers and teams between design and development. I helped author a mobile device management platform that was web-based and switching to Silverlight afforded us about a four times boost in productivity. That’ right – compared to wrestling with cross-browser compatibility and living in AJAX land, Silverlight enabled us to take a concept and bring it to fruition in a quarter of the time. Why on earth would I want to let that go?
My colleague Noel Steiglitz gathered all of the experience and information Wintellect gathered while migrating our customers from Silverlight to modern platforms (both desktop and browser-based) and packaged it in a whitepaper that anyone looking to migrate from Silverlight needs to read. It covers the challenges of migrating to modern platforms and how to determine which platform makes the most sense given the application requirements, whether the target is desktop, Windows 8, or web. He discusses challenges like touch integration and deployment options. There’s a lot more to it but the best part is that it is completely free so I encourage you to visit the download page and grab your copy today. Don’t hesitate to receive your in-depth look at <a href=”https://training.atmosera.com/silverlight-update-xaml-html5?sr
c=jrlblog”>Silverlight Migration Strategies!