There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
Consider creating a ContainerProvider
I noticed there's an IPrismContainer interface which is not used.
I would like to suggest that a ContainerProvider be created so that a concrete Dependency Injection provider can be specified in a configuration file. For example, the interface and base classes (if needed) would live in Prism.Container, and any concrete provider
implementations would live in external assemblies such as: Prism.Container.Unity etc. Obviously, this would enabled the benefit of being able to swap out or change the provider via a configuration file change. And, it prevents the need of hard-coding a reference
Feel free to change the nomenclature though, if you feel "Container" is too ambiguous. However, I do not recommend using anything too specific in the name, such as "DependencyInjection", or "InversionOfControl", or even their well