共用方式為

EF 6.1.1 RTM Available

  • 發行項

Today we are pleased to announce the availability of EF6.1.1. This patch release includes a number of high priority bug fixes and some contributions from our community.

 

What’s in EF6.1.1?

You can see a list of the fixes/changes included in EF6.1.1 on our CodePlex site.

In particular, we’d like to call out the following two fixes to issues that a number of people have encountered:

 

Where do I get EF6.1.1?

The runtime is available on NuGet. Follow the instructions on our Get It page for installing the latest version of Entity Framework runtime.

The tooling for Visual Studio 2012 and Visual Studio 2013 is available on the Microsoft Download Center. You only need to install the tooling if you want to create models using the EF Designer, or generate a Code First model from an existing database.

 

Thank you to our contributors

We’d like to say thank you to folks from the community who contributed features, bug fixes, and other changes to the 6.1 release:

 

What’s next?

In addition to working on the next major version of EF (Entity Framework 7), we’re also working on another update to EF6. This update to EF6 is tentatively slated to be another patch release (EF6.1.2) and we are working a series of bug fixes and accepting pull requests.

If you want to learn more about our plans for EF7, see our recent EF7 - New Platforms, New Data Stores post.

Comments

  • Anonymous
    June 20, 2014
    All of my code based on EntityStoreSchemaGenerator and EntityModelSchemaGenerator broke when I upgraded. Is there a replacement for these classes?

  • Anonymous
    June 20, 2014
    How are cascade deletes behaving in EF 6 ? Do they still just cascade only to objects in memory ? Isn't this just strange and inefficient for the end user ?

  • Anonymous
    June 20, 2014
    Will we get the PDBs/Source this time via Symbol/Source Server for 6.1.1 RTM?

  • Anonymous
    June 20, 2014
    sorry I was not clear in my last post because I did not know what was going on behind the scenes regards cascading deletes. With EF code first as it stands today I get really confused how to set cascading rules in OnModelCreating(DbModelBuilder modelBuilder) and literature about it is a bit lacking. I don't know what is done by default when no rules are set in OnModelCreating. I'm also not sure if reverse engineering an existing database translated into the proper rules re. cascading deletes. Having said that, I have the following problem at the moment. Suppose we have a parent->child relationship and if the parent is deleted, I want the child relationship to the parent set to NULL. Let's say the parent is deleted from DbContext (in memory only) before SaveChanges takes place. The end user decides to Cancel these changes because he did this by mistek. So to cancel this delete we do something like this...                foreach (var entry in context.ChangeTracker                    .Entries<parent>()                    .Where(u => u.State == EntityState.Deleted))                {                    entry.State = EntityState.Unchanged;                } The problem is that cascading changes to the children loaded in dbcontext would already have taken place and a SaveChanges will send these changes to database. How can I stop this from happening ?

  • Anonymous
    June 21, 2014
    @James079 Why not simply dispose without saving and re-query the data, and let user know don't do such a mistake again :).

  • Anonymous
    June 22, 2014
    @guest While I'm aware that short lived instances of dbcontext is the way to go, this is not always the case in LOB desktop applications. What's the purpose of implementing these cascading changes in EF if the programmer going to dispose of dbcontext and reload data from the database anyway ?

  • Anonymous
    June 23, 2014
    Can anyone help explain why the "Version" in Reference Properties is showing as 6.0.0.0 even though I'm referencing a 6.1.1 DLL in "..EntityFramework.6.1.1libnet45EntityFramework.dll" ?

  • Anonymous
    June 23, 2014
    Addendum to Ed's question: when I run it through ildasm it identifies the Assembly version as 6.0.0.0

  • Anonymous
    June 24, 2014
    I experience a massive performance problem with EF 6.1.1 on SQL CE. This bug was known and pushed back to 6.1.2, because you didn't think the impact was that big: entityframework.codeplex.com/.../2296 Maybe you'll test performance not just with SQL Server?

  • Anonymous
    June 24, 2014
    @Ed Blake entityframework.codeplex.com/.../1753 entityframework.codeplex.com/.../41993a3d1ae5b4515d51adbef3419b0af36de6bb

  • Anonymous
    June 25, 2014
    @Daniel You should be able to get a verify the fix from the nightly builds

  • Anonymous
    June 25, 2014
    @ErikEJ I installed the latest build (6.1.1-beta2-30625), the problem still exists.

  • Anonymous
    June 26, 2014
    @Joel - There is a discussion on those classes here - entityframework.codeplex.com/.../461241. They currently aren't available in EF6, but we can look at enabling scenarios you have. @James079 - The child entities should be marked as modified too (since the FK value will have changed to null), could you simply mark them as Unchanged too? @Andre.Ziegler - We we're still blocked by an issue with Symbol Source. I've just moved the work item back onto our triage list to see if we are unblocked now.

  • Anonymous
    June 26, 2014
    @Ed Blake & @Luke Pryor - We keep the assembly version the same so that tooling compiled against EF (e.g. MVC Scaffolding) can continue to work with whatever version you have installed in your project. If you look at FileVersion or AssemblyInformationalVersion you will see 6.1.1. @Daniel  - Any chance you could open a new issue and include code that demonstrates the issue you are still experiencing? The exact scenario in issue #2296 is fixed in our nightly builds, but you may be hitting the same outcome via a different code path.  entityframework.codeplex.com/.../Create

  • Anonymous
    June 26, 2014
    @Daniel Sadly, support for SQLCE from Microsoft is going downhill all the time. We decided to switch to LocalDb six months ago and have not regretted it. At least a new version was included with SQLServer 2014! See: stackoverflow.com/.../is-sql-server-compact-discontinued-from-visual-studio-2013

  • Anonymous
    June 26, 2014
    @Rowan Miller ok, I voted for the workitem: entityframework.codeplex.com/.../386 Hopefully you can fix this.

  • Anonymous
    June 26, 2014
    @Rowan Miller - I have created an issue: entityframework.codeplex.com/.../2369 @DabblerNL - Unfortunately, LocalDB is not an option for us. Some of our customers still run XP...

  • Anonymous
    June 28, 2014
    Where did EntityConnectionStringBuilder go? I can't find it using ISpy either.

  • Anonymous
    June 28, 2014
    Nevermind.  The NuGet upgrade just removed the reference to System.Data.Entity for some reason.

  • Anonymous
    June 29, 2014
    @Casey: the correct namespace for EntityConnectionStringBuilder in this (and in any 6.x) version of EF is System.Data.Entity.Core.EntityClient. For EF6 we moved all of EF to the NuGet package ad we had to change namespaces of existing types in .NET framework to avoid conflicts in some scenarios. The references to System.Data.Entity.dll is in fact removed by the EF NuGet package at installation time to help you in the upgrade process. For more information on upgrading your applications to EF6 or later please see this section in the documentation: msdn.microsoft.com/.../upgradeef6

  • Anonymous
    August 09, 2014
    when will have beta of 6.1.2 as i see codeplex has some fixed issue

  • Anonymous
    August 12, 2014
    @kym - There isn't a lot checked into 6.1.2 just yet (which is why we haven't released a beta), but you can use the nightly builds if there is a particular change that you are after - entityframework.codeplex.com/wikipage.