Until now we have been working and been very satisfied with the Prism approach for MVVM. Our last large project (WINRT) had analogue to the Adventureworks example, two separate projects (next to some other, but that is irrelevant in this case). One for the Views and one for the Viewmodels. They were "connected" via the ViewModelLocationProvider, that was part of the Prism.Mvvm framework.
Now we have tried to use Prism in a new project and started of with the Prism Template by Brian Lagunas. We notice that Views and Viewmodels are together in the same PCL project. We could not find any substitute for the viewmodellocationprovider.
We want to separate the views from the viewmodels. Two separate teams work on respectively the UI-design in XAML for the views, whereas another team works on the business logic in Viewmodels.
How can the same approach be implemented?