Why POCO is required in entity framework

Question

0.00/5 (No votes)

See more:

Hi,

I have just started learning entity framework for .net 4.0. But I didn't understand the need of POCO(Plain Old CLR Object) in it.

Please let me know the need of POCO with some good example if you have any idea. Waiting for your response. Thanks in advance..:):)

Posted 10-Jun-12 19:48pm

Sujeet Pardeshi

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)

db7uk · Answer 1 · 2012-06-10T22:37:00

a good starting point is here:
http://blogs.msdn.com/b/adonet/archive/2009/05/21/poco-in-the-entity-framework-part-1-the-experience.aspx[^]

and here:

http://thedatafarm.com/blog/data-access/agile-entity-framework-4-repository-part-1-model-and-poco-classes/[^]

POCO's are used all over the place and commonly used as DTO's (Data transfer objects) via data services. POCO's are literally objects that just have properties which are populated via routines. The POCO properties will / should only have well known .net types such as string, int, double etc...

added to the above, used with the Repository and Unit of Work pattern these "Basic" objects will be extreamly important to data operations.
http://huyrua.wordpress.com/2010/07/13/entity-framework-4-poco-repository-and-specification-pattern/[^]