EF6.0.2 RTM Available

  • Article

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 the 6.0.2 release available.

 

Getting EF6.0.2

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 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 use Model First or Database First.

 

What’s in the 6.0.2 Patch

The 6.0.2 patch includes fixes to some performance and functional issues that were introduced in the 6.0.0 and 6.0.1 releases. You can view a full list of the issues on our CodePlex site.

 

What’s not in the 6.0.2 Patch

In addition to the issues fixed in the 6.0.2 patch our team is working on other performance improvements, bug fixes and features for the EF6.1 release. You can see a full list of what’s currently in this release on our CodePlex site. Note that this is not a final list and plans will change as we progress on the release. We’ll start providing pre-releases of EF6.1 in the near future.

Comments

  • Anonymous
    December 16, 2013
    The comment has been removed

  • Anonymous
    December 17, 2013
    @Jon - Are you using Dynamic Data? We have an update to EDSC internally but we were waiting to publish anything until the Dynamic Data team has made the required updates at their end too. If we see folks who want to use EDSC without Dynamic Data then we could look at publishing it sooner.

  • Anonymous
    December 18, 2013
    If I install the updated tooling, will I still be able to work with older projects? (Is the tooling backwards compatible?)

  • Anonymous
    December 18, 2013
    @Stephen - Yes, tooling will continue to work. It does support both EF5 and EF6.

  • Anonymous
    December 19, 2013
    The comment has been removed

  • Anonymous
    January 09, 2014
    Actually, if you do not install tooling, even if you only use CodeFirst, you get the following warning: "Found conflicts between different versions of the same dependent assembly. In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; otherwise, add the following binding redirects to the "runtime" node in the application configuration file: <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"><dependentAssembly><assemblyIdentity name="EntityFramework" culture="neutral" publicKeyToken="b77a5c561934e089" /><bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" /></dependentAssembly></assemblyBinding>" So, I would say, installing tooling is a good idea even if you do not use Model/Database first.

  • Anonymous
    January 14, 2014
    @TPersistent - You shouldn't need to install the tooling to use Code First. If you are able to provide steps to reproduce the issue you are seeing then please file a bug report on our CodePlex site - entityframework.codeplex.com/.../Create.

  • Anonymous
    January 17, 2014
    It is just a warning that goes away after tooling is installed. No big deal. If anyone else gets the warning and wants to get rid of it – just install the tooling. Thanks

  • Anonymous
    January 25, 2014
    hi i am using spatial data . but in my data access later that is a class library  it dont work but in  it wirking very well why?

  • Anonymous
    January 30, 2014
    @bahman - Probably best to start a new thread on StackOverflow.com with more details of the issue you are having. Make sure you include sample code and use the entity-framework tag.

  • Anonymous
    February 24, 2014
    I want to know if it is right even to use Database Model First? ASP.NET Webforms in 4.5.1, and I try to use the EntityDataSource control and get a general error that says: The provider did not return to ProviderManifest Instance, please can tell me how this object?

  • Anonymous
    February 26, 2014
    @Flavio Cortes - To use EntityDataSource with EF6 you need to get an updated version of it. See this post for more details - blogs.msdn.com/.../preview-of-dynamic-data-provider-and-entitydatasource-control-for-ef6.aspx.