Interfaces and Inversion of Control

The way I see it, there are three reasons for using an Inversion of Control (IoC) / Dependency Injection (DI) container:To decouple the actual implementation from a base class/interface (the contract), so that we can change the implementation when neededTo allow the implementation itself to have ser