I think the trend you are seeing is because most Interfaces are either implemented or consumed in a single assembly. I don't think it's a hard and fast rule.
It makes perfect sense to me to place your interfaces in a separate assembly if they sit at a junction between many implementers and many consumers. --Jekke Bill Bassler wrote: > 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? -- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. =================================== 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
