Skip to content

24.0.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Jul 06:50
24.0.0
2c6f400

ReactiveUI 24.0.0

ReactiveUI 24 is a major release. ReactiveUI now runs on the allocation-conscious ReactiveUI.Primitives engine, with System.Reactive becoming optional. This changes public type identities and, for the System.Reactive-compatible distribution, namespaces, so review the migration path before upgrading.

Choose your distribution

Both distributions use the same ReactiveUI.Primitives engine, custom schedulers, and optimized sinks. Choose one package family consistently based on the reactive types you want in your public API.

You want Packages Namespace Public reactive types
The new lighter default ReactiveUI, ReactiveUI.WPF, ReactiveUI.WinForms, ReactiveUI.WinUI, ReactiveUI.Maui, ReactiveUI.Blazor, ReactiveUI.AndroidX, etc. ReactiveUI RxVoid, ISequencer, Signal<T>
ReactiveUI APIs using System.Reactive schedulers ReactiveUI.Reactive, ReactiveUI.WPF.Reactive, ReactiveUI.WinForms.Reactive, ReactiveUI.WinUI.Reactive, ReactiveUI.Maui.Reactive, ReactiveUI.Blazor.Reactive, etc. Primarily ReactiveUI.Reactive and ReactiveUI.Reactive.Builder Unit, IScheduler, Subject<T>

New default: ReactiveUI.Primitives types

Keeping the existing package names selects the new default distribution. The normal ReactiveUI namespaces remain, but these public reactive types change:

  • System.Reactive.Concurrency.IScheduler becomes ReactiveUI.Primitives.Concurrency.ISequencer.
  • System.Reactive.Unit becomes ReactiveUI.Primitives.RxVoid.
  • Subject<T>, BehaviorSubject<T>, and ReplaySubject<T> become Signal<T>, BehaviorSignal<T>, and ReplaySignal<T>.
  • System.Reactive is no longer a transitive dependency. ReactiveUI.Primitives provides Rx-style operators over IObservable<T>, so the default distribution does not require System.Reactive for observable composition. System.Reactive can still coexist with the default packages; choose the .Reactive family when you specifically want ReactiveUI APIs to use System.Reactive's IScheduler compatibility seam (together with Unit and subject interop types).

Use System.Reactive schedulers with ReactiveUI: choose the .Reactive packages

Use the .Reactive packages when you want ReactiveUI itself to accept and expose System.Reactive's IScheduler types. Merely referencing or using System.Reactive elsewhere does not require this distribution. Replace each ReactiveUI package with its matching .Reactive package; for example, use ReactiveUI.Reactive with ReactiveUI.WPF.Reactive instead of ReactiveUI with ReactiveUI.WPF.

The compatibility packages intentionally have distinct type identities. Most ReactiveUI APIs move from ReactiveUI to ReactiveUI.Reactive, builder APIs move to ReactiveUI.Reactive.Builder, and platform XAML/CLR namespace mappings may also need updating. This namespace change is part of why version 24 is a major release.

The .Reactive packages are not the old implementation: they use the same Primitives engine and performance work as the default packages, while exposing System.Reactive 7 types at the interop boundary.

Other changes to know about

  • DynamicData integration moved out of core. Core routing types such as RoutingState, IScreen, and RoutedViewHost remain in the main package. DynamicData-backed routing, change-set, collection, and auto-persist helpers now live in ReactiveUI.Routing, or ReactiveUI.Routing.Reactive for the System.Reactive distribution.
  • Hot MVVM paths are substantially faster. Representative .NET 10 benchmarks showed roughly 3–4× faster WhenAnyValue/ToProperty subscription and emission, with 5–13× less allocation. Both distributions benefit because both run on Primitives.
  • AOT-friendly view activation was added. New IActivatableView.WhenActivated overloads accept an IObservable<object?> ViewModel-change source and avoid reflection and trim warnings.
  • .NET 11 preview targets were added and aligned. MAUI now targets supported .NET 10+ releases; the end-of-life .NET 9 MAUI targets were removed. Existing .NET 9 Windows/WinUI targets remain.
  • Several correctness fixes are included. WhenAnyValue no longer loses a concurrent first change, WPF main-thread scheduling now dispatches correctly from background threads, suspension state is materialized before shutdown persistence, interaction task handlers resume on the captured UI context, and pure ObservableMixins helpers work before builder initialization.
  • Platform fixes are included. WinForms design-mode detection works on .NET Core and for nested controls. The WPF .Reactive package now resolves its XAML namespace and ships the default theme required by ViewModelViewHost.
  • Two internal-looking public sink types were removed. Consumers of ReactiveUI.Internal.SingleValueObservable<T> or SyncExecuteObservable<T> should use the equivalent ReactiveUI.Primitives.Advanced signal types (ReturnSignal<T> and StartSignal<T>).

🗞️ What's Changed

💥 Breaking Changes

✨ Features

♻️ Refactoring

🐛 Fixes

⚡ Performance

🧹 General Changes

📦 Dependencies

📌 Other

🔗 Full Changelog: 23.2.28...24.0.0

🙌 Contributions

🌱 New contributors since the last release: @deeferentleeg, @dwcullop
💖 Thanks to all the contributors: @ChrisPulman, @deeferentleeg, @dwcullop, @glennawatson, @xackus

🤖 Automated services that contributed: @Copilot, @renovate[bot]

Contributors

renovate, ChrisPulman, and 4 other contributors
Assets 25
Loading