Alex, thanks again.
Unfortunately, we need to pass the container into our Modules because service/view registration is handled via configuration and on demand. In order to achieve this we need a handle on the Unity container, so that we can call UnityContainerElement.Configure(IUnityContainer), which you can see being called in the IModule.Initialize() member above. It is in fact this passing around of the Unity container that poses the greatest problem to our testing strategy: because the exposed interfaces are only configured with dependencies upon the unity container, we have to go inspect the code to determine what other interfaces we actually need to mock in order to run the tests. However, our investigations have lead us to no other solution for configuring the container dynamically with requiring such a handle on the container, nor have we found any other mthod for getting said handle without having it injected. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino.Mocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhinomocks?hl=en -~----------~----~----~----~------~----~------~--~---
