[glennawatson]

Summary

ReactiveUserControl and ReactiveWindow are now trim and AOT safe. The .NET 11 build no longer uses runtime-async, and the example runs on every Avalonia platform.

• The reactive control and window constructors no longer need [RequiresUnreferencedCode]. They pass the view's ViewModelProperty observable to ReactiveUI's reflection-free WhenActivated overload.
• ReactiveUI.Avalonia and ReactiveUI.Avalonia.Reactive are now marked AOT compatible, so the trim and AOT analyzers check them.
• The ViewRegistrar Activator fallback gains the [RequiresUnreferencedCode] that its callers already carry.
• The .NET 11 assemblies are built without runtime-async, which Mono does not support.
• The example is now a shared library plus Desktop, Browser, Android and iOS heads. The platform packages follow $(AvaloniaVersion).
• Tests run through ReactiveUI.Avalonia.Tests.slnf, because the solution now contains app heads.
• Updates ReactiveUI to 26.0.0, ReactiveUI.Binding.Avalonia to 9.0.0 and TUnit to 1.72.16.

Why

Every view that derived from ReactiveUserControl or ReactiveWindow produced trim warnings under Native AOT, because activation found the view model by reflection. Separately, Avalonia's browser, Android and iOS apps run on Mono, where a runtime-async build can fail.

Breaking changes

None. The constructors lose an attribute, and the public API is otherwise unchanged. This ships as a patch release to keep in step with Avalonia's version numbers.

How this was verified

New tests cover swapping the view model while a control is shown, and the example's desktop, single-view, browser and no-storage paths. The iOS head was compiled for net10.0-ios on a host with the iOS workload. The Browser, Android and iOS apps were not run in a browser, emulator or simulator.

Notes for the reviewer

Start with ViewModelPropertySync.ForwardActivation and the two base constructors. The example split, the platform heads and the public API baseline changes are mostly mechanical. The iOS head builds its iOS target only when BuildAppleHead is true, which defaults to macOS hosts. CI and SonarCloud test only the test projects, because dotnet test asks the app heads for a device.

Checklist

• I have read the Contribute guide
• The PR title follows Conventional Commits
• Tests cover this change, or the summary says why they do not
• New or changed public API has XML documentation

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.42%. Comparing base (0c7c656) to head (f879d84).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #221      +/-   ##
==========================================
+ Coverage   98.31%   99.42%   +1.10%     
==========================================
  Files          51       54       +3     
  Lines        1010     1042      +32     
  Branches      110      114       +4     
==========================================
+ Hits          993     1036      +43     
+ Misses         13        3      -10     
+ Partials        4        3       -1     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud