Skip to content

Update dependency ReactiveUI.WPF to v28 - #6171

Open
dependencyupdates[bot] wants to merge 1 commit into
masterfrom
renovate/reactiveui.wpf-28.x
Open

dependencyupdates[bot] wants to merge 1 commit into
masterfrom
renovate/reactiveui.wpf-28.x

Conversation

@dependencyupdates

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ReactiveUI.WPF (source) 22.3.1 → 28.0.0 age adoption passing confidence

Release Notes

reactiveui/reactiveui (ReactiveUI.WPF)

v28.0.0

Compare Source

Overview

ReactiveUI 28.0.0 moves every reflection-based and AOT-unsafe API out of the core and platform packages into new opt-in .Unsafe packages. The main packages are now clean for trimming and Native AOT. ReactiveUI.SourceGenerators 7.1.0 adds compile-time replacements for the APIs that moved, so most apps can drop the reflection instead of carrying it.

💥 Why this release is breaking

Before 28.0.0, the core packages shipped APIs marked [RequiresUnreferencedCode] and [RequiresDynamicCode]. On Apple platforms the ...Unsafe view hosts raised IL3050 warnings in every Native AOT app, even apps that never used them, and the app could not suppress those warnings (#​4561).

The fix is to keep those APIs out of the assemblies that every app references. If your code calls one of them, it no longer compiles against the core package alone. You have two ways forward:

  1. Add the matching .Unsafe package. The types keep their names and namespaces, so in most cases a package reference and a rebuild is all you need.
  2. Switch to the compile-time alternative in ReactiveUI.SourceGenerators 7.1.0, described below. This is the recommended path for trimmed and Native AOT apps.
New opt-in packages
Package .Reactive variant
ReactiveUI.Unsafe ReactiveUI.Unsafe.Reactive
ReactiveUI.Wpf.Unsafe ReactiveUI.Wpf.Unsafe.Reactive
ReactiveUI.Winforms.Unsafe ReactiveUI.Winforms.Unsafe.Reactive
ReactiveUI.WinUI.Unsafe ReactiveUI.WinUI.Unsafe.Reactive
ReactiveUI.Maui.Unsafe ReactiveUI.Maui.Unsafe.Reactive
ReactiveUI.AndroidX.Unsafe ReactiveUI.AndroidX.Unsafe.Reactive

These packages are not trimmable and not AOT compatible by design. Apps that stay trim and AOT safe do not need them.

What moved, and what to use instead
API that moved Now in Compile-time alternative
ViewModelViewHostUnsafe, RoutedViewHostUnsafe, AutoDataTemplateBindingHookUnsafe, ViewModelControlHostUnsafe, RoutedControlHostUnsafe The platform .Unsafe package (ReactiveUI.Unsafe for Apple and Android) ViewModelViewHost and RoutedViewHost with [RegisterView]
RegisterViewsForViewModels(assembly) and WithViewsFromAssembly(assembly) ReactiveUI.Unsafe [RegisterView] and RegisterGeneratedViews()
AutoPersist and AutoPersistCollection overloads without metadata ReactiveUI.Unsafe [AutoPersist] and the overloads that take AutoPersistMetadata
ReactiveProperty<T>.AddValidation(() => Property) ReactiveUI.Unsafe [ReactiveValidation], or the new AddValidation(displayName, params ValidationAttribute[])
Untyped ISuspensionHost members: GetAppState<T>(), ObserveAppState<T>(), SetupDefaultSuspendResume() ReactiveUI.Unsafe ISuspensionHost<TAppState> with a source-generated JsonTypeInfo<TAppState>
Android ControlFetcherMixins (WireUpControls, GetControl), ResolveStrategy, LayoutViewHostUnsafe, ReactiveViewHostUnsafe ReactiveUI.Unsafe and ReactiveUI.AndroidX.Unsafe [WireUpControls]
Suspension drivers

ISuspensionDriver now only has the JsonTypeInfo<T> members. The reflection-based LoadState() and SaveState<T>(T) moved to a new interface, IUnsafeSuspensionDriver, in ReactiveUI.Unsafe.

  • A custom driver that only needs the typed members needs no change beyond removing the two reflection methods if you no longer want them.
  • A custom driver that must keep reflection-based serialization should implement IUnsafeSuspensionDriver.
  • DummySuspensionDriverUnsafe, BundleSuspensionDriverUnsafe (Android) and AppSupportJsonSuspensionDriverUnsafe (Apple) are the reflection-capable twins of the built-in drivers.
  • With ReactiveUI.Unsafe referenced, the untyped SetupDefaultSuspendResume() still finds the driver the platform registered, and the untyped GetAppState<T>() still loads state for a host that was set up through the typed overload.
Other changes in this release
  • New reflection-free ReactivePropertyMixins.AddValidation(params ValidationAttribute[]) and AddValidation(string? displayName, params ValidationAttribute[]) in the core package.
  • IReactiveUIBuilder.WithViewsFromAssembly is no longer an interface member. It is an extension method in ReactiveUI.Unsafe.
  • ReactiveUI.Binding is updated to 12.1.0 and ReactiveUI.Primitives to 10.2.3.

✨ Automating the wiring with ReactiveUI.SourceGenerators 7.1.0

ReactiveUI.SourceGenerators 7.1.0 adds four generators. Each one replaces a piece of wiring that used to need reflection at run time, or careful hand-written code, with code generated at build time.

[RegisterView]: view registration without assembly scanning

Mark each view. The generator writes one RegisterGeneratedViews() extension method that registers them all. [RegisterView<TViewModel>] also takes a contract and a singleton flag.

[RegisterView]
public sealed class PlaylistView : IViewFor<PlaylistViewModel> { /* ... */ }

[RegisterView<PlaylistViewModel>(Contract = "compact", IsSingleton = true)]
public sealed class CompactPlaylistView : IViewFor<PlaylistViewModel> { /* ... */ }

// At startup, in place of WithViewsFromAssembly(...):
builder.RegisterGeneratedViews().BuildApp();
[AutoPersist]: persistence metadata without reflection

Add [AutoPersist] to a partial [DataContract] class. The generator writes a static AutoPersistMetadata property that lists the [DataMember] properties, so AutoPersist never has to inspect the type at run time.

[DataContract]
[AutoPersist]
public sealed partial class Note : ReactiveObject
{
    [DataMember]
    public string Title { get; set => this.RaiseAndSetIfChanged(ref field, value); } = string.Empty;
}

note.AutoPersist(SaveAsync, Note.AutoPersistMetadata, TimeSpan.FromSeconds(3));
[ReactiveValidation]: DataAnnotations on ReactiveProperty<T> without expressions

Add [ReactiveValidation] to a partial class. The generator writes a ConfigureValidation() method that applies each property's validation attributes and its [Display(Name = ...)] through the new reflection-free AddValidation overload.

[ReactiveValidation]
public sealed partial class SignupModel
{
    public SignupModel() => ConfigureValidation();

    [Display(Name = "Student Name")]
    [Required(ErrorMessage = "Enter the student's name.")]
    public ReactiveProperty<string> Name { get; } = new(string.Empty);

    [Range(8, 18)]
    public ReactiveProperty<int> Age { get; } = new(5);
}
[WireUpControls]: Android control wiring without resource reflection

The attributes live in the ReactiveUI.SourceGenerators.Android namespace. The generator writes a WireUpControls() method that calls FindViewById<T>(Resource.Id.*) for each control property. Fragments get WireUpControls(View rootView). Use [WireUpResource("id")] when the resource name differs from the property name, and [IgnoreResource] to skip a property.

[WireUpControls]
public sealed partial class AbsenceActivity : ReactiveAppCompatActivity<AbsenceViewModel>
{
    [WireUpResource("statusLabel")]
    public TextView? StatusText { get; set; }

    [IgnoreResource]
    public TextView? ScratchLabel { get; set; }

    protected override void OnCreate(Bundle? savedInstanceState)
    {
        base.OnCreate(savedInstanceState);
        SetContentView(Resource.Layout.activity_absence);
        WireUpControls();
    }
}

Runnable versions of all four examples are in src/examples/Documentation.

🗞️ What's Changed

💥 Breaking Changes
🐛 Fixes
📦 Dependencies

🔗 Full Changelog: reactiveui/ReactiveUI@27.0.1...28.0.0

🙌 Contributions

💖 Thanks to all the contributors: @​glennawatson

Automated services that contributed: renovate[bot]

v27.0.1

Compare Source

Overview

ReactiveUI 27.0.1 fixes Apple application builds that fail during .NET 11 trimming with IL2037 and NETSDK1144, and replaces legacy linker preservation with explicit .NET trimming dependencies.

Apple and Android trimming
  • Keep UIKit and Android binding properties, methods and events through DynamicDependency annotations on reachable platform registration methods.
  • Remove dummy linker methods and invalid constructor preservation on static classes in both ReactiveUI variants.
  • Update the registration and reflection examples to show modern trimming practices. Retain the public PreserveAttribute type for binary compatibility.
Dependency maintenance
  • Inherit the organisation's shared Renovate update rules.

🗞️ What's Changed

🐛 Fixes
🧹 General Changes

🔗 Full Changelog: reactiveui/ReactiveUI@27.0.0...27.0.1

🙌 Contributions

💖 Thanks to all the contributors: @​glennawatson

v27.0.0

Compare Source

ReactiveUI 27.0.0 moves modern .NET support to .NET 10 and .NET 11, removes the .NET 8, .NET 9 and .NET Framework 4.6.2 targets, and updates the Primitives, Binding, SourceGenerators and Splat dependencies. This is a major release because applications targeting the removed frameworks must retarget before upgrading, and projects that disable implicit usings must explicitly import the ReactiveUI namespaces they use.

.NET 8 and .NET 9 removal

.NET 8 and .NET 9 both reached Microsoft's end of support on 10 November 2026. Microsoft no longer provides security fixes, servicing updates or technical support for either version. ReactiveUI's modern .NET targets are now .NET 10 and .NET 11, including their supported UI platform variants. See Microsoft's end-of-support announcement and the .NET support policy.

.NET Framework 4.6.2 (net462) removal

Microsoft lists the end of support for .NET Framework 4.6.2 as 12 January 2027. We are removing this target ahead of that deadline as part of the same compatibility change. This reduces the legacy build and dependency combinations we maintain. Packages that provide .NET Framework assets target net47, net471, net472, net48 and net481; available targets vary by package and UI platform. See Microsoft's .NET Framework support policy.

Implicit usings respect your project settings

ReactiveUI's transitive package imports now respect the consuming project's ImplicitUsings setting. Projects that set it to false or disable, or leave it unset, must add explicit using directives for the ReactiveUI and binding namespaces they use. Projects using true or enable retain the automatic imports. This applies to the lean, System.Reactive and WPF package imports. See the change and migration details.

Dependencies and platform updates

  • Updated Splat to 22.0.1, ReactiveUI.Primitives to 10.0.0, ReactiveUI.Binding to 10.0.0 and ReactiveUI.SourceGenerators to 5.0.0. These dependency releases have their own version numbers; their major versions do not need to match ReactiveUI's version.
  • Updated framework-specific dependencies and build tooling while preserving intentional compatibility pins.
  • Updated the iOS documentation app to UIKit's scene lifecycle and aligned Apple example builds with the current SDK toolchain. The .NET 10 macOS deployment minimum is preserved.
  • Aligned analyzer settings with ReactiveUI.SourceGenerators, removed Roslynator and cleaned up unused central package entries and redundant explicit ValueTuple references. Remaining .NET Framework targets already provide ValueTuple.

Upgrading

Retarget .NET 8 or .NET 9 applications to .NET 10 LTS or .NET 11, including the matching platform target for UI applications. For .NET Framework applications, prefer 4.8 or 4.8.1 where supported by your Windows version. Update the ReactiveUI packages used by your application together and review the dependency release notes when upgrading.

If you cannot retarget yet, keep using a compatible ReactiveUI 26.x version while planning the migration. Staying on an older package does not extend Microsoft's runtime support. As with Splat's framework transition, removing these targets lets us focus maintenance and dependency updates on the remaining framework combinations.

🗞️ What's Changed

💥 Breaking Changes
🐛 Fixes
🧹 General Changes
📦 Dependencies

🔗 Full Changelog: reactiveui/ReactiveUI@26.0.1...27.0.0

🙌 Contributions

💖 Thanks to all the contributors: @​glennawatson

🤖 Automated services that contributed: renovate[bot]

v26.0.1

Compare Source

🗞️ What's Changed

🧹 General Changes

🔗 Full Changelog: reactiveui/ReactiveUI@26.0.0...26.0.1

🙌 Contributions

💖 Thanks to all the contributors: @​glennawatson

v26.0.0

Compare Source

Summary

ReactiveUI 26.0.0 is a major version because the .NET 11 assemblies are built without runtime-async. The public API does not change.

Why runtime-async is off
  • In .NET 10 and older, the C# compiler adds a state machine to each async method. The state machine stores the local variables and tracks where to resume after each await.
  • .NET 11 adds a feature called runtime-async. The runtime does this work instead, so async code can run faster.
  • ReactiveUI 25.x built the .NET 11 assemblies with runtime-async on. The .NET 8 to 10 and .NET Framework assemblies never used it.
  • The feature needs a runtime that supports it. CoreCLR does, and Mono does not.
  • Blazor WebAssembly runs on Mono unless you opt into CoreCLR. Avalonia's browser apps, WASI, Android API levels 21 to 23, and apps that set UseMonoRuntime=true also run on Mono.
  • ReactiveUI built with runtime-async can fail in every app that runs on Mono.
  • A NuGet package ships one build for every runtime, so ReactiveUI leaves the feature off. This matches ReactiveUI.Binding 9.0.0 and Refit 16.0.0.
  • Apps that target .NET 10 or older are not affected. Apps on .NET 11 that run on CoreCLR do not get the speed gain inside ReactiveUI's own async code.
  • You can turn on runtime-async in your own app if it runs only on CoreCLR.
Other changes
  • View WhenActivated is now trim and AOT safe. It watches the view's ViewModel through the registered ICreatesObservableForProperty plugin, as the binding source generator does, instead of reflection. The [RequiresUnreferencedCode] attribute is gone from every view WhenActivated overload, including the WPF ones, so views that call this.WhenActivated(...) publish with Native AOT without trim warnings.
  • ReactiveUI.Binding is updated to 9.0.0. That release also fixes BindCommandUnsafe keeping bindings it had replaced (reactiveui/ReactiveUI.Binding.SourceGenerators#163).

🗞️ What's Changed

🐛 Fixes

🔗 Full Changelog: reactiveui/ReactiveUI@25.1.1...26.0.0

🙌 Contributions

💖 Thanks to all the contributors: @​glennawatson

v25.1.1

Compare Source

🗞️ What's Changed

🧹 General Changes
📦 Dependencies

🔗 Full Changelog: reactiveui/ReactiveUI@25.1.0...25.1.1

🙌 Contributions

💖 Thanks to all the contributors: @​glennawatson

🤖 Automated services that contributed: renovate[bot]

v25.1.0

Compare Source

🗞️ What's Changed

🧹 General Changes
📦 Dependencies

🔗 Full Changelog: reactiveui/ReactiveUI@25.0.1...25.1.0

🙌 Contributions

💖 Thanks to all the contributors: @​glennawatson

🤖 Automated services that contributed: renovate[bot]

v25.0.1

Compare Source

Summary

ReactiveUI 25.0.1 adds back the ability to ask an interaction as an observable through IInteraction<TInput, TOutput>. ReactiveUI 25.0.0 removed it by accident.

  • IInteraction<TInput, TOutput>.Handle(input) returns IObservable<TOutput>, as it did in ReactiveUI 24.
  • Interaction<TInput, TOutput>.WhenHandled(input) returns the question as an IObservable<TOutput>.
  • new Interaction<TInput, TOutput>(handlerScheduler) runs each handler on that scheduler, such as RxSchedulers.MainThreadScheduler.
  • Interaction<TInput, TOutput>.Handle(input) still returns Task<TOutput>, so code written against 25.0.0 keeps compiling.

The change comes from ReactiveUI.Binding 8.6.0. The migration guide shows how to use each call.

🗞️ What's Changed

🧹 General Changes

🔗 Full Changelog: reactiveui/ReactiveUI@25.0.0...25.0.1

🙌 Contributions

💖 Thanks to all the contributors: @​glennawatson

v25.0.0

Compare Source

Summary

ReactiveUI 25.0.0 is a major version. Binding moves to a source-generator-first library, the ReactiveUI source generators now come with every install, and the documentation has been rebuilt. Most apps that use ReactiveObject and the usual binding calls keep compiling, but read the breaking changes below before you upgrade.

Binding moves to ReactiveUI.Binding
  • Property observation and binding now run on ReactiveUI.Binding. It generates the code at build time, so it works with trimming and NativeAOT.
  • WhenAny*, WhenAnyValue, ObservableForProperty, Bind, OneWayBind, BindTo, BindCommand, InvokeCommand, BindInteraction, ToProperty and ObservableAsPropertyHelper<T> keep their names. They now come from ReactiveUI.Binding, which ReactiveUI brings in for you. Existing using ReactiveUI; code keeps compiling.
  • If the generator cannot read a property path, use the matching ...Unsafe overload.
  • ReactiveUI's old reflection-based observation and binding engine is removed. That is about 190,000 fewer lines, and far fewer trimming warnings.
  • View location, view hosts, templates, routing, activation and validation presentation stay in ReactiveUI.
  • The default view hosts on WPF, WinForms, WinUI, MAUI, Apple and Android find views without reflection and are AOT safe. Each has an ...Unsafe twin that also asks the service locator.
  • Routing reports navigation through plain observables of values.
  • The migration guide lists the removed types, the behaviour changes and what to change in your code.
Source generators come with ReactiveUI
  • ReactiveUI.Core now brings ReactiveUI.SourceGenerators. Both ReactiveUI and ReactiveUI.Reactive depend on Core, so every project gets the generators with no extra package.
  • [Reactive], [ReactiveCommand], [ReactiveCollection], [BindableDerivedList] and [IReactiveObject] generate your view model properties and commands at build time. This is now the recommended way to write view models.
  • If your project references an older ReactiveUI.SourceGenerators package directly, restore fails with NU1605. Remove that reference, or move it to 4.0.0 or later.
  • [ObservableAsProperty] and [IViewFor] now come from ReactiveUI.Binding.
New documentation and examples
  • The documentation website at https://reactiveui.net/documentation/reactiveui and its related pages have been rewritten.
  • src/examples/Documentation has a runnable example for every public class and method, one project per website page. The website quotes these examples, and each one checks its printed output, so the docs stay in step with the code.
  • Platform examples cover WPF, WinForms, WinUI, MAUI, Blazor, Android and Apple.
  • These examples replace the old reactiveui/ReactiveUI.Samples repository, which is now archived.
Known issues
  • Interaction.Handle returns Task<TOutput> instead of IObservable<TOutput>. This change was not intended.
Other changes
  • Many bug fixes across Android, Apple, MAUI, WPF, WinUI, routing, suspension, the app builder and ReactiveRecord. The full list is below.
  • Android and iOS device tests now run through dotnet test --device.

🗞️ What's Changed

💥 Breaking Changes
🐛 Fixes
🧹 General Changes
✅ Tests
📝 Documentation

🔗 Full Changelog: reactiveui/ReactiveUI@24.3.0...25.0.0

🙌 Contributions

💖 Thanks to all the contributors: @​glennawatson

v24.3.0

Compare Source

🗞️ What's Changed

🐛 Fixes

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Commands to ignore dependencies

You can trigger dependency actions by commenting on this PR:

  • @particularbot ignore this major version
  • @particularbot ignore this minor version
  • @particularbot ignore this dependency

@dependencyupdates dependencyupdates Bot added dependencies Pull requests that update a dependency file NuGet labels Nov 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file NuGet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants