I am in the process of converting a v2 app to use v3.
I have removed the hookups to the generic DataWindow & Control classes & renamed my 'view' classes to line up with the std naming conventions listed for the view & view model locators. In my case the UserControls are all named [VM]View and all
the Windows are named [VM]Window.
I have now hit a snag that I would like some advice about.
I have numerous windows which contain views (usercontrols). IE the control contains most of the vm related controls & the window acts as the 'current' wrapper for the view. This makes it easier to mix views in windows as required.
The snag is that the ViewLocator seems to locate Views before it locates Windows (for a specified view model). EG calling viewLocator.ResolveView(typeof(MyViewModel) returns the type of the usercontrol 'related' the the vm, not the appropriate
I assume that [Up].Views.[VM].Views and [UP].Views.[VM].Controls are higher in the 'lookup list' than [UP].Views.[VM]Window, causing the locator to find the View or Control class before the Window class.
I can 'fix' this by manually registering the appropriate Window class for each view model, but this is cumbersome & requires manual updating each time classes are added/edited/removed.
What is the best way to get the locator to find the Window classes before the UserControl classes?