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.
We are starting a new web application and we decided to use N-Tier design.
We have some disagreement about the objects that transfer data between layers (DTO),
should there be methods in them?
If it’s to organize the data from 2 databases, should we create one DTO for all layer per object? What is the standard?
We are reading the web application design by Microsoft.
DTO object is usaually a container for data and has no behavior. There are many ways of implementing the mapping between tiers using the DTO objects.
You could have some guidelines reading the article about DTO from MS pattern & practice team : http://msdn.microsoft.com/en-us/library/ff649585.aspx
There is another ressource on SO : How to effectively use DTO objects (Data Transfer Objects)?
You could also have a look on a working project sample “Microsoft – Domain Oriented N-Layered .NET 4.0 App Sample ” : http://microsoftnlayerapp.codeplex.com/ where many patterns are used and the DTO also.