Partilhar via

EF6.1.3 Beta 1 Available

  • Artigo

Today we are making Beta 1 of the EF6.1.3 release available. This patch release contains only high priority bug fixes.

 

What are the 6.1.3 release timelines?

At this stage we are planning for our next release to be the RTM. This may change if we get additional reports of high priority bugs that we decide should be fixed in 6.1.3.

We expect to ship the next release sometime next month but this may change if we decided to take additional changes.

 

What’s in Beta 1?

EF6.1.3 will just contain fixes to high priority issues that have been reported on the 6.1.2 release. The fixes included in beta 1 are:

 

Where do I get the beta?

The runtime is available on NuGet. 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 Visual Studio 2013 is available on the Microsoft Download Center.

 

Support

This is a preview of changes that will be available in the final release of EF6.1.3 and is designed to allow you to try out the new features and report any issues you encounter. Microsoft does not guarantee any level of support on this release.

If you need assistance using the new features, please post questions on Stack Overflow using the entity-framework tag.

Comments

  • Anonymous
    February 16, 2015
    The comment has been removed

  • Anonymous
    February 16, 2015
    @Jon - The issue you are hitting should be resolved by entityframework.codeplex.com/.../2673 which we are planning to get in to RTM (we're using a flag to toggle between functionality so it's a low risk fix and not something we'll delay the RTM for).

  • Anonymous
    February 16, 2015
    Thanks Rowan. Much appreciated. Yeah, that looks like the issue that I ran into. I'm looking forward to being able to upgrade beyond 6.1.1 because 6.1.2 does seem to speed up initialization of the context by a noticeable amount.

  • Anonymous
    March 04, 2015
    I just ran into a problem where I was using Include() to make EF pull the data all in using SQL JOINs for a query, but, even though I could see that it was doing JOINs in the initial query, eventually it tried lazy loading one of the properties using a sub-query. I don't know if this is a known issue or not. The main reason that I noticed it is because I'm using the MySQL driver which doesn't support multiple active result sets which caused an exception.

  • Anonymous
    March 13, 2015
    @Jon - Could you open an issue and include code that demonstrates the issue? entityframework.codeplex.com/.../Create