The DTOs should live in the same project that defines your service interfaces. The interfaces are the operations your service consumers can request, and the DTOs are the messages passed into and out of those service methods.
The Object -> DTO transformers (aka mappers, aka assemblers) should live behind the service boundary, and (depending on your needs) will probably not be exposed to your clients. Keeping them separate means your DTO objects are just dumb data contracts while the objects that create them are behind the service boundary and under your control. By the way, I highly recommend AutoMapper (http://www.codeplex.com/ AutoMapper) for simplifying your domain -> DTO mapping. Does that help answer your question? -cg --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
