MySQL Connector/NET 8.0.23 has been released
Posted by: Nawaz Nazeer Ahamed
Date: January 18, 2021 08:47AM
Date: January 18, 2021 08:47AM
Dear MySQL users, MySQL Connector/NET 8.0.23 is the latest General Availability release of the MySQL Connector/NET 8.0 series. This version supports .NET 5.0 and the X DevAPI, which enables application developers to write code that combines the strengths of the relational and document models using a modern, NoSQL-like syntax that does not assume previous experience writing traditional SQL. To learn more about how to write applications using the X DevAPI, see http://dev.mysql.com/doc/x-devapi-userguide/en/ For more information about how the X DevAPI is implemented in Connector/NET, see http://dev.mysql.com/doc/dev/connector-net NuGet packages provide functionality at a project level. To get the full set of features available in Connector/NET such as availability in the GAC, integration with Visual Studio's Entity Framework Designer and integration with MySQL for Visual Studio, installation through the MySQL Installer or the stand-alone MSI is required. Please note that the X DevAPI requires at least MySQL Server version 8.0 or higher with the X Plugin enabled. For general documentation about how to get started using MySQL as a document store, see http://dev.mysql.com/doc/refman/8.0/en/document-store.html To download MySQL Connector/NET 8.0.23, see http://dev.mysql.com/downloads/connector/net/ Installation instructions can be found at https://dev.mysql.com/doc/connector-net/en/connector-net-installation.html Enjoy! Changes in MySQL Connector/NET 8.0.23 (2021-01-18, General Availability) 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-ripemd160@openssh.com, hmac-sha1-96 (invalid) For a complete list, see SSH Ciphers in Connector/NET https://dev.mysql.com/doc/connector-net/en/connector-net-ssh-ciphers.html (Bug #31917057) * The IgnorePrepare connection-string option is deprecated in this release and the default value, which was true, is now false. When set to true, the option instructs Connector/NET to ignore any calls to MySqlCommand.Prepare() made with the classic MySQL protocol. The option is scheduled for removal in the next release. (Bug #31872906) * ASP.NET applications using the MySQL provider model (MySql.Web) can now target .NET Framework 4.8. (Bug #31799902) * 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) * 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 clients running macOS. * 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 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 https://dev.mysql.com/doc/connector-net/en/connector-net-entityframework-core.html Breaking change: all MySql.Data.EntityFrameworkCore.xxx namespaces are renamed to MySql.EntityFrameworkCore.xxx. New EF Core package naming for Connector/NET 8.0.23: + 5.0.0-m8.0.23 + 3.1.10-m8.0.23 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) Enjoy and thanks for the support! On behalf of the MySQL Release Team, Nawaz Nazeer Ahamed
Subject
Views
Written By
Posted
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.