Separation of interfaces and implementation

Posted by bonefisher on Stack Overflow See other posts from Stack Overflow or by bonefisher
Published on 2010-04-12T16:28:25Z Indexed on 2010/04/12 16:33 UTC
Read the original article Hit count: 290

From assembly(or module) perspective, what do you think of separation of Interface (1.assembly) and its Implementation (2.assembly)?

In this way we can use some IoC container to develop more decoupling desing.. Say we have an assembly 'A', which contains interfaces only. Then we have an assembly 'B' which references 'A' and implements those interfaces..It is dependent only on 'A'.

In assembly 'C' then we can use the IoC container to create objects of 'A' using dependency injection of objects from 'B'. This way 'B' and 'C' are completely unaware (not dependent) of themselves..

© Stack Overflow or respective owner

Related posts about best-practices

Related posts about inversion-of-control