Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there a standard for how solutions/projects are organized in regards to interfaces and the classes that implement them? I’m working on a an MVP, DDD application and would love to hear feedback as to how others layout their projects and why they do it that way. Thanks!!
They should live in the namespace that is logical for them; this means that there’s no firm rule for whether or not they should reside in the same namespace. You’ll find relatively abstract namespaces often don’t live alongside their implementation, whereas interfaces that are more 1:1 with their implementors are more likely to remain alongside one another.
A more important consideration is to keep the interfaces consumable for reuse–normally this means more consideration given to what goes into the assembly alongside the interfaces, rather than the namespaces.