Follow
Question on IoC programm pattern.
By convention and tradition in IoC it is normal to define an interface, then implement a class for that interface, then define in the IoC provider that calls for the interface should get an instantiation of the class, this is usually done for ROI and reuse and different injection scenarios, but in my experience 85% of the time there is only ONE class in the project that implements the interface.
That is over-engineering
What am I missing?
@XSGeek - that being said, I've only done IoC in Java. So perhaps .Net has different uses/capabilities here.
@XSGeek - I might be off base here, but the only thing it got me was easier mocking.