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?
In order to support the new open source model for Entity Framework, it had to cut its ties to the core distribution of the .NET Framework. Unfortunately this required a breaking change to the namespaces exposed by the ORM in version 6.
Much has been written on the topic of ORMs and its failings. Most of the objections fall into two categories: Separation of Concerns and Object Oriented Design. For the Entity Framework we have good news for one these.
Developer Ricardo Peres of Portugal has published a seemingly unbiased comparison of the leading .NET ORMs: NHibernate and Entity Framework. While we recommend anyone considering both to read his article, Differences Between NHibernate and Entity Framework, we are going to tough on some of the key differences.
With the release of .NET 4.5 nearing, Microsoft has started to pull back the curtain on the next version of their development platform. While there has been a lot of fanfare around Metro and Windows 8, the improvements made to the core features of .NET, which have traditionally focused on web, service, and data development, may steal the show in the short term.
For those .NET developers who still choose to work directly with the DataReader series of classes, .NET 4.5 brings some new async and streaming support your way.
Entity Framework 4.3 release finally brings the Migrations feature to Developers, without having to depend on separate pre-release binaries.
The Code First approach means that the object model is created in code, and then the database structure is generated from that model. Code First Migrations allows developers to make changes to the database via code, many of which can be done automatically.