Which .NET dependency injection framework do you u

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 7 years ago.

Currently there are quite a few DI/IoC-frameworks for .NET out there (http://www.hanselman.com/blog/ListOfNETDependencyInjectionContainersIOC.aspx). I find it quite hard to choose. Therefore I wanted to measure the public opinion and see which framework is the most popular - so please post your favorite framework here and let the people vote...

Answer 1

StructureMap

I love the fact that I can configure it all using the fluent interface (aka Configuration DSL). Typesafe configuration is a must when I do refactoring.

Answer 2

Unity It's simple and unintrusive, yet type-safe. And it is created by Microsoft Pattern & Pratices group.

Answer 3

Have a look at Structuremap which is a Dependency Injection / Inversion of Control tool for .Net

Answer 4

I'm currently using Castle.Windsor. Mainly because of the integration it has with the Rhino Tools library.

Answer 5

Autofac. Type-safe and plays well with code-refactoring. Apart from the boiler-plate stuff, I found the delegate factories to be very useful.

Answer 6

I've been watching Kzu (creator of Moq)'s screencast series as he develops Funq - a DI framework that makes extensive use of lambdas the same way Moq does. No release yet but I'm looking forward to trying it out.