Filed Under : 
Jul.30,2010A few days ago Scott Guthrie announced the ASP.NET MVC 3 Preview 1 availability. The team did such a great job adding Dependency Injection to the whole framework using a slightly modified Service Locator, in that way you may plug your favorite DI container. As you may imagine, there is no DI container shipped with this first preview, so you need to roll your own. Brad Wilson did such a terrific job writing a post series about DI using MVC 3 Preview 1 and create a Unity Container Service Locator adapter, I really recommend you read his blog post series before continue with this post 
I prefer Castle Windsor Container, so using his blog posts as a blueprint, I write a simple Service Locator adapter for Castle Windsor.
Let’s tart with the Controller Factory:
using System.Web.Mvc;
using System.Web.Routing;
using Castle.MicroKernel;
namespace Castle.Windsor.Mvc {
public class WindsorControllerFactory : IControllerFactory {
private readonly IControllerFactory _defaultFactory;
private readonly IWindsorContainer _container;
public WindsorControllerFactory(IWindsorContainer container) : this(container, new DefaultControllerFactory()) {
_container = container;
}
public WindsorControllerFactory(IWindsorContainer container, IControllerFactory defaultFactory) {
_container = container;
_defaultFactory = defaultFactory;
}
public IController CreateController(RequestContext requestContext, string controllerName) {
try {
return _container.Resolve<IController>(controllerName.ToLowerInvariant());
} catch (ComponentNotFoundException) {
return _defaultFactory.CreateController(requestContext, controllerName);
}
}
public void ReleaseController(IController controller) {
_container.Release(controller);
}
}
}
Pretty straighforward, now, it’s time for the Castle Windsor adapter for MvcServiceLocator, it is almost a wrap over Windsor methods:
using System;
using System.Linq;
using System.Collections.Generic;
using System.Web.Mvc;
namespace Castle.Windsor.Mvc {
public class WindsorMvcServiceLocator : IMvcServiceLocator {
private readonly IWindsorContainer _container;
public WindsorMvcServiceLocator(IWindsorContainer container) {
_container = container;
}
public object GetService(Type serviceType) {
return _container.Resolve(serviceType);
}
public IEnumerable<TService> GetAllInstances<TService>() {
return _container.ResolveAll<TService>();
}
public IEnumerable<object> GetAllInstances(Type serviceType) {
return _container.ResolveAll(serviceType).Cast<object>();
}
public TService GetInstance<TService>() {
return _container.Resolve<TService>();
}
public TService GetInstance<TService>(string key) {
return _container.Resolve<TService>(key);
}
public object GetInstance(Type serviceType) {
return GetService(serviceType);
}
public object GetInstance(Type serviceType, string key) {
return _container.Resolve(key, serviceType);
}
public void Release(object instance) {
_container.Release(instance);
}
}
}
To allow inject filters you need to provide a IFilterProvider implementation, I did it using Brad’s post about DI on Action Filters:
using System.Web.Mvc;
namespace Castle.Windsor.Mvc {
public class WindsorFilterAttributeFilterProvider : FilterAttributeFilterProvider {
private readonly IWindsorContainer _container;
public WindsorFilterAttributeFilterProvider(IWindsorContainer container) {
_container = container;
}
protected override System.Collections.Generic.IEnumerable<FilterAttribute> GetControllerAttributes(
ControllerContext controllerContext, ActionDescriptor actionDescriptor) {
var attributes = base.GetControllerAttributes(controllerContext, actionDescriptor);
foreach (var attribute in attributes) {
_container.BuildUp(attribute.GetType(), attribute);
}
return attributes;
}
protected override System.Collections.Generic.IEnumerable<FilterAttribute> GetActionAttributes(
ControllerContext controllerContext, ActionDescriptor actionDescriptor) {
var attributes = base.GetActionAttributes(controllerContext, actionDescriptor);
foreach (var attribute in attributes) {
_container.BuildUp(attribute.GetType(), attribute);
}
return attributes;
}
}
}
That last part was a little different than others mainly because we cannot use constructor injection in Attributes, so an easy way is just to create a simple method extension to extend Windsor and inject the properties in an already created instance:
using System;
using System.Linq;
namespace Castle.Windsor.Mvc {
public static class WindsorExt {
public static void BuildUp(this IWindsorContainer container, Type type, object instance) {
var properties = type.GetProperties().Where(p => p.CanWrite && p.PropertyType.IsPublic);
foreach (var propertyInfo in properties) {
if (container.Kernel.HasComponent(propertyInfo.PropertyType)) {
propertyInfo.SetValue(instance, container.Resolve(propertyInfo.PropertyType), null);
}
}
}
}
}
Simple… you can grab the sourcecode from my bitbucket repository http://bitbucket.org/cprieto/castle-windsor-mvc
NOTE: before anybody else start screaming about using Service Locator: I don’t like at all the use of Service Locator, and I think it must be considered the atomic bomb in component injection (it’s even considered an antipattern as Mark Seeman describes). I’m writing this articule to sample how to to plug your own DI framework inside ASP.NET MVC 3 Preview 1… at least we have now a native way to do it.
Tags : 
, como siempre agradezco sus comentarios, tags, pings, whatever… siempre son bienvenidos….