OpenSilver 3.3: Blazor Components Now Run Directly Inside XAML Applications
Userware today released OpenSilver 3.3, introducing native integration between XAML and Blazor. Developers can now embed Blazor components from libraries like DevExpress, Syncfusion, MudBlazor, Radzen, and Blazorise directly inside XAML applications, with no JavaScript bridges or performance overhead.
OpenSilver is an open-source framework that runs WPF-style C# and XAML applications in web browsers via WebAssembly. It supports deployment to iOS, Android, Windows, macOS, and Linux through .NET MAUI Hybrid. With version 3.3, developers can also leverage the Blazor component ecosystem while keeping XAML as their primary UI technology.
“Blazor has an incredible component ecosystem. XAML has a powerful layout and binding system that developers love,” said Giovanni Albani, CEO of Userware. “With 3.3, you don’t have to choose. Use XAML where it excels, drop in Blazor components where you need them. Your ViewModels and architecture stay the same.”
How It Works
Because OpenSilver renders UI elements to the HTML DOM (just like Blazor), both technologies share the same rendering model. Developers have two options for integration:
- Option1: Inline Razor code – Write Razor markup directly inside XAML files within <RazorComponent> tags. XAML markup extensions like {Binding} and {StaticResource} work directly in the embedded Razor code.
- Option 2: Reference .razor files – Create standard Blazor components in .razor files and reference them from XAML using: <RazorComponent ComponentType=”{x:Type local:MyBlazorComponent}”/>
Access to the Blazor Ecosystem
OpenSilver 3.3 provides immediate access to popular Blazor component libraries including DevExpress, Syncfusion, MudBlazor, Radzen, and Blazorise. No special builds or glue code required: add the NuGet package, reference the component, and use it in XAML.
“We’re pleased to see OpenSilver enabling new scenarios for DevExpress Blazor components,” said Alexander Chuev, Blazor Team Product Manager at DevExpress. “Developers now have more options for building modern applications with familiar tools.”
A Modernization Path
For enterprises maintaining WPF or Silverlight applications, Blazor integration offers a practical modernization approach. Rather than rewriting entire applications, teams can replace individual controls with modern Blazor equivalents while keeping their existing architecture intact.
The capability is already being used in production. Cegid, a European business software company, recently integrated the DevExpress RichEdit Blazor component into their Tax Flex application to add Word document editing capabilities. Tax Flex is a large XAML codebase that was migrated from Silverlight to OpenSilver.
“Adding the RichEdit component was straightforward,” said Pascal Olivier, R&D Director at Cegid’s Finance Innovation Factory. “We added the NuGet package, placed the component in our XAML, connected it to our existing ViewModel, and it worked.”
Also in This Release
OpenSilver 3.3 includes significant updates beyond Blazor integration:
- Platform support: Full compatibility with .NET 10 (released November 2025), C# 14, and Visual Studio 2026.
- Responsive layouts: A new Responsive markup extension enables adaptive Uis in XAML:
<Border Width=”{Responsive Mobile=200, Desktop=500}” Visibility=”{Responsive Mobile=Collapsed, Desktop=Visible}”/>
- WPF compatibility: Complete CommandManager and RoutedCommand infrastructure, template selectors, preview/tunneling events, and numerous API additions including WeakEventManager, DependencyPropertyDescriptor, and a rewritten CollectionViewSource.
- Modern layout properties: Grid and StackPanel now support BorderThickness, BorderBrush, Spacing, Padding, and CornerRadius, along with MAUI-style shorthand syntax for row and column definitions.
Try It
Live samples demonstrating Blazor component integration are available in the OpenSilver Showcase, with source code for each example:
- Web: OpenSilverShowcase.com
- iOS: App Store
- Android: Google Play
Availability
OpenSilver 3.3 is available now on NuGet.org, in the Visual Studio and VS Code marketplaces (with XAML designer and project templates), and online at XAML.io for browser-based development without installation.
Blazor integration documentation and limitations: doc.opensilver.net/documentation/general/opensilver-blazor.html
The post OpenSilver 3.3: Blazor Components Now Run Directly Inside XAML Applications appeared first on SD Times.
Tech Developers
No comments