Hi Guido and thanks for you quick reply.
I am still not seeing why this is removing the region from the RegionManager but it most definately is.
In my applicaiton I have a tab control within a separate document window (separate region) and to the right of this document window (region) I have a right docking region which is where I inject now two views.
Currently I am using the onselectionchanged event of the tab control situated in my document window and when fired, I test to see if the tab item's datacontext (viewmodel) being changed from/to supports a custom interface I wrote that allows
me to call back through the tab item(s) related view model and request it to remove any related views from the docking region (ie, will call's a supporting method of the old tabitem's view model tabbing from) and then I call the
the tab item's supporting interface to requestnavigate any views back into the docking region (within my custom interface's).
I added two views instead of just one to the same and only removed one of the views.
What I see is what I expect to see, the one view remains (does not implement IRegionMemberLifetime) while the other is removed and the Region remains which allows me to navigate the one I removed back into the region when I click back to the supporting tab
It's as if some code elsewhere is requesting that I remove this docking region but hangs on until all the views are removed. I have searched high and low but do not see where anything is trying to remove a region.