It works with you use:
but, when you try to do anything like
IRegion region = regionManager.Regions["MainRegion"];
it won't work because the Regions collection is always empty. To test this, I used the HelloWorld sample you sent me and I ran it with BusyIndicator commented out and then with it uncommented.
When BusyIndicator was commented out, when I hit the breakpoint in overridden InitializeModules() method in Bootstrapper, I get one ActiveRegion in Container.Resolve<IRegionManager>().Regions.
When I re-run with BusyIndicator uncommented, it says no results <Empty>.
You would think that it would be pretty common use case to have busy indicator wrapping most of the shell and thereby wrapping at least one region. Anyways, thanks for the sample, as it allowed me to see exactly what my problem was.
You see, I have a menu on the shell that loads views from various modules into a main region (also in the shell). So, I need to have better control than simply calling RegisterViewWithRegion. I need to be able to deactivate and remove views from regions,
and I think this can only be done with IRegion instances. My app is working, but I may have to move the busyindicator to a section of the screen where it doesn't contain a region. Unless someone has another solution.