OpenSilver 3.3 has been released by Userware, bringing a major update to the open-source framework for creating cross-platform applications with C# and XAML. The new version allows developers to run Blazor web components directly inside XAML applications, making it easier to integrate modern web features into desktop and native apps. OpenSilver 3.3 was officially announced on January 27, and SDKs for Visual Studio and Visual Studio Code are available for download from opensilver.net.

Blazor Components Now Run Inside XAML Applications

With the latest update, Blazor components can now be embedded directly into the XAML visual tree. This means that components like MudBlazor data grids or DevExpress rich text editors can be dropped into a XAML app without complex JavaScript bridges or interop wrappers. The components share the same DOM and runtime environment as the host application, simplifying development and improving performance.

This integration allows developers to combine the best of both worlds—using Blazor’s rich web UI components within traditional XAML-based applications. Since OpenSilver runs on WebAssembly for browsers and on .NET MAUI Hybrid for native platforms, the same codebase can target web, iOS, Android, Windows, macOS, and Linux, providing a unified development experience.

Design-Time Limitations and Workarounds

One important note from Userware is that Razor code embedded inside XAML may show errors during design time. However, these errors are only at design time and won’t affect the actual build or runtime. Developers can work around this by wrapping Razor code within CDATA sections, placing it in separate .razor files, or filtering out build-only errors in their development environment.

This approach helps maintain a smooth workflow while still leveraging Razor syntax within XAML apps. As the framework evolves, these limitations might be addressed, but for now, developers should be aware of this behavior when designing their interfaces.

OpenSilver itself is an open-source replacement for Microsoft Silverlight, a now-discontinued framework for rich internet applications. Since Silverlight was phased out in 2021, developers maintaining legacy Silverlight or WPF apps can use OpenSilver to modernize their applications gradually. Integrating Blazor components offers a straightforward way to replace outdated controls with modern, web-based UI elements, improving user experience without a complete rewrite.

Inspired by

• https://www.infoworld.com/article/4123105/opensilver-3-3-runs-blazor-components-inside-xaml-apps.html

Sources

• opensilver.net
• opensilver.net