Thanks for your reply, these are indeed some very useful links that you have provided. It took me a while to go through them, but did learn a lot from these links.
"Too many regions in my shell" is in perticular very close to what I was looking at, but I was not exactly able to get this working in my previous try when I tried to
create a scoped reagion for my modules.
in nutshell this is what I tried.
- Created a Shell with one "ModuleRegion" where my modules would register its container view.
- Created a container view of ModuleX say "ViewX" with some regions for my module and in the module activation added this to the shells's "ModuleRegion" with CreateRegionManagerScope = true.
- when a different module ModuleY is activated, I unregister the earler module container view using shellModuleRegion.Deactivate(ViewX) and shellModuleRegion.Remove(ViewX)
- Now I add the container view of ModuleY say ViewY which has its own reagions
It works fine up to this point, but when I re activate the ModuleX, I end up getting the following error in the big exception stack trace:"Region with given name already registred:".
Looks like shell somehow gets registred with the internal nested regions of ViewX eventhough its created with the scoped region and after I deactivate and removed it.
do you see something wrong in my approach.