build(deps): update solution packages and fix compatibility - #432
Merged
Merged
Conversation
- Upgrade ReactiveUI, Binding, Primitives, Avalonia, MAUI, TUnit, and analyzers to current compatible releases. - Migrate generated bindings, navigation locators, clocks, and platform examples to the updated APIs. - Fix analyzer diagnostics and numeric edge cases without suppressions. - Add regression coverage and share WPF dispatcher ownership across gallery tests. - Remove unused Verify.TUnit and give reactive tests a unique report identity.
- Install wasm-tools-net10 in build and deployment workflows before restoring solution workloads.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Dependency updates, compatibility fixes, regression tests, and CI workload configuration.
What is the new behavior?
Update the solution to current compatible ReactiveUI, Binding, Primitives, Avalonia, MAUI, source generator, TUnit, and analyzer releases. Migrate bindings, view locators, generated view contracts, clocks, and activation lifetimes to the updated APIs across the libraries and examples.
Preserve exact color equality and handle non-finite numeric comparisons correctly. Keep gallery resources and runtime tests on one WPF dispatcher. Give the reactive test assembly a unique name so reports no longer collide. Remove the unused Verify.TUnit dependency.
Both CI workflows install
wasm-tools-net10before restoring workloads. The browser example builds self-contained and links its native WebAssembly assets.What is the current behavior?
The solution uses older package versions and API contracts. Upgrading them exposes compilation and analyzer failures, navigation locator incompatibilities, dispatcher ownership problems in runtime tests, and missing browser native-build configuration.
Checklist
Additional information
Validated locally on Windows against the full solution:
dotnet build CrissCross.slnx -c Debug -warnaserror: 0 warnings, 0 errors.dotnet build CrissCross.slnx -c Release -warnaserror: 0 warnings, 0 errors.dotnet test --solution CrissCross.slnx -c Release --coverage --coverage-output-format cobertura -- --report-trx: 731 passed, 0 failed, 0 skipped.git diff --checkpassed.Standalone analyzer formatting remains limited by generated WPF workspace loading; the actual build analyzers are clean. Remote CI has not yet completed.
ReactiveUI.Avalonia 12.1.5 is the compatible current integration line; the older 14.7.1 version targets legacy ReactiveUI/Avalonia dependencies.
Both commits were created through GitHub's authenticated
createCommitOnBranchAPI and have valid GitHub signatures. The final remote tree matches the reviewed staged tree exactly.