New features in the Entity Framework support!

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Locked
Devart
Site Admin
Posts: 3802
Joined: Tue 26 Oct 2004 13:51

New features in the Entity Framework support!

Post by Devart » Thu 03 Dec 2020 19:10

Dear users,

We are glad to announce the new features that are available in the Entity Framework support in the latest version. dotConnect for Oracle, MySQL, PostgreSQL, and SQLite now support Entity Framework Core 5.0. Please note that it comes with breaking changes to Devart.Data.***.EFCore NuGet packages. These packages previously contained the corresponding Devart.Data.***.Entity.EFCore.dll assemblies for different Entity Framework Core versions:
  • EF Core 1 assembly (.NET Standard 1.3)
  • EF Core 2 assembly (.NET Standard 2.0)
  • EF Core 3 assembly (.NET Standard 2.1)
Now the assemblies and their .NET Standard compatibility changed in this packages. They now contain assemblies for the following Entity Framework Core versions:
  • EF Core 1 assembly (.NET Standard 1.3)
  • EF Core 3 assembly (.NET Standard 2.0)
  • EF Core 5 assembly (.NET Standard 2.1)
Note that these packages does not contain an assembly for Entity Framework Core 2 anymore. This assembly is now available only via the installer of the corresponding dotConnect provider. It installs it into \Entity\EFCore2\netstandard2.0\ subfolder of the provider installation folder.

This means that if you used this NuGet package in your project, using Entity Framework Core 2, the project will be automatically upgraded to Entity Framework Core 3 when updating our NuGet package. Note that there are breaking changes between Entity Framework Core 2 and 3. And if your project used Entity Framework Core 3, it will be upgraded to Entity Framework Core 5.

If you want to stay on Entity Framework Core 2, you need to do the following things:
  • Delete the Devart.Data.***.EFCore package from your project
  • Add the Devart.Data.*** package instead.
  • Add the Microsoft.EntityFrameworkCore.Relational package of version 2.2.6 to your project.
  • Add the \Entity\EFCore2\netstandard2.0\Devart.Data.***.Entity.EFCore.dll assembly from the provider installation folder to your project.


Here is the list of changes:
  • Entity Framework Core 5.0 is supported (Oracle, MySQL, PostgreSQL, SQLite)
  • Entity Framework Core 3.1.10 is supported
  • The behavior is changed: EF Core 3 assemblies available via NuGet package are compiled for .NET Standard 2.0 instead of .NET Standard 2.1 (Oracle, MySQL, PostgreSQL, SQLite)
  • The behavior is changed: EF Core 2 assemblies are no longer available via NuGet package but created in the provider installation folder (Oracle, MySQL, PostgreSQL, SQLite)
  • The bug with generating invalid SQL, when the sdo_geometry column is part of a subquery, in EF Core 3 is fixed (Oracle)
  • The bug with using another context's connection in DbContextOptionsBuilder<NewDbContext>.UseOracle(connection) in EF Core is fixed (Oracle)
  • The bug with using another context's connection in DbContextOptionsBuilder<NewDbContext>.UseMySql(connection) in EF Core is fixed (MySQL)
  • The bug with using another context's connection in DbContextOptionsBuilder<NewDbContext>.UsePostgreSql(connection) in EF Core is fixed (PostgreSQL)
  • The bug with using another context's connection in DbContextOptionsBuilder<NewDbContext>.UseSQLite(connection) in EF Core is fixed (SQLite)
  • The bug with using another context's connection in DbContextOptionsBuilder<NewDbContext>.UseDB2(connection) in EF Core is fixed (DB2)
Devart development team
http://www.devart.com/dotconnect/entityframework.html

Locked