Comparing Castle Windsor, Unity and StructureMap

by

See here and here for a pretty thorough technical comparison of several IoC containers, although somewhat outdated by now (they’re from before Windsor 2.0)

However, I don’t think there are really any vital features that Windsor offers and other containers don’t. Windsor, StructureMap, Spring.NET have all been around for several years and have been used in lots of projects over these years so they’re very mature now. Newer containers, like Autofac, Unity, Ninject and SimpleInjector build on that previous experience so they won’t lack those vital features either.

Now the more subjective part of the answer: I like to think that Windsor has a nice mix of usability, extensibility and integration modules.

Usability: for example, you can use XML and/or code registration (it also has a fluent API like most containers nowadays).

Extensibility: Lots of extension points that you can use to customize or override pretty much any default behavior.

Integration: Windsor has lots of facilities (modules) that allow for easy integration with other frameworks/libraries. Other integrations include ASP.NET MVC, MonoRail, Workflow Foundation, NServiceBus, MassTransit, Rhino Service Bus, Quartz.Net, SolrNet, SolrSharp, Windows Fax Services.

This series of articles covers many niceties and extension points of Windsor.

Note that I’m not saying that other containers don’t offer similar things! Even if you picked one of them and later you found out it’s lacking some integration, it’s usually not hard to code it yourself.

Bottom line: I don’t think you can go wrong with any of the main IoC containers, as long as you structure your code properly (e.g. avoid the service locator anti-pattern).

More Related Contents:

  1. Is there a pattern for initializing objects created via a DI container
  2. Why not use an IoC container to resolve dependencies for entities/business objects?
  3. Ioc/DI – Why do I have to reference all layers/assemblies in application’s entry point?
  4. Why do I need an IoC container as opposed to straightforward DI code? [closed]
  5. Windsor – pulling Transient objects from the container
  6. How do the major C# DI/IoC frameworks compare? [closed]
  7. How do I effectively design my application where most classes depend on ILogger?
  8. When to use PerThreadLifetimeManager?
  9. Which Dependency Injection Tool Should I Use? [closed]
  10. Passing constructor arguments when using StructureMap
  11. Resolving HttpControllerContext with Castle Windsor
  12. Windsor castle Injecting properties of constructed object
  13. How to avoid Dependency Injection constructor madness?
  14. What is a composition root in the context of dependency injection?
  15. Dependency Injection in attributes
  16. Dependency Injection Unity – Conditional Resolving
  17. Inversion of Control < Dependency Injection [closed]
  18. Dependency injection through constructors or property setters?
  19. Unity Inject dependencies into MVC filter class with parameters
  20. Avoiding all DI antipatterns for types requiring asynchronous initialization
  21. .NET Core DI, ways of passing parameters to constructor
  22. When are .NET Core dependency injected instances disposed?
  23. Meaning of bean discovery mode annotated in CDI 1.1
  24. Property Injection in ASP.NET Core
  25. Dagger @Reusable scope vs @Singleton
  26. Null User on HttpContext obtained from StructureMap
  27. MEF (Managed Extensibility Framework) vs IoC/DI
  28. When to use Dependency Injection
  29. Net Core Dependency Injection for Non-Controller
  30. How to integrate IoC Membership provider with ASP.NET MVC

Leave a Comment