How can I expose Unity to my MVC contollers for unit testing? I quickly found resources for exposing Unity to MVC through a Controller Factory in a custom HttpApplication Start event. But, unit tests usually create and call Controllers directly, so... I suppose I could create a custom Controller class that exposes and initializes Unity within a controller, but then I have the problem of running as a web application, maintaining a single instance of Unity to work with. I suppose I could attempt a static instance on some custom global object... Seems like such a kludge at this point.

Your unit tests will usually just instantiate a specific controller, rather than letting Unity handle this? Check www.cartrackr.net for an MVC sample using Unity + MStest.

This is a great project, but the tests are hard-coded to use a specific Repository rather than using the same logic stored within the application that relies on Unity to inject the type of Repository. This is what I am after: My logic for Unity type injection should be the same for my tests as for my application, but I should be able to configure them differently using Unity configuration sections.

After seeing this project's implementation, I am resolved to the fact that I will need to create my own singleton for storing and managing a reference to the UnityContainer and will need to reference this object in both my tests and application.

If done right, I suppose I could be a ridiculous developer and try to make my application IOC container agnostic; swapping out any IOC framework! An IOC for IOC frameworks? LOL! No... I have work to do.

If you are trying to test your controller then I don't see what is wrong with explicitly setting the repository via the controllers constructor in your test. After all you want to test your controller, not that your controller factory is using IoC correctly.

Re your second point see - http://www.codeplex.com/CommonServiceLocator