OpenSilver 3.3 brings native Blazor into XAML apps

OpenSilver has released version 3.3, adding support for running Blazor components directly inside XAML applications.

The open-source framework targets developers who maintain applications built with WPF-style C# and XAML. OpenSilver runs these applications in web browsers via WebAssembly. It also supports deployment to iOS, Android, Windows, macOS, and Linux through .NET MAUI Hybrid.

OpenSilver 3.3 adds what the company describes as native integration between XAML and Blazor. The release allows developers to embed Blazor components from third-party libraries in XAML views. OpenSilver said this works without JavaScript bridges or wrappers.

Libraries named in the release include DevExpress, Syncfusion, MudBlazor, Radzen, and Blazorise. OpenSilver said the approach also works with other Blazor component libraries.

"Blazor has an incredible component ecosystem. XAML has a powerful layout and binding system that developers love," said Giovanni Albani, CEO, 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

OpenSilver said it renders UI elements to the HTML DOM. The company said Blazor uses the same rendering model. OpenSilver positions this as the basis for integrating the two technologies within a single runtime.

Developers have two integration methods. One option places Razor markup inside XAML files via RazorComponent tags. OpenSilver said XAML markup extensions, including Binding and StaticResource, work inside the embedded Razor code. A second option references standard .razor files from XAML by pointing to a component type.

Third-party components

OpenSilver said developers can add a component library via NuGet and then reference components from XAML. The company said this does not require special builds.

DevExpress referenced the integration as a new route for use of its Blazor components.

"We're pleased to see OpenSilver enabling new scenarios for DevExpress Blazor components," said Alexander Chuev, Blazor Team Product Manager, DevExpress. "Developers now have more options for building modern applications with familiar tools."

Modernisation focus

Userware also framed the release as a path for teams maintaining WPF or Silverlight applications. The company said the integration makes it possible to replace individual controls while keeping an existing architecture.

OpenSilver said the approach already appears in production use at Cegid. The company said Cegid integrated the DevExpress RichEdit Blazor component into its Tax Flex application. OpenSilver said Tax Flex previously migrated from Silverlight to OpenSilver and that the component added Word document editing.

"Adding the RichEdit component was straightforward," said Pascal Olivier, R&D Director, 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."

Platform updates

Beyond Blazor integration, OpenSilver 3.3 adds support for .NET 10, C# 14, and Visual Studio 2026, according to the company.

The release also introduces a Responsive markup extension for adaptive layouts in XAML. OpenSilver also listed WPF compatibility work, including additions around CommandManager and RoutedCommand, template selectors, preview events, and API updates such as WeakEventManager and DependencyPropertyDescriptor. The company also said it rewrote CollectionViewSource.

OpenSilver said it also updated layout properties for Grid and StackPanel. It listed BorderThickness, BorderBrush, Spacing, Padding, and CornerRadius. The company also referenced MAUI-style shorthand syntax for row and column definitions.

Userware said OpenSilver remains available as an open-source project and through distribution channels including NuGet. The company said developers can access live samples that demonstrate the Blazor component integration, including examples that use third-party component libraries.