Share via

EF6.1.3 RTM Available

  • Article

Today we are pleased to announce the availability of EF6.1.3. This patch release contains only high priority bug fixes.

 

What’s in EF6.1.3?

EF6.1.3 just contain fixes to high priority issues that have been reported on the 6.1.2 release. The fixes include:

 

Where do I get EF6.1.3?

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

 

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. We’ve already made a series of changes and accepted some community contributions into the code base for this next release. We don’t have a specific timeline for the release just yet.

Comments

  • Anonymous
    March 10, 2015
    Hi, thanks for the update. Will this be automatically rolled into EF7 as well? PS: what is your opinion about these requests (unrelated) visualstudio.uservoice.com/.../3725445-xna-5 visualstudio.uservoice.com/.../4233646-allow-net-games-on-xbox-one

  • Anonymous
    March 10, 2015
    Just installed E.F. 6.1.3 and again I'm having issues. See my blog post of december 22, 2014 on EF 6.1.2. This topic should have been covered in 6.1.3. My TPH solution that looks like this:   abstract class A;  (not mapped to any table) abstract class B:A (mapped to table X) abstract class C:A (mapped to table Y) class D:B class E:B ... class K:C etc. class A has a property "Extend" which is a complex type (lets call this ExtendA). This property is ignored via fluent API  Ignore(x => x.Extend). The inherited classes can have an "Extend" property that is derived from ExtendA and declared as new, hiding the base class Extend property. So my TPH model looks something like class ExtendA class ExtendB:ExtendA abstract class A {      public ExtendA Extend {get;set;} } abstract class B: A {   public new ExtendB Extend {get {return (ExtendA)base.Extend ;} set {base.Extend=value}} } Now with 6.1.3 I receive tons of validation errors during model generation. For every (derived) Extend property and all the complex properties in it I get an "EntityType has no key defined" error, which is weird because the Extend property is ignored within the OnModelCreating event via fluent api     I can imagine TPH is really complex, but my solution works well (and fast) in 6.1.1. Maybe this blog is not the right place to drop bugs. Please let me know if there is a better way to contribute. In the meantime I have to fall back again on EF 6.1.1.

  • Anonymous
    March 11, 2015
    #Thijs - the place to post bugs for EF or post other contributions is here: entityframework.codeplex.com/.../basic

  • Anonymous
    March 13, 2015
    The comment has been removed

  • Anonymous
    March 13, 2015
    @Dev - EF7 is actually a very different code base, so the changes here really don't apply. We have made some significant changes to how the query pipeline is factored in EF7, so we should avoid a lot of these issues where changes cause unexpected breaking changes in other areas (which is what a number of the fixes in 6.1.3 are related to).

  • Anonymous
    March 13, 2015
    @Thijs /cc @Igor - Thanks for the CodePlex issue, we are investigating at the moment and will follow up on CodePlex.

  • Anonymous
    March 13, 2015
    @Jon - could you open an issue with details of the query here entityframework.codeplex.com/.../Create

  • Anonymous
    March 20, 2015
    Hello, Do you have plans for Multi-tenant? thank you

  • Anonymous
    March 24, 2015
    The comment has been removed

  • Anonymous
    April 16, 2015
    Where can I have a look at the sources? We have an issue with DbSet.AddOrUpdate and I'd like to review the bits to make sure the issue is not in EF 6.1.3

  • Anonymous
    April 21, 2015
    I prefer downloads other then nuget. We normally put all things to install for a version in one folder so it can be reinstalled after years. Don't know if nuget exists then. This is end-of-usage for EF for us.  

  • Anonymous
    May 12, 2015
    @Fabricio (cc @Jon) – If you are storing data in separate tables (i.e. each tenant has a table prefix, schema, etc) then this already works. You can just write login in OnModelCreating to adjust the mapping for the appropriate tenant (romiller.com/.../ef-4-1-multi-tenant-with-code-first).  If you are storing data in the same tables then there isn’t native support at the moment but you could use something like query interceptors to add the appropriate filtering to each query.

  • Anonymous
    May 12, 2015
    @Tom de Koning – Source code is here entityframework.codeplex.com.

  • Anonymous
    May 12, 2015
    @Not nice – You can always just download the NuGet package (either login to NuGet.org and you will get a download link, or just grab the package off disk after you install it via NuGet). You can point NuGet at your local folder that contains the downloaded versions of the packages. Alternatively, if you really don’t want to use NuGet then download the package and grab the binaries out of it.

  • Anonymous
    May 12, 2015
    @"Not Nice" download would be here: www.nuget.org/.../6.1.3 just unzip the .nupkg file and grab the DLLs from the lib folder.

  • Anonymous
    July 17, 2015
    How do I configure the new project.json file to include a specific ADO.NET provider for Oracle 12c? I am currently getting the following error; "Unable to determine the provider name for provider factory of type 'Oracle.ManagedDataAccess.Client.OracleClientFactory'. Make sure that the ADO.NET provider is installed or registered in the application config."

  • Anonymous
    August 12, 2015
    The comment has been removed

  • Anonymous
    September 21, 2015
    Where is the tooling for creating EF Models in VS 2015? Creating a model using the reverse engineering approach on existing databases is the only way we use EF. The Wizard in VS 2012 and 2013 made this process really simple and really fast. Without this functionality we cannot Visual Studio 2015.

  • Anonymous
    October 19, 2015
    The comment has been removed

  • Anonymous
    October 19, 2015
    @Fosol – Are you using a NuGet package to get the Oracle ADO.NET implementation? If so, I suspect that package uses an install script to add the config for the oracle provider to the config file… but install scripts and web.config are not supported on ASP.NET 5. You probably need to manually register the provider factory using machine.config.