Skip to main content

Controller Factory for Castle Windsor v2.5.0, with HttpContext Resolution/Injection

The code below defines an object that holds an instance of the Castle Windsor container and sets it up to handle all requests to resolve ASP.NET MVC Controllers.  It also includes code to inject instances of HttpRequest and HttpContextBase.  This means that you can define injected objects that contain references to HttpContextBase in their constructors (which can be your MVC controllers) and they will receive populated instances of these objects.  It is worth noting that if you reference an instance of HttpContext that has not been resolved / injected by your IoC container then there is a high likely hood that you will end up with two or more separate instances which will cause problems (see this article on Injecting into Action Filter Attributes that can suffer this issue).

Please feel free to use this code and let me know if you run into any issues or have recommendations on how it could be improved.

public class WindsorControllerFactory : DefaultControllerFactory
IWindsorContainer Container { get; set; }

public WindsorControllerFactory(IWindsorContainer container)
Container = container;
Container.Register(AllTypes.FromThisAssembly().BasedOn(typeof(IController)).Configure(c => c.LifeStyle.Is(LifestyleType.Transient)));

.UsingFactoryMethod(() => new HttpRequestWrapper(HttpContext.Current.Request)));

.UsingFactoryMethod(() => new HttpContextWrapper(HttpContext.Current)));

Container.Register(Component.For<HttpContext>().LifeStyle.PerWebRequest.UsingFactoryMethod(() => HttpContext.Current));

protected override IController GetControllerInstance(RequestContext requestContext, Type controllerType)
return (IController)Container.Resolve(controllerType);

public override void ReleaseController(IController controller)

This can then just be simple called by adding the following to your global.asax code.  Note: This expects a “castle” section to be defined in your web.config to resolve non-controller references handled within the WindsorControllerFactory.

public static IWindsorContainer WindsorContainer { get; private set; }

protected void Application_Start()
WindsorContainer = new WindsorContainer(new XmlInterpreter(new ConfigResource("castle")));
ControllerBuilder.Current.SetControllerFactory(new WindsorControllerFactory(WindsorContainer));


  1. Instead of AllTypes.FromAssembly(Assembly.GetExecutingAssembly())

    you can call AllTypes.FromThisAssembly()

    also you don't need FactorySupportFacility.

  2. Thanks Krzysztof, have updated article and more importantly my code.

  3. Thanks Paul, this is just what I was looking for.



Post a Comment

Popular posts from this blog

Mocking HttpCookieCollection in HttpRequestBase

When unit testing ASP.NET MVC2 projects the issue of injecting HttpContext is quickly encountered.  There seem to be many different ways / recommendations for mocking HttpContextBase to improve the testability of controllers and their actions.  My investigations into that will probably be a separate blog post in the near future but for now I want to cover something that had me stuck for longer than it probably should have.  That is how to mock non abstract/interfaced classes within HttpRequestBase and HttpResponseBase – namely the HttpCookieCollection class.   The code sample below illustrates how it can be used within a mocked instance of HttpRequestBase.  Cookies can be added / modified within the unit test code prior to being passed into the code being tested.   After it’s been called, using a combination of MOQ’s Verify and NUnit’s Assert it is possible to check how many times the collection is accessed (but you have to include the set up calls) and that the relevant cookies have …

Do "Task Hours" add anything in Scrum (Agile)?

What do task hours add to the overall process in scrum?This was a question that has arisen from all team members in both instances that I've helped teams switch over to scrum. The benefits of artifacts like the comparative story point estimation, the 2 week sprints, stand-ups and the end of sprint demo have been self evident to the team, but as one I think every team member has expressed dismay when it comes to task planning and estimating each task in hours. Left unchecked there is a natural tendency for people to actually begin to dread the start of each sprint purely due to the task planning session.In my current role we've been lucky to investigate this further as a team.The team sat down to discuss the problems it was experiencing with estimating tasks in hours and the following common themes appeared:It is hard: Maybe it shouldn't be, but time estimation is hard! Story points are comparative and abstracted making them easier to determine, but time estimate is gen…

Why do my Android Notification only appear in the status bar?

I'm definitely getting back into Android development, I'm remembering that feeling of 'Surely this should be easier than this!'. All I wanted to do was to schedule a local notification which behaved similar to a push notification pop-up. That is, as well as showing the small icon in the status bar I wanted it to pop up on screen to notify the end user. All seems fairly easily, I found this code for how to schedule a notification. That all worked perfectly, apart from the notification would only appear in the status bar. Searching around I found loads of different answers / solutions, mostly all saying the same thing:It only worked if you used 'NotificationCompat.Builder' in place of 'Notification.Builder', orYou had to set the priority to 'NotificationCompat.PRIORITY_HIGH'As usually happens, none of these solutions worked for me until I added in the missing piece of the jigsaw:- '.setDefaults(Notification.DEFAULT_ALL)'. For me this…