Devart - 71.9 MB ( Commercial Trial)
dotConnect for MySQL enhanced ORM data provider to easily create MySQL-based database applications.
dotConnect for MySQL is a reliable and enhanced ORM (Entity Framework, NHibernate, LinqConnect) enabled data provider build over ADO.NET architecture, being in the same time a development framework with impressive innovative technologies. It was developed to offer a complete solution for designing MySQL-based database applications while increasing the productivity in the same time. The application offers flexible conectivity – being able to operate in Direct Mode without MySQL client library and in Client mode with usage of libmysql.dll, database application development extensions, MySQL advanced features such as SSL and SSH connections, embedded server, HTTP tunneling and more, BIS support, ASP.NET Identity 1 and 2 support, Sync Framework support, a vast number of GUI tools that increase your productivity, per-component tracing of database events with a free dbMonitor application and much more.
The bug with absent Devart.Data.MySql.NHibernate.NHibernateMySqlConnection and Devart.Data.MySql.NHibernate.NHibernateMySqlCommand classes in the .Net Core NuGet package is fixed.
Using an extended property of type OutputInfo is supported.
Code generated for nullable properties is simplified: now T? is generated instead of System.Nullable<T>
An additional constructor that accepts DbContextOptions as an argument is added to the DbContext class descendant in the VB.NET version of the DbContext template for EF Core.
The bug with "No database provider has been configured for this DbContext." in the DbContext template for EF Core is fixed.
The bug with code generation for nullable properties for EF1/EF4/EF5/EF6 is fixed.
Entity Framework support
Entity Framework Core 2.1.3 is supported.
The bug with throwing an error by context.Database.Migrate(), when the __EFMigrationsHistory table already exists but tables being mapped by model classes are not created yet, in EF Core 2 is fixed.
The bug with a memory leak in EF Core 2, when a connection is set for DbContext as an MySqlConnection instance, and not via a connection string, is fixed.