OpenSilver 3.3 adds native Blazor component support inside XAML applications, allowing cross-platform deployment across web and desktop environments using a single open source codebase.
OpenSilver 3.3, an open-source replacement for Microsoft Silverlight, adds native support for running Blazor components directly inside XAML applications, extending interoperability between the Blazor and XAML development models.
In this release, Blazor components run within the XAML visual tree and share the same DOM and runtime. This removes the separation that previously existed between the two UI frameworks. The integration removes the need for JavaScript bridges or interop wrappers, reducing architectural complexity and associated runtime overhead.
OpenSilver 3.3 supports cross-platform deployment from a single codebase. The framework runs on WebAssembly for browser-based applications and uses .NET MAUI Hybrid for native deployments. Applications built with OpenSilver can run on the Web, iOS, Android, Windows, macOS, and Linux using the same source code.
The update allows developers to reuse existing Blazor components inside XAML applications. Third-party components such as MudBlazor data grids, DevExpress rich text editors, and other standard Blazor components can be embedded directly, allowing existing XAML applications to incorporate Blazor-based UI elements without replacing the full interface layer.
OpenSilver 3.3 also adds support for .NET 10 and C# 14, aligning the framework with upcoming versions of the .NET platform.
The release was unveiled on January 27. SDKs for Microsoft Visual Studio and Visual Studio Code are available for download from opensilver.net. OpenSilver is developed by Userware and is intended for building cross-platform applications using C# and XAML without reliance on proprietary Silverlight tooling.
