WhoMightUseFlexDi

There are a few very good mature & well-supported DI containers available for .NET, including Autofac and Ninject. These are both well-suited to enterprise application development. So - why write another?

FlexDi is simpler than other large-scale containers. It is aimed at those who need:

• Extensibility - the architecture exposes hooks and opportunities to customise most aspects of the registration and resolution process.
• Simplicity - it is very easy to add a FlexDi container to your project and get using it immediately.
• Registration-less resolution - with the appropriate options enabled, it is possible to resolve some classes straight from the container with no need to register then first.

FlexDi is particularly suited to:

• Resolution of dependencies for automated integration/acceptance testing
• Small applications with modest DI needs