The official source of information on Managed Providers, DataSet & Entity Framework from Microsoft
The information in this post is out of date.
EF6 RTM is now available.
Visit msdn.com/data/ef for the latest information on current and past releases of EF.
Since releasing Alpha 3 a few months ago, we've been working hard to add the remaining new features to the EF6 runtime and get the EF tooling ready to preview. Today we are pleased to announce the availability of EF6 Beta 1.
You can help us make EF6 a great release by providing feedback and suggestions. You can provide feedback by commenting on this post, commenting on the feature specifications linked below or starting a discussion on our CodePlex site.
This is a preview of features that will be available in future releases and is designed to allow you to provide feedback on the design of these features. It is not intended or licensed for use in production. The APIs and functionality included in Beta 1 are likely to change as we polish the product ready for the final release of EF6.
If you need assistance using the new features, please post questions on Stack Overflow using the entity-framework tag.
The runtime is available on NuGet. If you are using Code First then there is no need to install the tooling. Follow the instructions on our Get It page for installing the latest pre-release version of Entity Framework.
The tooling is available on the Microsoft Download Center and will work with Visual Studio 2012. Install the tooling if you want to use Model First or Database First.
Note: In some cases you may need to update your EF5 code to work with EF6, see Updating Applications to use EF6.
Migrations created with earlier previews of EF6 will need to be recreated due to some changes we made to the metadata stored in code behind. We realize that changes like this can be frustrating. One of the reasons we release early previews is to get your feedback and bug reports to help us make the final release great. Sometimes that means we need to make breaking changes between preview releases.
To recreate migrations, downgrade to the last migration created with EF5 or earlier, delete migrations from your Migrations folder that were created with EF6, then use Add-Migration to re-scaffold the changes you have made. If migrations are not re-created you will receive the following error when trying to add or apply migrations:
System.Data.Entity.Core.MappingException: Schema specified is not valid. Errors: <File Unknown>(0,0) : error 2025: XML Schema validation failed for mapping schema. Schema Error Information : The 'http://schemas.microsoft.com/ado/2012/10/edm/migrations:IsSystem' attribute is not declared.
When you install the Beta 1 tooling it will replace the EF Designer that was included in Visual Studio 2012. To revert back to the tooling that was included with Visual Studio 2012 follow these steps.
The following features and changes have been implemented since Alpha 3:
The following features and changes were included in earlier previews of EF6.
Beta 1 contains all the features we are planning to implement for the EF6 release. We'll now be focusing on polishing and completing these features, fixing bugs and everything else to make EF6 a great release. We’ll still consider pull requests for the EF6 release but larger changes or ones that need significant testing will likely be moved to the following release.
If you want to try out changes we've made since the last official pre-release, you can use the latest signed nightly build. You can also check out our Feature Specifications and Design Meeting Notes or follow us on Twitter and Facebook to stay up to date with what our team is working on.