2. business software
  3. news
  4. reviews
  5. top apps
Télécharger dotConnect for MySQL 8.12.1229.0

dotConnect for MySQL 8.12.1229.0

Par Devart  (Essai commercial)
Note des utilisateurs

dotConnect for MySQL, formerly known as MyDirect .NET, is an enhanced 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 leverages database applications.

The tool supports Entity Framework, NHibernate, and LinqConnect (formerly known as LINQ to MySQL).


Titre: dotConnect for MySQL 8.12.1229.0
Nom de fichier: dcmysql.exe
Taille de fichier: 71.94MB (75,433,312 Octets)
Exigences: Windows (Toutes les versions)
Langues: Langues Multiples
Licence: Essai commercial
Date ajoutée: octobre 2, 2018
Auteur: Devart
Vérification MD5: E6E83F55DA67948EF78A26B0987C013F

The bug with absent Devart.Data.MySql.NHibernate.NHibernateMySqlConnection and Devart.Data.MySql.NHibernate.NHibernateMySqlCommand classes in the .Net Core NuGet package is fixed.

Entity Developer
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.