dotConnect for Oracle 9.4 is released!

dotConnect for Oracle 9.4 is released!

Postby Devart » Thu 25 May 2017 16:58

Dear users,

Devart is glad to announce the release of dotConnect for Oracle 9.4, Devart ADO.NET data provider for Oracle with support for Entity Framework, LinqConnect (LINQ to Oracle) and NHibernate. The new version offers you support for .NET Core and Entity Framework Core 1.1.2.

Since .NET Core is limited in comparison to Full .NET Framework, not all provider features, available for Full .NET Framework are also available for .NET Core. Namely, there are no DataSet and DataTable features, support for Sync Framework, Workflow Foundation, and Enterprise Library. You can see the full list of features, not supported on .NET Core, in the dotConnect for Oracle documentation.

.NET Standard compatible assemblies use different licensing mechanism than assemblies for Full .NET Framework. They use either license key files placed to a specific folder (C:\ProgramData\Devart\dotConnect\License\) or license keys provided as a connection string parameter. Note that trial license key files are generated by the trial installers of our products. If you want to try the .NET Standard compatible assemblies of our products, distributed via NuGet packages, you will still need to install the product in order to obtain the trial license key file. You can find more information about technical licensing in the dotConnect for Oracle documentation.

Here is the complete list of dotConnect for Oracle 9.4.280 features:

  • .NET Core is supported
  • The NuGet packages with .NET Standard 1.3 (.NET Core) compliant assemblies are uploaded to www.nuget.org
  • The Default Fetch Size connection string parameter, which specifies the number of rows that will be transferred across the network at a time, is added
  • The possibility to assign a value of the DateTimeOffset type to OracleParameter.Value is added
  • The bug with the "ORA-01017" error when connecting to an Oracle user account with PASSWORD_VERSIONS equal to 10g only in the Direct mode is fixed
  • The bug with setting an InputOutput parameter to DBNull.Value instead of preserving its previous value if its value is not changed in the command in the Direct mode is fixed
  • The bug with incorrect behaviour of method OracleIntervalYM.Parse() when leading characters of the year part were ignored for some values is fixed
  • The bug in OracleCommandBuilder.RefreshingFields with handling of quoted column names has been fixed
  • The bug with previewing a DataSet is fixed
  • The bug with AccessViolationException when FetchSize is specified explicitly for a command and records of the result set have large size, and thus, too large prefetch buffer is required, is fixed
  • The bug with OracleDataReader, returning null values for Object, Array, Table, Xml, AnyData columns instead of returning an empty value of the corresponding type in the Direct mode is fixed
Entity Developer
  • The .NET Core projects in Visual Studio 2017 are supported
  • The Snake case in both Model and Database naming rules is supported via the new "Add underscore" option
  • The bug with setting parameter prefix in command text generated for calling pipelined function via EF Core is fixed
LinqConnect support
  • The bug with running LINQ queries, which invoke .NET methods on client side during materialization of result set, is fixed
  • The bug with materializing scalar value collection when converting values on the client side is fixed
Entity Framework support
  • Entity Framework Core 1.1.2 is supported
  • The CreateSequence and DropSequence operations in EF Core Code-First Migrations are supported
  • The support of EF Core models with string columns, which are defined without length limit and participate in PKs, FKs, indices, is improved
  • The possibility to use command interception for EF6 commands executed within batch updates is implemented
  • The compatibility with ASP.NET Core Identity is improved
  • The bug with using config.CodeFirstOptions.TruncateLongDefaultNames in EF Core is fixed
  • The bug with using the ForOracleHasColumnName and ForOracleHasColumnType modelBuilder methods with the value-type properties in EF Core is fixed
  • The bug with paging in EF Core is fixed
  • The bug with paging in subselect within EXISTS generated for Oracle 12c using EF1/EF4/EF5/EF6 is fixed

Devart development team
http://www.devart.com/dotconnect/oracle/
Devart
Devart Team
 
Posts: 3070
Joined: Tue 26 Oct 2004 13:51

Return to dotConnect for Oracle