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.
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.
Since .NET 4 was released Microsoft has been pushing an ever faster release cadence for its .NET libraries with new features coming out every few months instead of every few years like it had done in the past. As a result of a recent embarrassment, the ADO.NET team is moving back to using beta releases and, to reduce future confusion, adopting the concept of Semantic Versioning.
The introduction of a Code First option in Entity Framework has received quite a bit of praise. While it still has a long way to go before it unseats the reigning ORM, nHibernate, the progress Microsoft is making is quite astounding. In order to keep the momentum up Microsoft is releasing a set of power tools that will take an existing database and create a Code First representation.
ADO.NET Entity Framework 4.1 is upon us – slated for a late April release, it will come with a whole set of new features, but not all of them are going to make it.
Earlier this month the ADO.NET team released CTP5 of their Entity Framework Code-First library. The library is meant to provide a code-centric workflow for developers when working with data.