Update ReactiveUIPackageVersion to v26

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ReactiveUI (source)	25.1.1 → 26.0.1
ReactiveUI.Core (source)	25.1.1 → 26.0.1
ReactiveUI.Drawing (source)	25.1.1 → 26.0.1
ReactiveUI.Drawing.Reactive (source)	25.1.1 → 26.0.1
ReactiveUI.Maui (source)	25.1.1 → 26.0.1
ReactiveUI.Maui.Reactive (source)	25.1.1 → 26.0.1
ReactiveUI.Reactive (source)	25.1.1 → 26.0.1
ReactiveUI.WPF (source)	25.1.1 → 26.0.1
ReactiveUI.WPF.Reactive (source)	25.1.1 → 26.0.1
ReactiveUI.WinForms (source)	25.1.1 → 26.0.1
ReactiveUI.WinForms.Reactive (source)	25.1.1 → 26.0.1
ReactiveUI.WinUI (source)	25.1.1 → 26.0.1
ReactiveUI.WinUI.Reactive (source)	25.1.1 → 26.0.1

---

Release Notes

reactiveui/reactiveui (ReactiveUI)

v26.0.1

Compare Source

🗞️ What's Changed

🧹 General Changes

• reactiveui/ReactiveUI@8831268 build(deps): update binding to 9.1.0 (#​4533) @​glennawatson

🔗 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

• reactiveui/ReactiveUI@264b88c fix: make view WhenActivated trim and AOT safe; build without runtime-async (#​4532) @​glennawatson

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

🙌 Contributions

💖 Thanks to all the contributors: @​glennawatson

---

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 these updates again.

---

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

---

This PR was generated by Mend Renovate. View the repository job log.