This might seem like an unusual question but I can't find any advise on the subject.
Scenario: I have an interface X. Because the goal of the interface is enforce a protocol that can be implemented by many types it needs to be widely available. I might also have several other interfaces that I want to make available because they need to be commonly implemented. Questions: What is the best way to acheive easy availability of interfaces amoung components? One thought would be to place commonly used interface definitions in their own assembly so that they can be referenced from many components? For some reason, (even in MS Application block code) I tend to see interface definitions deployed in a particular assembly that needs to use it. What if another type wants to implement the interface? Because interfaces are contained in the assembly that implements them another implementor would need to reference that assembly just to get a reference to the interfaces. Suggestions? =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
