OpenSilver

In 2014, Userware, founded in 2007 and led by Giovanni Albani, launched CSHTML5, a precursor to becoming OpenSilver. This initiative began efforts to provide a contemporary alternative to Microsoft Silverlight in 2020, focusing on open-source development. As technology progressed and the need for modern web application frameworks grew, CSHTML5 evolved, culminating in the creation of OpenSilver 1.0 in October 2021. OpenSilver aimed to seamlessly integrate Silverlight's legacy capabilities with the demands of modern web development. The inception of OpenSilver was motivated by the discontinuation of Silverlight and the need for a robust solution that allows legacy Silverlight applications to continue functioning in a modern web environment. By providing a path forward for these applications, OpenSilver helps preserve the investment made in Silverlight-based projects while taking advantage of the advancements in web technology. ==Version history and milestones==

OpenSilver integrates three main components: • Compiler - Converts XAML into C# equivalents and copies resources, such as images, to the output folder. • Runtime - Bridges the HTML DOM and the XAML code. • Simulator - Allows developers to debug OpenSilver web applications like desktop applications. OpenSilver's foundation is its ability to take .NET assemblies and XAML files (the building blocks of Silverlight applications) as input and use Blazor to compile them in WebAssembly. Compilation process • XAML to C# conversion - Converts XAML files into C# classes, preserving the layout and styling of Silverlight applications. • .NET to WebAssembly execution - NET assemblies, which include C#, VB.NET, and F# code, can execute in web browsers through two primary modes supported by Mono for WebAssembly: interpreter mode and Ahead-of-Time (AOT) compilation. Runtime environment • WebAssembly Runtime - The compiled code runs within the browser's WebAssembly runtime, generating HTML, CSS, and JavaScript to render the application. • JavaScript Interoperability - A JavaScript layer bridges WebAssembly and the browser's native functions, allowing access to browser APIs that are not directly accessible via WebAssembly. • HTML/CSS Renderer - The browser renders the converted HTML and CSS, including the visual layout, styles, and interactive elements defined in the original XAML. Development and debugging • Facilitate development and testing - The simulator provides a robust and accurate environment mimicking Silverlight's behavior, aiding the transition from Silverlight to OpenSilver. High-level architecture of OpenSilver • Blazor web app (C#) - The entry point creates an OpenSilver application instance and runs the code in WebAssembly. • OpenSilver app (C#, VB, F#, and XAML) - Integrates several mechanisms to run converted Silverlight applications on standard web technologies in modern browsers without plugins. == Development tools ==

OpenSilver offers development tools and a software development kit (SDK) to aid application development. These tools include Visual Studio project templates and the OpenSilver Simulator, simplifying the workflow for developers accustomed to Silverlight or .NET environments. === Supported IDE === === Supported coding editors === NOTE: OpenSilver CLI is supported since OpenSilver 3.0. It allows the creation and manipulation of OpenSilver projects with Command-line interface, which makes it convenient for users to use their preferred code editors for software development. == Licensing ==

OpenSilver is licensed under the MIT License, which allows users to freely use, modify, distribute, and sell the software as long as they include the original copyright and permission notices. == See also ==