Skip to content
Dan Siegel edited this page Aug 6, 2019 · 1 revision

Why use the Prism.Container.Extensions? Prism is great but it's simple by design. For complex applications and enterprise solutions it quite likely that you'll run into situations where you simply exceed what is possible from the base Registration methods and require more advanced scenarios that require direct container access. The container extensions are purpose built with the belief that your code should not be explicitly tied to a specific container. By using the Container Extensions you get access to container registration methods that are often used in more advanced scenarios:

  • Register a single Implementing type that is registered as a singleton and that singleton is resolved for multiple service interfaces
  • Register a service with a simple factory which may have no inputs, or a more complex factory which may require resolving services with either IServiceProvider or IContainerProvider
  • Register a scoped service
Clone this wiki locally