Devart dotConnect for MySQL v9.2.0 Professional
Devart dotConnect for MySQL v9.2.0 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 with MySQL
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.
ADO.NET Provider with .NET Core and Entity Framework Support
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:
.NET 5.0, 6.0 compatibility
macOS 11 Arm64 (or "Apple Silicon" or "Apple M1") support
Windows 11 is supported
Visual Studio 2022 version 17.2 is supported.
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, 3.x, 5.0, and 6.0
NHibernate
LinqConnect
Dapper
9.2.0 16-Nov-23
MariaDB 11 is supported
Visual Studio 2022 version 17.8 Preview is supported
The error during installation on the 32-bit version of Windows has been fixed
The bug with inserting milliseconds via prepared command is fixed
Entity Framework support
Entity Framework Core 7.0.5 is supported
Entity Framework Core 6.0.16 is supported
The bug with throwing "Unexpected null value in SQL fragments", when LINQ query has multiple .Include() with spatial DbGeometry and DbGeography properties, in EF4/EF5/EF6 is fixed
The bug with throwing Microsoft.EntityFrameworkCore.Infrastructure.ManyServiceProvidersCreatedWarning by the UseMySql(DbConnection connection) extension method of DbContextOptionsBuilder in EF Core 6 and EF Core 7 is fixed
The bug with using custom converters in mapping in EF Core 3 and higher is fixed
Entity Developer
The bug with detecting TINYINT(1) NOT NULL DEFAULT 1 as function-based column default value in EF Core Model is fixed
The bug with detecting TINYINT(1) NOT NULL DEFAULT 1 as function-based column default value in EF Core Model is fixed
The bug with detecting the numeric default value of string columns as function-based column default value in EF Core Model is fixed
MariaDB 11 is supported
Visual Studio 2022 version 17.8 Preview is supported
The error during installation on the 32-bit version of Windows has been fixed
The bug with inserting milliseconds via prepared command is fixed
Entity Framework support
Entity Framework Core 7.0.5 is supported
Entity Framework Core 6.0.16 is supported
The bug with throwing "Unexpected null value in SQL fragments", when LINQ query has multiple .Include() with spatial DbGeometry and DbGeography properties, in EF4/EF5/EF6 is fixed
The bug with throwing Microsoft.EntityFrameworkCore.Infrastructure.ManyServiceProvidersCreatedWarning by the UseMySql(DbConnection connection) extension method of DbContextOptionsBuilder in EF Core 6 and EF Core 7 is fixed
The bug with using custom converters in mapping in EF Core 3 and higher is fixed
Entity Developer
The bug with detecting TINYINT(1) NOT NULL DEFAULT 1 as function-based column default value in EF Core Model is fixed
The bug with detecting TINYINT(1) NOT NULL DEFAULT 1 as function-based column default value in EF Core Model is fixed
The bug with detecting the numeric default value of string columns as function-based column default value in EF Core Model is fixed
Only for V.I.P
Warning! You are not allowed to view this text.