Devart is glad to announce the release of dotConnect for MySQL 8.9, Devart ADO.NET data provider for MySQL with support for Entity Framework, LinqConnect (LINQ to MySQL) 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 MySQL 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 MySQL documentation.
Here is the complete list of dotConnect for MySQL 8.9.912 features:
- .NET Core is supported
- The NuGet packages with .NET Standard 1.3 (.NET Core) compliant assemblies are uploaded to www.nuget.org
- The bug with previewing a DataSet is fixed
- 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
- The bug with returning incorrect data by the 'BooleanProperty ?? false' LINQ query is fixed
- 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 json datatype and rowversion pseudotype in SSDL is fixed
- Entity Framework Core 1.1.2 is 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 compatibility with ASP.NET Core Identity is improved
- The possibility to use command interception for EF6 commands executed within batch updates is implemented
- The bug with using config.CodeFirstOptions.TruncateLongDefaultNames in EF Core is fixed
- The bug with using the ForMySqlHasColumnName and ForMySqlHasColumnType modelBuilder methods with the value-type properties in EF Core is fixed
- The bug with paging in EF Core is fixed