Related Documentation Download these Release Notes
PDF (US Ltr) - 0.7Mb
PDF (A4) - 0.7Mb


MySQL Connector/NET Release Notes  /  Changes in MySQL Connector/Net 6.10  /  Changes in MySQL Connector/NET 6.10.3 (2017-08-18, Release Candidate)

Changes in MySQL Connector/NET 6.10.3 (2017-08-18, Release Candidate)

Known limitation of this release:

The use of the SSL protocol is restricted to TCP and Unix socket connections. Connections using named pipes and shared memory do not support SSL mode.

Functionality Added or Changed

  • The following methods are available for use with EF Core in asynchronous command and connection operations:

    • Microsoft.EntityFrameworkCore.DbContext.AddAsync

    • Microsoft.EntityFrameworkCore.DbContext.AddRangeAsync

    • Microsoft.EntityFrameworkCore.DbContext.FindAsync

    • Microsoft.EntityFrameworkCore.DbContext.SaveChangesAsync

    • Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.EnsureDeletedAsync

    • Microsoft.EntityFrameworkCore.Infrastructure.DatabaseFacade.EnsureCreatedAsync

    • Microsoft.EntityFrameworkCore.DbContext.ToListAsync

  • Support for connections using Unix domain socket files was extended to include MySQL servers deployed on the Linux hosts in .NET Core scenarios. To specify a Unix domain socket connection, set the value of the Server connection-string option to the path of the socket file and the Protocol option to unix. For example:

    "server=/path/to/socket;protocol=unix;user=root;password=mypass"
  • The AutoEnlist and IncludeSecurityAsserts connection-string options are not appropriate for use by applications that target .NET Core and now return an error when used.

  • EF Core: Support for explicit loading was added. Explicit loading is an object-relational mapper (O/RM) pattern introduced in EF Core 1.1.0, which enables .NET developers to explicitly load related data from the database at a later time.

  • EF Core: Support for scaffolding a DbContext from multiple databases was added. With multiple databases (or schemas of tables) specified, the resulting entity classes are created within a single context.

    EF Core CLI usage example:

    dotnet ef dbcontext scaffold "connection-string" MySql.Data.EntityFrameworkCore --schema world --schema sakila

    Package Manager Console (Visual Studio) usage example:

    Scaffold-DbContext "connection-string" MySql.Data.EntityFrameworkCore -Schemas world,sakila
  • The following connection-string options are not currently supported for use by applications that target .NET Core and now return an error when used:

    • SharedMemoryName

    • IntegratedSecurity

    • PipeName

    • Logging

    • UseUsageAdvisor

    • UsePerformanceMonitor

    • InteractiveSession

    • Replication

Bugs Fixed

  • EF Core: Some methods in the DbContext class were not supported for use with asynchronous operations. (Bug #26448321, Bug #84814)

  • EF Core: When attempting to commit a transaction in which the FirstOrDefaultAsync method was called, the connector returned System.InvalidOperationException: Connection must be valid and open to commit transaction instead of committing the transaction. (Bug #26026972, Bug #86199)