Rickard Nilsson is a software architect, developer, craftsman, agile enthusiast, and father of three... More
Rickard blogs about crafting software using .NET tooling and solid, development practices.
Update! Download sample project MvcWithUnity.VS2010.zip (727,52 kb)
This is an update to a previous post on MVC and Unity: Dependency injection in ASP.NET MVC with Unity IoC Container
After my previous post, new versions of both ASP.NET MVC and Unity has been released and some confusion about their compatibility has shown up on the Internet. The first hit on Google on the topic is this which is completely wrong and uninformed. BillKrat writes:
"MVC2 will pull the rug out from under these blogs because the IControllerFactory interface for CreateController no longer provides a "type" - it provides a "string" which will simply hold the controllerName; not as easy to work with."
In fact, this is not the case at all. The following snippet is fresh out of the code repository from the MVC 1.0 relase:
public interface IControllerFactory { IController CreateController(RequestContext requestContext, string controllerName); void ReleaseController(IController controller); }
thus, the interface has not changed at all, and all samples on integrating ASP.NET MVC with Unity still apply!
What BillKrat has done is to mistake the interface for the base implementation in System.Web.Mvc.DefaultControllerFactory. If we subclass DefaultControllerFactorty all we need to do is this (as I’ve explained previously):
public class UnityControllerFactory : DefaultControllerFactory { private readonly IUnityContainer container; public UnityControllerFactory(IUnityContainer container) { this.container = container; } protected override IController GetControllerInstance( RequestContext requestContext, Type controllerType) { return container.Resolve(controllerType) as IController; }}
thus, here we get our type which plays very nicely with Unity’s Resolve method.