Are we using IoC effectively?

Posted by Juliet on Stack Overflow See other posts from Stack Overflow or by Juliet
Published on 2010-03-21T21:32:12Z Indexed on 2010/03/21 21:51 UTC
Read the original article Hit count: 259

So my company uses Castle Windsor IoC container, but in a way that feels "off":

  • All the data types are registered in code, not the config file.
  • All data types are hard-coded to use one interface implementation. In fact, for nearly all given interfaces, there is and will only ever be one implementation.
  • All registered data types have a default constructor, so Windsor doesn't instantiate an object graph for any registered types.

The people who designed the system insist the IoC container makes the system better. We have 1200+ public classes, so its a big system, the kind where you'd expect to find a framework like Windsor. But I'm still skeptical.

Is my company using IoC effectively? Is there an advantage to new'ing objects with Windsor than new'ing objects with the new keyword?

© Stack Overflow or respective owner

Related posts about castle-windsor

Related posts about design-patterns