You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When doing ViewLocator lookups, if you happen to derive a VM from the MVVM Framework's base type instead of ViewModelBase, ViewLocator.Match will fail causing ViewLocator.Build to never happen. It's not the most straightforward thing to debug from personal experience.
Describe the solution you'd like
Remove ViewModelBase from the project templates, but first check if people are actually commonly extending this with properties/methods instead of leaving it empty. If it's empty, then there's no added benefit over deriving directly from the MVVM framework's base type as you're tightly coupled to this.RaiseAndSetIfChanged, etc anyways.
Describe alternatives you've considered
Change ViewLocator.Match to match against the Mvvm Framework's base INPC type instead of ViewModelBase
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When doing ViewLocator lookups, if you happen to derive a VM from the MVVM Framework's base type instead of
ViewModelBase
,ViewLocator.Match
will fail causingViewLocator.Build
to never happen. It's not the most straightforward thing to debug from personal experience.Describe the solution you'd like
Remove
ViewModelBase
from the project templates, but first check if people are actually commonly extending this with properties/methods instead of leaving it empty. If it's empty, then there's no added benefit over deriving directly from the MVVM framework's base type as you're tightly coupled tothis.RaiseAndSetIfChanged
, etc anyways.Describe alternatives you've considered
Change
ViewLocator.Match
to match against the Mvvm Framework's base INPC type instead ofViewModelBase
Additional context
No response
The text was updated successfully, but these errors were encountered: