<p>I like the idea of having Interfaces and Implementation separate.  But how separate?  Are the Interface definitions in a separate .Net assembly?  Do you have a single project that defines all Interfaces for a solution?  Otherwise are there issues with circular dependencies of Interfaces?</p>

[{'answer_id': 57391, 'author': 'Lars Mæhlum', 'author_id': 960, 'author_profile': 'https://Stackoverflow.com/users/960', 'pm_score': 4, 'selected': True, 'text': '<p>Put your domain objects and interfaces in a seperate "domain" assembly.<br>\nThis assembly should never reference anything but the core .net assemblies.</p>\n\n<p>This way you get a clean seperation from your domain/service model and your implementation.</p>\n\n<p><em>Edit:</em><br>\n<a href="http://jeffreypalermo.com/blog/the-onion-architecture-part-1/" rel="nofollow noreferrer">http://jeffreypalermo.com/blog/the-onion-architecture-part-1/</a></p>\n'}, {'answer_id': 57396, 'author': 'Rob Walker', 'author_id': 3631, 'author_profile': 'https://Stackoverflow.com/users/3631', 'pm_score': 2, 'selected': False, 'text': "<p>I wouldn't put the interfaces into a separate assembly just for the sake of it. However, if the interfaces take part in any form of IPC or extensibility architecture then it often makes sense to give them their own assembly.</p>\n\n<p>If you have projects that need to reference each other, then yes, you will need a separate assembly for the interfaces, but you should also <strong>carefully</strong> examine architecture to see if there is another way of resolving the circular dependency.  </p>\n"}, {'answer_id': 57404, 'author': 'Anthony Mastrean', 'author_id': 3619, 'author_profile': 'https://Stackoverflow.com/users/3619', 'pm_score': 1, 'selected': False, 'text': '<p>I prefer keeping the most common or simple implementations of the interface in a sub-folder (and namespace) following the name of the interface.</p>\n\n<pre>\n\\project\\\n\\project\\IAppender.cs\n\\project\\Appender\\\n\\project\\Appender\\FileAppender.cs\n\\project\\Appender\\ConsoleAppender.cs\n</pre>\n\n<p>If I extend this class outside the project. In a special project, repeat the folders/namespace similarly.</p>\n\n<pre>\n\\specialproject\\\n\\specialproject\\Appender\\\n\\specialproject\\Appender\\MemoryAppender.cs\n</pre>\n'}, {'answer_id': 57428, 'author': 'Community', 'author_id': -1, 'author_profile': 'https://Stackoverflow.com/users/-1', 'pm_score': 0, 'selected': False, 'text': "<p>In the project I'm working on right now, the interfaces and related base classes go into assemblies that are logically divided among functions.  The implementations of these providers and classes go inside a core assembly.  The idea being that people who use our API can reference more or one of the API dlls in a clear and logical manner.</p>\n\n<p>Smaller applications don't need this kind of separation.  But, no matter where I keep the interfaces, I would keep them in the same namespace as any base classes.</p>\n"}]
['https://Stackoverflow.com/questions/57386', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/4231/']