[BUG] [WPF] Problems with default ActivationForViewFetcher when upgrade from 13.3.2 to 14.1.1

[HavenDV]

Describe the bug
In WPF, when creating any form, an exception is thrown in the constructor after calling the this.WhenActivated extension :
System.ArgumentException: 'Don't know how to detect when Dedoose.Views.MainView is activated/deactivated, you may need to implement IActivationForViewFetcher'
The same behavior is repeated when updating to the latest version 16.2.1

Screenshots

Environment

• ReactiveUI Version: 14.1.1

[glennawatson]

Question I assume you have the wpf nuget package installed.

[HavenDV]

Sorry, the problem is trivial - I updated the ReactiveUI for the main library and forgot to update for the WPF project.

[HavenDV]

Small bug in 16.2.1:
PropertyBindingMixins.OneWayBind shows a nullable warning when using a selector function and a vm property that is not marked nullable.

public static IReactiveBinding<TView, TOut> OneWayBind<TViewModel, TView, TProp, TOut>(this TView view, TViewModel? viewModel, Expression<Func<TViewModel, TProp?>> vmProperty, Expression<Func<TView, TOut>> viewProperty, Func<TProp?, TOut> selector)

I'm assuming you don't need ? for TProp

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.