Hi Don,
Thank you for replying the solution you could accomplish. Instead of removing your initial question, it is much better to reply and post your solution because your work would be helpful for users that may go through the same or similar problem.
I think the right anwswer regarding your design question would only be done by the P&P Team. However, based on my understanding I would think that default apps would not need to remove a specific View manually. Furthermore, you would be adding the related responsibility to someone that would not be appropiate.
Regarding the scenario you described, I am afraid I don't completely understand how you would change the View name with the Application running. Any available View that you would be able to Navigate to would have been already loaded and registered in a specific Region. That is why I don't see the problem you mentioned. Plus, I understand that if a View source name is modified, then a rebuild would be needed. Please, let me know if there is something that I missunderstood.
Maybe you could find helpful the Navigation chapter on MSDN Prism's Guide:
I hope I could provide some better understanding about the Region/NavigationPrism design.
Regards,
Gabriel Ostrowsky.
https://blogs.southworks.net/gostrowsky
Thank you for replying the solution you could accomplish. Instead of removing your initial question, it is much better to reply and post your solution because your work would be helpful for users that may go through the same or similar problem.
I think the right anwswer regarding your design question would only be done by the P&P Team. However, based on my understanding I would think that default apps would not need to remove a specific View manually. Furthermore, you would be adding the related responsibility to someone that would not be appropiate.
Regarding the scenario you described, I am afraid I don't completely understand how you would change the View name with the Application running. Any available View that you would be able to Navigate to would have been already loaded and registered in a specific Region. That is why I don't see the problem you mentioned. Plus, I understand that if a View source name is modified, then a rebuild would be needed. Please, let me know if there is something that I missunderstood.
Maybe you could find helpful the Navigation chapter on MSDN Prism's Guide:
I hope I could provide some better understanding about the Region/NavigationPrism design.
Regards,
Gabriel Ostrowsky.
https://blogs.southworks.net/gostrowsky