In designing component package / framework using Interface programming, where is the best place to put the Interfaces to reduce dependencies? In a single assembly that is referenced by other assemblies. In the domain assembly near the class that inherits the interface? or In the client assembly where the interface is being used?
RE: In designing component package / framework using I...
I think the best place is to keep them in the client assembly. By this, the cleint need not do a reference to any assembly for accessing the interface. Please comment on this. ThanksAbhang
RE: In designing component package / framework using I...
I think the best place is the client assembly by which the client need not add a reference for accessing the interface itself. Please reply I am not sure.
RE: In designing component package / framework using I...
I believe this depends on the kind of interface and component you are designing. If you indend to share your interface among different assemblies then it makes sense to place the interface in a client assembly.
RE: In designing component package / framework using Interface programming, where is the best place to put the Interfaces to reduce dependencies? In a single assembly that is referenced by other assemblies. In the domain assembly near the class that inh
One of the Architectural goal of the interface is to create rules/contract for defining of what needs to be done in the component/implementation and most of the time you end up creating for specific layer/component (Like Data Layer/ Business Layer) and its not much of use outside that layer. If you have multiple business layers and if each has its own way of interaction/contract then its best to have interfaces within those components or if all layers have the same type of interaction/contract then have the interface as a separate DLL and used by multiple layers. Hope this helps. Kindly comment if i over baked it :-)
