Devart dotConnect for MySQL v8.16.1541
Devart dotConnect for MySQL v8.16.1541 Professional
dotConnect for MySQL is a high-performance ORM enabled data provider for MySQL that builds on ADO.NET technology to present a complete solution for developing MySQL-based database applications. It introduces new approaches for designing application architecture, boosts productivity, and facilitates the development of database applications.
Our ADO.NET MySQL provider supports a wide range of MySQL-specific features, such as secure SSL and SSH connections, embedded server, compression protocol, HTTP tunneling and others.
Advanced Visual Studio Integration
dotConnect for MySQL provides a vast number of GUI tools that increase your productivity. For example, it includes DataSet tools, such as DataSet Wizard, DataSet Editor, DataSet Manager, provide you an easy way to create and edit typed and untyped DataSets.
MySQL ADO.NET Provider supports advanced Visual Studio integration (DDEX), and provides convenient visual component editors to simplify component tweaking.
Broad Compatibility
dotConnect for MySQL was the first MySQL database provider to support .NET Core and Entity Framework Core, and we work hard to support new platforms and development technologies as soon as they are released.
MySQL support: from 3.23 to 8.0, Percona, and MariaDB
Visual Studio support: 2008 – 2019
Platforms support:
Full .NET Framework 2.0 – 4.8
.NET Core 1.x, 2.x, and 3.0
.NET Compact Framework 2.0 and above
Mono 2.0 and above
Enhanced ORM Support
dotConnect for MySQL offers enhanced ORM support with a bundled visual designer for ORM models - Entity Developer. Our MySQL ADO.NET Provider supports the following ORMs:
Entity Framework v1 - v6
Entity Framework Core 1.x, 2.x, and 3.1
NHibernate
LinqConnect
8.16.1541 23-Dec-19
Visual Studio 2019 version 16.5 Preview is supported
The bug with using Toolbox component MySqlDataSource in web projects of Visual Studio 2013, 2015, 2017, 2019 is fixed
The bug with enabling Devart DataSet Editor in Visual Studio 2017 and Visual Studio 2019 is fixed
LinqConnect (formerly known as LINQ to MySQL)
The bug with using Toolbox component DbLinqDataSource in web projects of Visual Studio 2013, 2015, 2017, 2019 is fixed
Entity Developer
The bug with creating one-to-one association basing on an optional FK in EF Core Model is fixed
The bug with code generation for oneOrZero-to-one and one-to-many associations based on an optional FK in EF Core Model is fixed
The bug with generating a mapping for a unique constraint specified in owned type property of EF Core Model is fixed
Entity Framework support
Entity Framework 6.4 is supported
Entity Framework Core 3.1 is supported
The new \Entity\EFCore3\Devart.Data.MySql.Entity.EFCore.dll assembly compiled with EF Core 3.1 and .NET Framework 4.6.1 is added
The new config.CodeFirstOptions.TruncateAllLongNames option (default value is False) is added to use EF Core 2/EF Core 3 implementation for truncating long names of columns and PK/FK/IX/UX
The config.DatabaseScript.ForeignKey.IndexCreation configuration option is supported in EF Core 1/EF Core 2/EF Core 3
The RenameColumn operation translated to ALTER TABLE RENAME COLUMN is supported for MySQL 8.0 and higher via Code-First Migrations in EF4/EF5/EF6/EF Core 1/EF Core 2/EF Core 3
The behavior is changed: System.Decimal is mapped now to MySQL data type DECIMAL(58,29) instead of DECIMAL by Code-First Migrations in EF Core 1/EF Core 2/EF Core 3
The bug with creating a unique constraint in the database via EF Core Code-First Migrations is fixed
The bug with applying .ValueGeneratedOnAdd() to the string, guid, byte[] properties with .Key() and without .HasDefaultValueSql() in EF Core is fixed
The error message with notification about missing annotation for the RenameColumn operation translated to ALTER TABLE CHANGE COLUMN in case of MySQL versions lower than 8.0 is fixed
The bug with detecting implicit database column type, when model mapping and migration mapping are different, via EF Core Code-First Migrations is fixed
The bug with generating SQL when using explicit cast in LINQ queries in EF Core 1/EF Core 2 is fixed
The bug with throwing the "Null TypeMapping in Sql Tree" error by methods in LINQ query in EF Core 3 is fixed
Visual Studio 2019 version 16.5 Preview is supported
The bug with using Toolbox component MySqlDataSource in web projects of Visual Studio 2013, 2015, 2017, 2019 is fixed
The bug with enabling Devart DataSet Editor in Visual Studio 2017 and Visual Studio 2019 is fixed
LinqConnect (formerly known as LINQ to MySQL)
The bug with using Toolbox component DbLinqDataSource in web projects of Visual Studio 2013, 2015, 2017, 2019 is fixed
Entity Developer
The bug with creating one-to-one association basing on an optional FK in EF Core Model is fixed
The bug with code generation for oneOrZero-to-one and one-to-many associations based on an optional FK in EF Core Model is fixed
The bug with generating a mapping for a unique constraint specified in owned type property of EF Core Model is fixed
Entity Framework support
Entity Framework 6.4 is supported
Entity Framework Core 3.1 is supported
The new \Entity\EFCore3\Devart.Data.MySql.Entity.EFCore.dll assembly compiled with EF Core 3.1 and .NET Framework 4.6.1 is added
The new config.CodeFirstOptions.TruncateAllLongNames option (default value is False) is added to use EF Core 2/EF Core 3 implementation for truncating long names of columns and PK/FK/IX/UX
The config.DatabaseScript.ForeignKey.IndexCreation configuration option is supported in EF Core 1/EF Core 2/EF Core 3
The RenameColumn operation translated to ALTER TABLE RENAME COLUMN is supported for MySQL 8.0 and higher via Code-First Migrations in EF4/EF5/EF6/EF Core 1/EF Core 2/EF Core 3
The behavior is changed: System.Decimal is mapped now to MySQL data type DECIMAL(58,29) instead of DECIMAL by Code-First Migrations in EF Core 1/EF Core 2/EF Core 3
The bug with creating a unique constraint in the database via EF Core Code-First Migrations is fixed
The bug with applying .ValueGeneratedOnAdd() to the string, guid, byte[] properties with .Key() and without .HasDefaultValueSql() in EF Core is fixed
The error message with notification about missing annotation for the RenameColumn operation translated to ALTER TABLE CHANGE COLUMN in case of MySQL versions lower than 8.0 is fixed
The bug with detecting implicit database column type, when model mapping and migration mapping are different, via EF Core Code-First Migrations is fixed
The bug with generating SQL when using explicit cast in LINQ queries in EF Core 1/EF Core 2 is fixed
The bug with throwing the "Null TypeMapping in Sql Tree" error by methods in LINQ query in EF Core 3 is fixed
Only for V.I.P Warning! You are not allowed to view this text.