WinUI 3¶

Run the complete page example.

Add ReactiveUI.WinUI to your WinUI 3 application project. It brings ReactiveUI and, through it, ReactiveUI.Binding.

dotnet add package ReactiveUI.WinUI

ReactiveUI.WinUI also ships as ReactiveUI.WinUI.Reactive, built from the same source, for an app that uses System.Reactive.

Configure ReactiveUI at startup¶

Call WithWinUI on the app builder once, in your Application's OnLaunched, before you create your main window. RegisterView<TView, TViewModel> registers a view alongside it, so the router or a view host can resolve it.

_ = RxAppBuilder.CreateReactiveUIBuilder()
    .WithWinUI()
    .RegisterView<StationListPageView, StationListPageViewModel>()
    .RegisterView<StationDetailPageView, StationDetailPageViewModel>()
    .RegisterView<AlertView, AlertViewModel>()
    .ConfigureViewLocator(static locator => locator.Map<SensorMaintenanceViewModel, SensorMaintenanceView>())
    .BuildApp();

ConfigureViewLocator maps a view to its view model by hand, for a view that implements only the non-generic IViewFor.

WithWinUI registers the WinUI view hosts, the activation fetcher and the dispatcher-backed main-thread sequencer. RxAppBuilder covers the builder and RegisterView in depth, and WinUI 3 covers everything you build with the package: ReactivePage<T> and ReactiveUserControl<T>, showing a router's current page, and binding with Bind, OneWayBind and BindCommand.

The compelling example walks through a first view model and view. There is no ReactiveUI.Validation code in this installation's example project; see Validation for validation rules on a view model.