DI Container

Dec 9, 2009 at 5:08 AM

Hi Daniel, in your 3rd article on Calcium you wrote that one can substitute DI providers.
But ServiceLocator singleton is automatically created in Bootstrapper, which explicitly uses Unity.
Deriving an own Bootstrapper and AppStarter does'nt help as they use internal client members.
How can I use my DI of choice without changing Calcium sources?

Dec 11, 2009 at 9:25 AM

The Prism UnityBootstrapper is being used, so two classes: AppStarter and Bootstrapper would need to be replaced or extended. The IServiceRegistrar also needs an implementation for the container you intend to use, which then needs to be registered with the container itself. I will make this a work item, and provide an easier way to pass the container in the future.




Dec 11, 2009 at 9:26 AM
This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.