Hi Kalle,
I believe the issue you are having is related to the scoped region manager and that the same is not being created so all the regions are being registered in the same region manager, causing the issue you are describing.
It seems you are using the approach described here and that might not work anymore in PRISM 5.
Could you please provide a small sample reproducing the issue so we can take a further look to it?
Thanks,
Ez.
http://blogs.southworks.net
I believe the issue you are having is related to the scoped region manager and that the same is not being created so all the regions are being registered in the same region manager, causing the issue you are describing.
It seems you are using the approach described here and that might not work anymore in PRISM 5.
Could you please provide a small sample reproducing the issue so we can take a further look to it?
Thanks,
Ez.
http://blogs.southworks.net