Now that Visual Studio 2010 and .NET Framework 4.0 have been released, users of Entity Framework can use POCO objects with Entity Framework without the need for wrapper layers such as EFPocoAdapter . Since I know a number of people are using EFPocoAdapter in their production applications and it is not...

We have recently published Visual Basic versions of our MSDN Code Gallery samples for Entity Framework v3.5SP1. The following translated samples are currently available in two languages (C# and VB) ADO.NET Entity Framework Query Samples http://code.msdn.com/EFQuerySamples Persistence Ignorance...

I've just posted another round of updates to EF POCO Adapter based on feedback from users. This set of changes is focused on N-tier scenarios and detached entities (it adds missing wrappers for EF APIs and fixes behavior of existing ones). Change log: Added wrapper for ObjectContext.ApplyPropertyChanges...

I've just posted updates to EF POCO Adapter (v1.02) which resolves a couple of issues spotted by users: Detached proxies (created by EFPocoContxt.CreateObject<T>) as well as proxies in the Added state were failing on property navigation. This has been fixed, and the property navigation doesn't...

One of the limitations of Entity Framework V1 released as part of .NET Framework 3.5 SP1 and Visual Studio 2008 SP1 is lack of support for POCO entity objects. POCO stands for Plain Old CLR Object and refers to an object that does not have any persistence concerns and is not aware of persistence framework...