We are glad to announce the new features that are available in the Entity Framework support in the latest version:
- Entity Framework Core 1.0.1 is supported
- The new optional parameter Action<MySqlDbContextOptionsBuilder> is added to UseMySql() extension method of DbContextOptionsBuilder in EF Core (MySQL)
- The new optional parameter Action<OracleDbContextOptionsBuilder> is added to UseOracle() extension method of DbContextOptionsBuilder in EF Core (Oracle)
- The new optional parameter Action<PgSqlDbContextOptionsBuilder> is added to UsePostgreSql() extension method of DbContextOptionsBuilder in EF Core (PostgreSQL)
- The new optional parameter Action<SQLiteDbContextOptionsBuilder> is added to UseSQLite() extension method of DbContextOptionsBuilder in EF Core (SQLite)
- The new optional parameter Action<DB2DbContextOptionsBuilder> is added to UseDB2() extension method of DbContextOptionsBuilder in EF Core (DB2)
- The new optional parameter Action<SalesforceDbContextOptionsBuilder> is added to UseSalesforce() extension method of DbContextOptionsBuilder in EF Core (Salesforce)
- The config.DatabaseScript.Schema.Extensions configuration option is added to specify the extensions to create with DeleteDatabaseBehaviour.Database via the Code-First approach (PostgreSQL)
- The config.SpatialOptions.ReadAs2D configuration option (default value is False) is implemented for EF5 / EF6 to treat 3D SDO_GEOMETRY objects as 2D (Oracle)
- The behaviour is changed: FK constraints within CREATE TABLE are named now in Code-First Migrations (Oracle)
- The bug with using Take(0) with the entity, which includes the DbGeometry or DbGeography fields, in EF5/EF6 is fixed (Oracle)
- The bug with paging in EF Core, when working with Oracle 11g and below, is fixed (Oracle)
- The bug with processing IN expressions in EF Core is fixed
- The bug with retrieving objects of TPH hierarchy in EF Core is fixed
http://www.devart.com/dotconnect/entityframework.html