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.
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?
Put your domain objects and interfaces in a seperate ‘domain’ assembly.
This assembly should never reference anything but the core .net assemblies.
This way you get a clean seperation from your domain/service model and your implementation.
Edit:
http://jeffreypalermo.com/blog/the-onion-architecture-part-1/