Proper way to handle navigation exception with DryIoc

[alessandrogaspani]

Hello Everyone!

If I forgot to register a dependency, and i try to navigate to a VModel with this dependency, I get the Navigation Exception as expected, but I can not find a way to show in a MessageBox what dependency is missing.

Recently i created a question on StackOverflow about it..
https://stackoverflow.com/questions/73138497/proper-way-to-handle-prism-navigation-exception

And I found out that is a DryIoc problem..
dadhi/DryIoc#506

Now DryIoc should be fixed, is it possible to include this fix to the next Prism DryIoc Package release?

Thanks!

Alessandro Gaspani