Updates for Container Extensions

[dansiegel]

Description of Change

This adds a number of extensions from the Prism.Container.Extensions to provide a more complete registration API.

This also adds a ContainerResolutionException that both the UnityContainerExtension and DryIocContainerExtension will through when they are unable to resolve a given type.

The ContainerResolutionException has a GetErrors method which will evaluate the resolution error to try to give you additional information around why the resolution error occurred.

• For instance you wrote bad XAML and encountered a XAML Parse Exception that was thrown by InitializeComponents in the View's ctor
• Or you were missing a registration for a given service, etc... Note currently this will show an error for INavigationService in Xamarin.Forms since it doesn't have any knowledge of INavigationService or the service name.

fixes #2076
fixes #2078

Behavioral Changes

The UnityContainerExtension is now guarded on named resolutions as Unity would simply activate a new object() when trying to resolve unregistered Views.

PR Checklist

• Has tests (if omitted, state reason in description)
• Rebased on top of master at time of PR
• Changes adhere to coding standard

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.