What is the best practice, where the region manager should be located in views module or in view models module?
On the one hand, it seems that navigation should be controlled by view model, since the view model contains all UI logic.
On the other hand, the regions it is something that belongs to visual representation, and if we will control navigation from the view model, our view model will be coupled to region names defined in views.
Moreover, with view first approach we will need to get the view from IoC container and use this view for navigation. This means that we will need some naming conventions, to get views from IoC in view model methods, i.e. again our view model will be depend on views...
Also, I am not sure, will be view model classes unit testable if it will call the RegionManager methods?
On the one hand, it seems that navigation should be controlled by view model, since the view model contains all UI logic.
On the other hand, the regions it is something that belongs to visual representation, and if we will control navigation from the view model, our view model will be coupled to region names defined in views.
Moreover, with view first approach we will need to get the view from IoC container and use this view for navigation. This means that we will need some naming conventions, to get views from IoC in view model methods, i.e. again our view model will be depend on views...
Also, I am not sure, will be view model classes unit testable if it will call the RegionManager methods?