Tuesday, February 03, 2009

Ninject or not?

For my next project, I'm looking into using a Dependency Injection framework. For those of you who don't know what it is, I would like to forward you to this article from Martin Fowler. The book I'm reading uses Castle Windsor, but it hasn't been updated in a while so I'm looking into others, like the Unity application block.

I came across Ninject lately (thanks to StackOverflow) but it seems awkward to choose for a DI framework without the ability to configure it from outside the code.


  1. Anonymous4:52 AM

    Glad you're considering using Ninject! Ninject takes the stance that the configuration of your DI framework is actually part of your application, and shouldn't be publicly configurable. If you want certain bindings to be configurable, you can easily make your Ninject modules read your app.config. Having your bindings in code saves you from the verbosity of XML, and gives you type-safety, refactorability, and intellisense.

  2. Thank you!

    That's exactly the answer I was looking for in this question. Do you mind if I quote you, or do you prefer to answer it yourself?