Thanks, looks like I expressed myself badly. What I meant was something like: another View is configured to be composed by RequestNavigate...
I did not mean that the regions were actually created in designtime (VS or Blend).
I am quite new to Prism and I thought that there was some mechanism so that the Shell (in this case) could show the views (associated with the regions ) by using d:DataContext given for the view.
In my (learning)App the region(s) are defined in the Shell.xaml (<ContentControl prism:RegionManager.RegionName="TheRegion"/>) and the RegionManager.RequestNavigate (Extension) method is executed within the IModule's Initialize() method.
Anyway, it would have been a nice feature if possible though, but perhaps I do not know enough about the dynamics of regions/view associations and have silly wishes.
I did not mean that the regions were actually created in designtime (VS or Blend).
I am quite new to Prism and I thought that there was some mechanism so that the Shell (in this case) could show the views (associated with the regions ) by using d:DataContext given for the view.
In my (learning)App the region(s) are defined in the Shell.xaml (<ContentControl prism:RegionManager.RegionName="TheRegion"/>) and the RegionManager.RequestNavigate (Extension) method is executed within the IModule's Initialize() method.
Anyway, it would have been a nice feature if possible though, but perhaps I do not know enough about the dynamics of regions/view associations and have silly wishes.