While Entity Framework has a rather ignominious reputation for breaking backwards compatibility, it pales in comparison to the total rewrite undertaken for Entity Framework core. In this article InfoQ looks at some of the major feature changes and their repercussions.
In an effort to dramatically reduce confusion, ASP.NET 5.0 and Entity Framework 7.0 have been renamed to ASP.NET Core 1.0 and Entity Framework Core 1.0.
Shadow properties are fields that don’t exist in the class itself, but are treated as if they did by Entity Framework. They can participate in queries, create/update operations, and database migrations.
Entity Framework was created solely for working with relational data on the full version of .NET. In EF 7, neither of those statements is true.
Version 7 of Entity Framework represents a major redesign of the 6-year-old ORM. As such, Microsoft will not be recommending the initial release of EF 7 for existing projects. Rather, it is only meant for projects that are using ASP.NET 5 and .NET Core.
When a database administrators think of high performance data loading, they are thinking of bulk operations, a feature noticeably lacking in Entity Framework. But that doesn’t have to be the case. We recently spoke with Jonathan Magnan of ZZZ Projects about their new offerings.
Entity Framework is being rebooted with an initiative called “Entity Framework Everywhere”. The goal of this project is dramatically reduce both the complexity of Entity Framework and the resources needed to run applications that use it. This will in turn allow it to run on a wider variety of platforms including Windows Store and Windows Phone.
Microsoft recently added Entity Framework 6 support for DynamicData and EntityDataSource controls with in addition to refreshed the templates. It also has few known issues as the support is limited to C# and Web Application projects.
Entity Framework continues to have performance problems when using larger EDMX models to generate classes. “If the EDMX only has one entity type materialization takes 840 ms […] but when the EDMX contains a richer model, for example one with 67 entity types and 92 associations, the same test takes 7246 ms to complete”.
RadControls for WPF and Silverlight Q2 2013 SP1 with Entity Framework 6 Support and Several Features
Telerik has released RadControls for WPF and Silverlight Q2 2013 SP1 with the ability to change application icon set during runtime in addition to support for Entity Framework 6. It also provides an ability to pass event arguments to command when using Telerik EventToCommandBehavior in addition to several new features and improvements.
Microsoft has released Entity Framework Power Tools Beta 4 with support for Entity Framework 6 and Visual Studio 2013.
Microsoft has released release candidate version of Entity Framework 6 with support for interception, SQL logging, testability improvements. It also includes substantial changes to API, IntelliSense documentation.
The recent release of Telerik Reporting Q2 2013 SP1 includes support for enhanced graph interactivity, Entity Framework and context menus of Graph items in addition to bug fixes.
With their focus on Xamarin, the commercial version of Mono, it often seems like Mono is being is being neglected. But the nine year old platform is still seeing active development. Mono 3.0.12 brings with several new features including support for Portable Class Libraries and cookies in WCF.
As part of the beta 1 release, Entity Framework 6 has added new methods to DbSet: AddRange, RemoveRange, and FindAsync. But what will happen with IDbSet, the matching abstract interface?