Hi Scott,

I have studied your code for a while and I am used to see you define all the IxxxRepository inside the Model.

However, when it comes to IxxxService as in Chapter 6, you put the interfaces under a special Contract name space.

Is it because you use WCF in chapter 6? Or is it generally a good idea to have a special Contract and DataContract for the Interfaces for the Service layer?

What about IxxxRepositories? Should we define them and the DTO's outside of Model, and let both the Service and Repository reference them?

Hi SamVan,

I define the repository interfaces within the model because domain services may need to use them at some point. I use projects to help define responsibility boundaries but you could do just the same with namespaces and folders all within one class project.

I did this to emphasis the responsibilities of each part of the WCF implementation also the client code will use the Contract and DataContract but I didn't want the client having a reference to the actual service implementation, this is why I split them up.

Not sure what you mean with this question. What are the IxxxRepositories?

Cheers
Scott

"IxxxRepository" sorry, my typo.

Ok, I guess I know what you are saying: If I am not distributing the objects, I can define everything in a single project -> just put different layers separately into folders and use different namespaces. And if I somehow need to use WCF, I will have to put the interface and DTO into a dll of their own so that the client and the server at different locations can reference them separately.

The location of the Interface definition depends on the context and the software architecture, and there is not an answer that is correct in all situations.

Am I right?

Thanks Scott

Yep you've got the idea. Remember context is king.

Cheers
Scott