EF6.0.2 Beta 1 Available on NuGet

We recently shared our plans to produce a 6.0.2 patch release to address some performance issues (and other bugs) in the 6.0.0 and 6.0.1 releases. Today we are making Beta 1 of the 6.0.2 release available.

 

Why the beta?

We were originally planning to go straight to RTM and have the 6.0.2 patch available in the month of November. Some of the fixes are proving harder to implement and test/verify than we expected, so we need a bit more time to finish the fixes and ensure that performance is improved. In order to keep our commitment to have a release available this month, we’ve opted to release the current code base – which includes a number of improvements – as a beta.

 

Can I use it in production?

Yes, with some caveats. The license does not prevent you from using the release in production. We’re still testing the changes we’ve made and there are more changes still to come. Microsoft does not guarantee any particular level of support on this beta. 

 

Where do I get the beta?

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 runtime.

The tooling for Visual Studio 2012 and 2013 is available on the Microsoft Download Center. You only need to install the tooling if you want to use Model First or Database First.

Note: If you are installing the tools for Visual Studio 2012, you will need to uninstall the existing Entity Framework Tools for Visual Studio 2012 (via Add/Remove Programs) before installing the new MSI. This is due to a temporary issue with the Beta 1 installer that will be fixed for RTM.

 

When can I expect the RTM?

Getting the 6.0.2 patch release to RTM is our teams top priority. We expect to have it available during December.

 

What if I find an issue in the beta?

Make sure it’s not something we already know about that is tracked to be fixed in 6.0.2. If it’s not, please file a new issue – be sure to include detailed steps on how to reproduce it, preferably including source code. 

 

What’s in the beta?

Fixes to the following issues are included in Beta 1. We haven’t finished verifying all these issues..

• [Performance] Startup time is bad with debugger attached
• [Performance] Buffered queries are executed in non-sequential mode
• [Performance] Revert buffering by default
• [Performance] Remove calls to BufferedDataReader.AssertFieldIsReady
• Memory leak in case of usage an external connection
• “The given key was not present in the dictionary.” when adding Association to Entities - all mapped to Views
• Code first stored procedure mapping fails when the stored procedures have more than 25 parameter mappings
• EF6 regression: identity pattern not applied to key by convention in simple inheritance scenario
• [UpForGrabs] Remove EF.PowerShell.dll from SqlServerCe package
• Race condition in InitializeMappingViewCacheFactory
• Migrating from EF5 to EF6: InversePropertyAttribute broken?
• Code First: TPC with joins from base class to Identity ApplicationUser Fails
• Moving from EF5 -> EF6: Invalid Column Name error
• Having System.ComponentModel.DataAnnotations.MaxLength() applied to a string property leads to InvalidCastException exception
• Unable to cast Anonymous Type from 'System.Linq.IQueryable' to 'System.Data.Entity.Core.Objects.ObjectQuery'
• Designer: Can not reverse engineer EDMX when FKs in different order than PKs (composite keys)
• EF Configuration Cause Null Reference Exception.
• Stored Procs :: Concurrency check on value types in conjunction with stored procedures doesn't work properly
• TypeLoadException thrown for a class nested in an internal class

Comments

• Anonymous
  December 03, 2013
  I can successfully install this nuget package but if I then install the EntityFramework.SqlServerCompact 6.0.2-beta1 package I get the following error: Unable to resolve dependency 'EntityFramework (≥ 6.0.2-beta1-21126). I have installed the 6.02 tooling for vs 2013 as well.

• Anonymous
  December 05, 2013
  @Brian - We've just uploaded a new EntityFramework.SqlServerCompact package that resolves this issue.