silverlight 4.0 - Problem with Prism RegionManager and Unity container -

I have a main silicilt project and other modules and I am using the prism so that they can get dependency injection for unity with unity.

I have a module I have that relies on a IRegionManager , which naturally moves it into an injection by unity.

On this issue, I am running that property of area regional manager which I do not include in any field, though I Two of the shells have been declared as follows:

  Regions: Regional Manager. RuleName = "Main Area"   
 I can not understand the reason for this behavior. I have tried to use  regional manager  as a singleton  
  container. Registrar & lt; IRegionManager & gt; (New area manager ());   
 Also handle this by leaving unity. However, I got the same result: ( 
 What I am trying to achieve is to inject a scene in a particular area and activate it, which  
 Can not use  _regionManager.RegisterViewWithRegion ("Main Region", Typef (MyViv));   
 This is the reason why I hold the "Main Reggae" object and It needs to be manipulated.  
 I hope someone has thought about it.  
  Edit : Let me tell you that Visual Search works just fine, I  RegisterViewWithRegion , but when I  Check the property of the Region   Regional Manager , then I think it's empty!   
 
 
 While thinking about this problem and in the context that it happened, it pushed me that the software The problem in most of the bugs was not where I was watching!  
 My setup was as follows: I started with the Silverlight Business Application Project template, it gave me a  manpage  in which I used my  shell  , And some thoughts (about  home  and ). Now, instead of sitting areas on my  shell, I put them on the main page by putting the main page in  Home  view.  
 I have the idea that the prism sets a  regional manager for  and that which it requires (using dependency injection container By doing this, when I asked a  IRegionManager  in my module, I found it for my  shell  which is not really any field (hence the empty  area  property).  
 To make it  resolve , I was kept at my right place in my area:  Shell , and all is well (for) Now working.  
  Update : Looks like my "take over" is actually true :), this is a fraction: ( scoped area )  
 
 defines areas with attached properties automatically passes their parent's regional manager. Usually, this  global area manager  is  shell  Window