Devart is glad to announce the release of dotConnect for Oracle 9.14, Devart ADO.NET data provider for Oracle with support for Entity Framework, Entity Framework Core, LinqConnect (LINQ to Oracle), and NHibernate. The new release offers support for Entity Framework Core 5. It also makes some breaking changes to Devart.Data.Oracle.EFCore NuGet package, which affect projects, using Entity Framework Core 2.
This package previously contained the corresponding Devart.Data.Oracle.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)
- EF Core 1 assembly (.NET Standard 1.3)
- EF Core 3 assembly (.NET Standard 2.0)
- EF Core 5 assembly (.NET Standard 2.1)
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.Oracle.EFCore package from your project
- Add the Devart.Data.Oracle package instead.
- Add the Microsoft.EntityFrameworkCore.Relational package of version 2.2.6 to your project.
- Add the \Entity\EFCore2\netstandard2.0\Devart.Data.Oracle.Entity.EFCore.dll assembly from the provider installation folder to your project.
Here is the complete list of dotConnect for Oracle 9.14.1150 features:
- Visual Studio 2019 version 16.9 Preview is supported
- The bug with throwing the ORA-01483 error when updating the VARCHAR2 column on Oracle 12.2 with NLS_CHARACTERSET=UTF8 in the Direct mode is fixed
- The bug with updating projects that reference EF6 provider assembly via Upgrade Wizard is fixed
- The new features are supported in Entity Framework 5.0:
- TPT inheritance
- Many-to-many associations
- The new types of properties IPAddress and PhysicalAddress
- The Model Refactoring functionality is supported for classes in EF Core Model
- The behavior is changed in a standalone Entity Developer: by default the Target Framework model property in EF Core Model is set to .NET 5 instead of .NET Framework
- The bug with saving non-default value of Target Framework model property in EF6 model modified with a standalone Entity Developer is fixed
- The bug with adding new arguments at the end of argument list instead of actual position in method signature by Update From Database Wizard is fixed
- The bug with placing procedure with no parameters in the Procedures node instead of being enlisted in its package's node of Update From Database Wizard tree in the case of Oracle 18c and higher is fixed
- Entity Framework Core 5.0 is supported
- 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
- The behavior is changed: EF Core 2 assemblies are no longer available via NuGet package but created in the provider installation folder
- The bug with generating invalid SQL, when the sdo_geometry column is part of a subquery, in EF Core 3 is fixed
- The bug with using another context's connection in DbContextOptionsBuilder.UseOracle(connection) in EF Core is fixed
http://www.devart.com/dotconnect/oracle/