Posts Tagged ‘Migrated Post’
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 pre-compiled views, an exception is thrown. […]
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 to EF
The sample comes with implementation of distributed cache which uses Velocity CTP 3 as well as an adapter for ASP.NET and simple in-memory cache implementation. […]
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) […]
I’d like to turn your attention to two blog posts on EF Design Blog about exciting new features planned 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. […]
Many people are asking if it is possible to use EFOracleProvider with EDM Designer in Visual Studio 2008 SP1. […]
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). […]
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. […]
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. Modern development approaches such as DDD (Domain-Driven Design) and TDD (Test-Driven Development) prefer clear separation of concerns which implies persistence ignorance. […]
We have recently published a sample called EFPocoAdapter that includes code generator and a supporting library that implements POCO object tracking on top of Entity Framework V1. […]
I wanted to let you know that we have just released Sample Entity Framework Provider for Oracle on MSDN Code Gallery.
The provider is implemented using essentially the same technique as EFSampleProvider, but targets System.Data.OracleClient […]