Migrating from EF POCO Adapter to Entity Framework v4.0

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 supported, I recommend they migrate…


Using EFProviderWrappers with precompiled views

One of the users has reported a problem with using EFProviderWrappers and precompiled views together. When you pre-compile views, Entity Framework calculates a hash of metadata (which includes csdl,ssdl and msl information), stores it with the generated views and compares it later when metadata is loaded. When loaded metadata doesn’t match the hash stored in…


Tracing and Caching for Entity Framework available on MSDN Code Gallery

We have just released a sample that shows how to extend Entity Framework in interesting ways by plugging into ADO.NET provider interface. The sample provides two extensions: EFTracingProvider – which adds the ability to log all SQL commands that are executed (similar to LINQ to SQL’s DataContext.Log EFCachingProvider – which adds transparent query results cache…


Entity Framework samples converted to Visual Basic

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 Sampleshttp://code.msdn.com/EFQuerySamples Persistence Ignorance (POCO) Adapter for Entity Frameworkhttp://code.msdn.com/EFPocoAdapter Transparent Lazy Loading for Entity Frameworkhttp://code.msdn.com/EFLazyLoading The samples have been fully converted to…


New posts on EF Design Blog

I’d like to turn your attention to two blog posts on EF Design Blog about exciting new features planned for Entity Framework: Foreign Key Support – we’re introducing new type of association, which can be manipulated through references OR foreign key values available on entities themselves. We believe that this will greatly improve scenarios such…


N-Tier Improvements for Entity Framework

We have recently published an article on API changes that we want to make in next version of Entity Framework in order to enable more N-Tier scenarios. Getting this right is very important to us and we’re interested in getting as much of your feedback on the proposed design as possible. Please read and comment…


Using EF Oracle Sample Provider with EDM Designer

Many people are asking if it is possible to use EFOracleProvider with EDM Designer in Visual Studio 2008 SP1. The answer is yes, but because the sample doesn’t include a DDEX provider required for VS integration, there are certain steps that have to be run manually. I’ve compiled a step-by-step guide for those interested in…


EF POCO Adapter updated (v1.03)

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() to IEntitySet<T> Added wrapper for ObjectContext.Detach() to IEntitySet<T>…


EF POCO Adapter updated (v1.02)

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 attempt the load in one of these states. Thanks to…


Persistence Ignorance (POCO) Adapter for Entity Framework V1

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….