Connector/NET 6.10 or 8.0.11

MySQL Server 5.6

Entity Framework 6 assemblies

.NET Framework 4.6.2

Connector/NET 8.0.22

MySQL Server 5.6

Entity Framework 6.4 assemblies

.NET Standard 2.1 (.NET Core SDK 3.1 and Visual Studio 2019 version 16.5)

Cross-platform support in Connector/NET 8.0.22 implements EF 6.4 as the initial provider version to include Linux and macOS compatibility with .NET Standard 2.1 from Microsoft.

Async Query and Save adds support for the task-based asynchronous patterns that have been available since .NET 4.5. The new asynchronous methods supported by Connector/NET are:

Connection Resiliency / Retry Logic enables automatic recovery from transient connection failures. To use this feature, add to the OnCreateModel method:

SetExecutionStrategy(MySqlProviderInvariantName.ProviderName, () => new MySqlExecutionStrategy());

Code-Based Configuration gives you the option of performing configuration in code, instead of performing it in a configuration file, as it has been done traditionally.

Dependency Resolution introduces support for the Service Locator. Some pieces of functionality that can be replaced with custom implementations have been factored out. To add a dependency resolver, use:

AddDependencyResolver(new MySqlDependencyResolver());

The following resolvers can be added:

Interception/SQL logging provides low-level building blocks for interception of Entity Framework operations with simple SQL logging built on top:

myContext.Database.Log = delegate(string message) { Console.Write(message); };

DbContext can now be created with a DbConnection that is already opened, which enables scenarios where it would be helpful if the connection could be open when creating the context (such as sharing a connection between components when you cannot guarantee the state of the connection)

  [DbConfigurationType(typeof(MySqlEFConfiguration))]
  class JourneyContext : DbContext
  {
    public DbSet<MyPlace> MyPlaces { get; set; }

    public JourneyContext()
      : base()
    {

    }

    public JourneyContext(DbConnection existingConnection, bool contextOwnsConnection)
      : base(existingConnection, contextOwnsConnection)
    {

    }
  }

  using (MySqlConnection conn = new MySqlConnection("<connectionString>"))
  {
    conn.Open();
    ...

    using (var context = new JourneyContext(conn, false))
    {
      ...
    }
  }

Improved Transaction Support provides support for a transaction external to the framework as well as improved ways of creating a transaction within the Entity Framework. Starting with Entity Framework 6, Database.ExecuteSqlCommand() will wrap by default the command in a transaction if one was not already present. There are overloads of this method that allow users to override this behavior if wished. Execution of stored procedures included in the model through APIs such as ObjectContext.ExecuteFunction() does the same. It is also possible to pass an existing transaction to the context.

DbSet.AddRange/RemoveRange provides an optimized way to add or remove multiple entities from a set.

Code First Mapping to Insert/Update/Delete Stored Procedures supported:

modelBuilder.Entity<EntityType>().MapToStoredProcedures();

Idempotent migrations scripts allow you to generate an SQL script that can upgrade a database at any version up to the latest version. To do so, run the Update-Database -Script -SourceMigration: $InitialDatabase command in Package Manager Console.

Configurable Migrations History Table allows you to customize the definition of the migrations history table.