Documentation Home
MySQL Connector/NET Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 0.8Mb
PDF (A4) - 0.8Mb

MySQL Connector/NET Release Notes  /  Changes in MySQL Connector/NET Version 8.x  /  Changes in MySQL Connector/NET 8.0.23 (2021-01-18, General Availability)

Changes in MySQL Connector/NET 8.0.23 (2021-01-18, General Availability)

Deprecation and Removal Notes

  • The IgnorePrepare connection-string option was deprecated in the Connector/NET 8.0.23 release and removed in the Connector/NET 8.0.24 release.

    The removed option instructed Connector/NET to ignore all calls to MySqlCommand.Prepare() that were made using the classic MySQL protocol. (Bug #31872906)

  • The following synonyms for the Server connection string option were deprecated in Connector/NET 8.0.22 and removed in 8.0.23: address, addr, and network address. (Bug #31248601)

Functionality Added or Changed

  • Connector/NET updates to SSH ciphers and algorithms are:

    • Encryptions: aes192-cbc, aes256-cbc (deprecated); 3des-cbc, blowfish-cbc, twofish-cbc, twofish128-cbc, twofish192-cbc, twofish256-cbc (invalid)

    • Host Key Algorithms: ssh-rsa (deprecated); sh-dss (invalid)

    • Key Exchange Algorithms: diffie-hellman-group-exchange-sha1 (invalid)

    • Keyed Hash Message Authentication Codes: hmac-ripemd160,, hmac-sha1-96 (invalid)

    (Bug #31917057)

  • ASP.NET applications using the MySQL provider model (MySql.Web) can now target .NET Framework 4.8. (Bug #31799902)

  • Previously, Connector/NET added client support for the MySQL Enterprise Edition SASL LDAP authentication plugin with SCRAM-SHA-1 as an authentication method. Connector/NET now also supports SCRAM-SHA-256 as an alternative authentication method for classic MySQL protocol connections. SCRAM-SHA-256 is similar to SCRAM-SHA-1 but is more secure. SASL-based LDAP authentication does not apply to .NET applications running macOS. (WL #14255)

  • With the availability of Entity Framework Core 5.0 in addition to Entity Framework Core 3.1, Connector/NET now provides two distinct EF Core NuGet packages. The split enables the connector to support both feature sets as they diverge. Initially, Connector/NET supports a partial EF Core 5.0 feature set (equivalent to EF Core 3.1) in this release. For more information, see Entity Framework Core Support.

    Breaking change: all namespaces are renamed to

    New EF Core package naming for Connector/NET 8.0.23:

    • 5.0.0+m8.0.23

    • 3.1.10+m8.0.23

    (WL #14214)

Bugs Fixed

  • If a prepared statement had no parameters, Connector/NET included in the COM_STMT_EXECUTE packet structure a byte corresponding to new-params-bound-flag instead of sending the byte only when the number of parameters was greater than zero. (Bug #32208427)

  • Incomplete validation limited the expected range of values that a stored procedure with a parameter of type Boolean could assign using the MySqlParameter.MySqlDbType property. (Bug #32066024, Bug #101302)

  • Stronger validation was applied to information contained in the certificate store for connections made using SslMode. (Bug #31954655)

  • A connection timeout was added to prevent the MySqlConnection.Open method from waiting indefinitely for a response after MySQL Router restarted unexpectedly. (Bug #31945397, Bug #100692)

  • A cast made with the wrong data type during a valid EF Core operation returned an exception. (Bug #31860492, Bug #100773)

  • Connector/NET used the value of -1 internally to ensure that a parameter without an index was added to the end of the parameter list. However, if an index with an actual value of -1 was passed in, the collection was interpreted as having no index and the argument did not generate an out-of-range exception. (Bug #31754599, Bug #100522)

  • Without validation, an underlying 64-bit enumeration value passed in as a MySQL command parameter defaulted to type Int32 and produced an overflow exception. (Bug #25467610, Bug #84701)