{"id":1276,"date":"2021-10-12T18:23:30","date_gmt":"2021-10-12T17:23:30","guid":{"rendered":"https:\/\/www.ituziast.com\/?p=1276"},"modified":"2023-07-09T10:38:26","modified_gmt":"2023-07-09T09:38:26","slug":"opensilver-1-0-released-today-as-silverlight-reaches-end-of-support","status":"publish","type":"post","link":"https:\/\/www.ituziast.com\/index.php\/2021\/10\/12\/opensilver-1-0-released-today-as-silverlight-reaches-end-of-support\/","title":{"rendered":"OpenSilver 1.0 Released Today as Silverlight Reaches End of Support"},"content":{"rendered":"\n

Userware announced today that it has released OpenSilver<\/a> 1.0, as Microsoft Silverlight has reached the end of support. <\/p>\n\n\n\n

What is OpenSilver?<\/strong><\/h2>\n\n\n\n

OpenSilver is a modern, plugin-free, open-source reimplementation of Silverlight, capable of running large, complex legacy applications, as well as newly written C# and XAML applications.  <\/strong><\/p>\n\n\n\n

Developers worldwide have poured great amounts of effort into building countless Silverlight applications over the past 15 years. OpenSilver provides them with an alternative to rewriting them. It lets their existing code run on every browser so that they can leverage their .NET skills and focus on new improvements instead. <\/p>\n\n\n\n

The project is hosted publicly on GitHub<\/a><\/strong> and is actively developed by a large team of full-time developers, funded by Userware and corporations of all sizes investing in the technology to maintain their line-of-business applications.<\/p>\n\n\n\n

Why OpenSilver?<\/strong><\/h2>\n\n\n\n

The company stated that the development of OpenSilver was motivated by the team\u2019s strong belief that developers should not be compelled to rewrite existing applications because of a change in the underlying stack. The thousands of Silverlight applications still in production are a testament to this. Silverlight\u2019s end of life was announced in 2011, as a technical roadblock presented itself: browsers would one day stop allowing plugins. Yet many developers remained committed for over ten years to what they considered to be a valid platform, as it worked just fine for their purposes. OpenSilver has worked on lifting Silverlight\u2019s roadblocks and improving the underlying technology.<\/p>\n\n\n\n

\n

OpenSilver is now mature enough to run complex line-of-business apps<\/p>\nsays Giovanni Albani, CEO of Userware.<\/cite><\/blockquote>\n\n\n\n

\n

We can now offer a modern, enhanced version of Silverlight and expand the realm of possibilities for .NET developers when it comes to web applications.<\/p>\n<\/blockquote>\n\n\n\n

How does it work?<\/strong><\/h2>\n\n\n\n

OpenSilver works just like Silverlight, but without the plugin.  <\/p>\n\n\n\n

Instead of using browser plugins, OpenSilver leverages WebAssembly to run applications directly and securely within the browser\u2019s sandbox. WebAssembly files (.wasm) follow a W3C standard and are natively recognized by all modern browsers, in the same way, JavaScript, HTML, and CSS are.  <\/p>\n\n\n\n

No knowledge of JavaScript, HTML, or CSS is required to build a fully functional web application.  Controller logic written in C# runs in the browser thanks to Microsoft Blazor. As for the presentation layer, OpenSilver adds support for XAML. This makes for a full .NET development experience. <\/p>\n\n\n\n

OpenSilver applications run on every modern browser, across all platforms, including iOS, Android, Windows, MacOS, and Linux.<\/p>\n\n\n\n

How is a Silverlight application migrated to OpenSilver?<\/strong><\/h2>\n\n\n\n

Developers can migrate an existing web application of any size using the OpenSilver Visual Studio extension. The extension helps developers create new projects from their existing code, replacing Silverlight API calls with their OpenSilver equivalent where appropriate. Additional steps are explained in the OpenSilver documentation. <\/p>\n\n\n\n

As companies and developers undertake the porting of their applications, Userware can provide development services to assist during the process or take care of the whole migration with the help of the core team. Every feature implemented for custom development is incorporated into OpenSilver.<\/p>\n\n\n\n

Is OpenSilver missing any features of Silverlight?<\/strong><\/h2>\n\n\n\n

OpenSilver fully supports the core capabilities of the Silverlight engine, including full language support (C#, XAML). Most of the platform APIs are supported, allowing developers to include major C# libraries<\/strong> such as Telerik UI<\/strong>, WCF RIA Services<\/strong>, PRISM<\/strong>, and MEF<\/strong>. Support for additional platform APIs is continuously being added.<\/p>\n\n\n\n

Does OpenSilver offer any improvements over Silverlight?<\/strong><\/h2>\n\n\n\n

OpenSilver can leverage the latest C# language version 9.0<\/strong> and the latest Visual Studio. It supports .NET Standard<\/strong>, .NET 5<\/strong>, and .NET 6<\/strong>, in addition to legacy Silverlight code. OpenSilver is also compatible with all JavaScript libraries, combining the best of both worlds.  <\/p>\n\n\n\n

Additionally, since OpenSilver relies entirely on open standards and runs within the browser\u2019s sandbox, it enjoys wider browser compatibility, can better benefit from browser enhancements and isn\u2019t vulnerable to any security issues that a plugin might introduce.<\/p>\n\n\n\n

Why remain in .NET instead of rewriting in a JavaScript-based framework?<\/strong><\/h2>\n\n\n\n

With Silverlight being discontinued, thousands of companies have been hit with the prospect of having to discard their entire .NET-based front-end applications, and having to begin the arduous task of re-designing and re-developing them in JavaScript\/HTML\/CSS. <\/p>\n\n\n\n

Such complete rewrites are sometimes draining for organizations. They are impactful to resources and costs, and have fluctuating timelines due to unforeseen bugs and intangibles, putting the overall project at significant risk of delay or abandonment. <\/p>\n\n\n\n

Thanks to OpenSilver, this scenario is no longer inevitable, as OpenSilver lets their development continue on their existing .NET codebase. <\/p>\n\n\n\n

According to Darshin Vyas, Userware\u2019s VP of Sales, the main advantage is cost. <\/p>\n\n\n\n

\n

Our clients estimate that a complete rewrite of a medium to the large-sized application would have taken one to two years.<\/p>\nsays Vyas.<\/cite><\/blockquote>\n\n\n\n

\n

There is significant overhead in gathering requirements, developing new specifications, recruiting and onboarding for a new skill set, understanding the existing code, and developing and deploying on a new stack. OpenSilver eliminates this overhead. Some of our clients were able to slash their timeline in half or more while spending a fraction of the rewrite cost. <\/p>\n<\/blockquote>\n\n\n\n

There are several other compelling reasons to stay on .NET, such as the reduced risk of keeping a stable codebase, the possibility to share C# code between the client-side and the server-side, and the availability of .NET libraries such as Telerik. <\/p>\n\n\n\n

What\u2019s next for OpenSilver?<\/strong><\/h2>\n\n\n\n

The team is continually expanding coverage of Silverlight\u2019s platform APIs, and improving OpenSilver\u2019s ability to migrate WPF applications (in addition to Silverlight applications). <\/p>\n\n\n\n

Future versions of OpenSilver will also include new functionality, such as the ability to support applications written in VB.NET, and those using the Microsoft LightSwitch component.<\/p>\n\n\n\n

\n\n\n\n