Does anyone use the POCO Adapter for Entity Framework in production?

Question

Reading that Entity Framework lacks persistence of ignorance I often stumble upon the POCO Adapter . The question is, does anyone use it in production, how it goes and what are the pitfalls?

I consider two alternatives for application design: use POCOs with this adapter in business logic and make the presentation layer use them or create a service level transformation between EF and DTO objects: (1) EF objects ↔ Adapter ↔ POCO business objects ↔ Presentation or ( 2) EF objects ↔ Service level ↔ DTOs ↔ Presentation. The first approach seems to be cleaner, but I somewhat doubt that the POCO adapter is not a very standard solution and may contain some disadvantages that are not obvious right now.

Answer 1

EFPocoAdapter Entity Framework 4.0. - , - 1, MSDN.

EFPocoAdapter. ADO.NET Entity Framework EF 4.0, .

: POCO Entity Framework: 1 - .

EFPocoAdapter, / POCO, n-. Entity Framework , T4 , , -, ( POCO). , , JavaScriptSerializer, , DataContractSerializer, , class/member, T4 .

EFPocoAdapter EF 4.0. , , . ( ).

Answer 2

, AutoMapper. EF, POCO DTO-s, . , , AutoMapper.

AutoMapper

Answer 3

, Entity Framework v4 POCO, # POCO Generator ( ), .

There are a few catches when using them with WCF services, although, therefore, if you plan to expose them through WCF, it might be worthwhile putting together a reasonable proof of concept and see if the complexity of the graphic object presents any problems for serialization, use of idle ones, etc. .d. etc.