Want the difference between POCO and DTO in C#

Question

1.00/5 (1 vote)

See more:

Anybody can explain about the difference between the
POCO and DTO objects in c# with example
and also go through the below link
in the below link having four types to transfer data from one layer to another layer
i cant under the link explanations

Four ways of passing data between layers[^]

What I have tried:

please help me out from the confusion

Posted 28-May-19 21:58pm

Member 14374813

Updated 28-May-19 22:14pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

lmoelleb · Answer 1 · 2019-05-28T22:15:00

DTO describes what an object is used for. POCO describes how it is implemented.

A lot of (old) frameworks require your objects to have a specific base class or implement a specific interface to work.

So if you wanted to use the framework X to store data in your database, then your class must be derived from XBase or implement XInterface. All fine until you want to support multiple storage systems, need another base class for another framework in another layer....

When using framework specific base classes or interfaces is NOT required, we often say the framework works with Plain Old C# Objects.

A DTO is a DataTransferObject. In is just a class that contains no business logic - only data (typically in the form of public properties). It is typically used between layers.

Most DTOs today are implemented as POCO - and I recommend you stick to this as well - but this is certainly no requirement for it to be a DTO. If the object is used for Data Transfer only, then it is a Data Transfer Object no matter how it is implemented.