0

What is the importance of POCO support in Entity Framework?
Maybe its better to ask What is the uses of POCO ?

Shahin
  • 12,543
  • 39
  • 127
  • 205
  • possible duplicate of [Define 'poco'?](http://stackoverflow.com/questions/250001/define-poco) – Ladislav Mrnka May 09 '11 at 07:36
  • 4
    Go through already asked questions: http://stackoverflow.com/questions/725348/poco-vs-dto http://stackoverflow.com/questions/250001/define-poco http://stackoverflow.com/questions/2478081/entity-framework-4-poco-where-to-start – Ladislav Mrnka May 09 '11 at 07:38
  • @Ladislav Mrnka Yes, the last link covers it well – sra May 09 '11 at 07:43

2 Answers2

1

Realy short: That you have objects that didn't know anything about the EntityFramework but are bound to it (Bound to the context so that the EntityFramework can take care).

sra
  • 23,820
  • 7
  • 55
  • 89
1

Actually POCO is similar to POJO (Plain old java objects) in .net world. POCOs are objects tha don't have to follow any particular conventions (implementing any interface ,extending any class,having special attributes or naming convention etc.)

Some of the persistent frameworks force us to use specific interfaces or attirbutes , abstract classes. This is not a problem as long as you are working on a project from scratch and you are choosing which framework to use but if you are working on a legacy system and want to change its data access layer to use a persistent framework , it might have a negative impact.

Beatles1692
  • 5,214
  • 34
  • 65