We are currently migrating all of our existing applications including our WPF application to .NET 6 from .NET 4.6.2.
This has been a huge challenge, but as part of that, we are updating to the latest version of Prism. as well as having to move to Unity from MEF.
We have pretty much got everything up and running, but we are having some navigation issues, and these seem to arise from an existing problem with nested regions.
I read the following StackOverflow article and it made sense but is resulting in some very strange behaviour.
Prism 7 throws and exception when working with nested views
We handle all view model initialisation once we pick up the OnNavigated to event, but since adding in this code for a potential fix, we are seeing OnNavigateTo events coming in using the parent View rather than the view embedded into the region.
I can do more debugging, but I just wondered if the solution linked above also applies to .NET 8 or am I just missing something.
Many thanks in advance
