By Javier Callico on
3/11/2010
There are plenty of good Dependency Injection Container implementations out there. The selection of an IoC container is not only defined by the developer's preference, which can swing the vote big time since most developers swear by their favorite container, but also of other factors like standards in the organization, the usage of another product which already supports, or favors, a given IoC implementation, etc.
The usage of an IoC container should always be abstracted, making the process of switching between implementations fairly simple, or at least, the refactoring needed to accomplish this task will be minimal compared to the one needed if you were using references to a specific container all over your codebase.