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...
Asked
Active
Viewed 1,215 times
7 Answers
4
I'm currently using Castle.Windsor. Mainly because of the integration it has with the Rhino Tools library.
Scott Muc
- 2,833
- 26
- 38
1
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.
Matt Hamilton
- 194,622
- 60
- 382
- 318
-
That looks interesting, thanks. – suhair Mar 13 '09 at 11:23
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.
BjartN
- 5,137
- 4
- 27
- 32
0
Use Windsor or Unity, and decide based on a POC
Unity is not so bloated up so far, you could go with that based on your project type - especially if you are using unity dependent frameworks like CompositeWPF
See another thread on SO about the same, Enterprise Library Unity vs Other IoC Containers
Community
- 1
- 1
amazedsaint
- 7,604
- 6
- 53
- 83
-
I'd just add that Composite WPF is not dependent on unity - all unity support is provided by a UnityExtensions module which you don't have to reference. You can (and I do) use Castle or another container. – Paul Stovell Feb 23 '09 at 20:02
0
Unity It's simple and unintrusive, yet type-safe. And it is created by Microsoft Pattern & Pratices group.
toxvaerd
- 3,392
- 3
- 23
- 29
-
Judging by http://unity.codeplex.com/SourceControl/PatchList.aspx, they do not accept any community contributions. – Yuri Astrakhan Oct 01 '09 at 15:16
-