我使用Simple Injector:

Simple Injector是一个简单、灵活、快速的依赖注入库，它使用最佳实践指导您的解决方案走向成功。

我花了大半天的时间苦苦挣扎，只为得到最简单的泉水。NET实例工作。永远不知道如何让它从XML文件中找到我的程序集。另一方面，在大约2小时内，我能够让Ninject工作，包括测试与NUnit和MSTest的集成。

编辑(不是作者写的):https://github.com/quozd/awesome-dotnet/blob/master/README.md#ioc:上有IoC框架的全面列表

Castle Windsor - Castle Windsor is best of breed, mature Inversion of Control container available for .NET and Silverlight Unity - Lightweight extensible dependency injection container with support for constructor, property, and method call injection Autofac - An addictive .NET IoC container DryIoc - Simple, fast all fully featured IoC container. Ninject - The ninja of .NET dependency injectors Spring.Net - Spring.NET is an open source application framework that makes building enterprise .NET applications easier Lamar - A fast IoC container heavily optimized for usage within ASP.NET Core and other .NET server side applications. LightInject - A ultra lightweight IoC container Simple Injector - Simple Injector is an easy-to-use Dependency Injection (DI) library for .NET 4+ that supports Silverlight 4+, Windows Phone 8, Windows 8 including Universal apps and Mono. Microsoft.Extensions.DependencyInjection - The default IoC container for ASP.NET Core applications. Scrutor - Assembly scanning extensions for Microsoft.Extensions.DependencyInjection. VS MEF - Managed Extensibility Framework (MEF) implementation used by Visual Studio. TinyIoC - An easy to use, hassle free, Inversion of Control Container for small projects, libraries and beginners alike. Stashbox - A lightweight, fast and portable dependency injection framework for .NET based solutions.

以下是原来的答案。

我想我在这里可能有点挑剔，但重要的是要注意DI(依赖注入)是一种编程模式，它由IoC(控制反转)框架促进，但并不需要。IoC框架只是让DI变得更容易，而且它们提供了许多其他优于DI的好处。

That being said, I'm sure that's what you were asking. About IoC Frameworks; I used to use Spring.Net and CastleWindsor a lot, but the real pain in the behind was all that pesky XML config you had to write! They're pretty much all moving this way now, so I have been using StructureMap for the last year or so, and since it has moved to a fluent config using strongly typed generics and a registry, my pain barrier in using IoC has dropped to below zero! I get an absolute kick out of knowing now that my IoC config is checked at compile-time (for the most part) and I have had nothing but joy with StructureMap and its speed. I won't say that the others were slow at runtime, but they were more difficult for me to setup and frustration often won the day.

更新

I've been using Ninject on my latest project and it has been an absolute pleasure to use. Words fail me a bit here, but (as we say in the UK) this framework is 'the Dogs'. I would highly recommend it for any green fields projects where you want to be up and running quickly. I got all I needed from a fantastic set of Ninject screencasts by Justin Etheredge. I can't see that retro-fitting Ninject into existing code being a problem at all, but then the same could be said of StructureMap in my experience. It'll be a tough choice going forward between those two, but I'd rather have competition than stagnation and there's a decent amount of healthy competition out there.

其他IoC视频也可以在Dimecasts上找到。

这取决于你在寻找什么，因为它们都有各自的优点和缺点。

Spring.NET is the most mature as it comes out of Spring from the Java world. Spring has a very rich set of framework libraries that extend it to support Web, Windows, etc. Castle Windsor is one of the most widely used in the .NET platform and has the largest ecosystem, is highly configurable / extensible, has custom lifetime management, AOP support, has inherent NHibernate support and is an all around awesome container. Windsor is part of an entire stack which includes Monorail, Active Record, etc. NHibernate itself builds on top of Windsor. Structure Map has very rich and fine grained configuration through an internal DSL. Autofac is an IoC container of the new age with all of it's inherent functional programming support. It also takes a different approach on managing lifetime than the others. Autofac is still very new, but it pushes the bar on what is possible with IoC. Ninject I have heard is more bare bones with a less is more approach (heard not experienced). The biggest discriminator of Unity is: it's from and supported by Microsoft (p&p). Unity has very good performance, and great documentation. It is also highly configurable. It doesn't have all the bells and whistles of say Castle / Structure Map.

总之，这取决于什么对你来说是重要的。我同意其他人的看法，去评估，看看哪一个合适。好处是你有很多甜甜圈可以选择，而不仅仅是果冻甜甜圈。

我可以推荐Ninject。它非常快速且易于使用，但仅当您不需要XML配置时，否则您应该使用Windsor。

春天。Net是非常可靠的，但是文档花了一些时间。Autofac很好，虽然支持。net 2.0，但你需要VS 2008来编译它，或者使用命令行来构建你的应用程序。