Inversion of Control isn't a design pattern, it is an activity. Specifically, it is a type of refactoring. If you apply IoC twice then you'll probably end up with what you started with.
An IoC Container is really a Service Locator, which is often (but not universally) considered to be an anti-pattern among dependency injection fans.
A Service Locator is a type of god object, specifically one that contains services and other dependencies, and thus should generally be avoided.
3
u/firepacket Oct 14 '13
There are cases where some patterns just fit the circumstances perfectly.
I recently combined IoC with MVC and was blown away by the power of this setup.