Hi James,
Based on my understanding Prism 4.2 would not have changed this behaviour yet. as the following download site describes the list of updates performed.
However, the following item related to this issue is open so you could vote for making the P&P team fix it and update the library on a future release:
Anyway, you could always be able to modify the Prism Library and make the ExecuteNavigation() actually throws the exceptions as Guido Maliandi tells in his post.
Regards.
Gabriel Ostrowsky
https://blogs.southworks.net/gostrowsky
Based on my understanding Prism 4.2 would not have changed this behaviour yet. as the following download site describes the list of updates performed.
However, the following item related to this issue is open so you could vote for making the P&P team fix it and update the library on a future release:
Anyway, you could always be able to modify the Prism Library and make the ExecuteNavigation() actually throws the exceptions as Guido Maliandi tells in his post.
Regards.
Gabriel Ostrowsky
https://blogs.southworks.net/gostrowsky