MySQL Connector/NET 8.0.19 has been released

Dear MySQL users,

MySQL Connector/NET 8.0.19 is the latest General Availability release of
the MySQL Connector/NET 8.0 series. This version supports .NET Core 3.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/index.html. 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.19, 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

Changes in MySQL Connector/NET 8.0.19 (2020-01-13, General
Availability)


     * Functionality Added or Changed

     * Bugs Fixed

Functionality Added or Changed


     * Connector/NET supports TLS protocol versions TLSv1,
       TLSv1.1, TLSv1.2, and TLSv1.3. A new connection-string
       option, tlsversion, permits the restriction of a
       connection to a single version or to a list with any
       combination of the four supported TLS versions (see
       Options for Both Classic MySQL Protocol and X Protocol
(https://dev.mysql.com/doc/connector-net/en/connector-net-8-0-connection-options.html#connector-net-8-0-connection-options-classic-xprotocol)).
       Known issue: both .NET Core 3.0 (crossplatform) and .NET
       Framework 4.8 (windows only) added support for TLSv1.3.
       Be sure to confirm that the platform operating system
       running your application also supports TLSv1.3 before
       using it exclusively for connections. (Bug #30225427)

     * Support for DNS Service (SRV) records now provides an
       alternative to specifying individual hosts in the
       connection string. Instead, a single DNS domain can map
       to multiple targets (servers) using SRV address records.
       Each SRV record includes the host name, port, priority,
       and weight. For .NET applications using X Protocol, a new
       URI scheme of mysqlx+srv:// enables connections to share
       the query load when a single DNS domain is mapped to
       multiple servers.
       Similarly, the new dns-srv connection-string option also
       enables DNS SRV lookups for connections using either the
       classic MySQL protocol or X Protocol. The DNS SRV feature
       is disable by default. For usage information, see Options
       for Both Classic MySQL Protocol and X Protocol
(https://dev.mysql.com/doc/connector-net/en/connector-net-8-0-connection-options.html#connector-net-8-0-connection-options-classic-xprotocol).

     * When creating a new connection using classic MySQL
       protocol, multiple hosts can be tried until a successful
       connection is established. A list of hosts can be given
       in a connection string, with or without priorities.

// Example with priority
server=(address=192.10.1.52:3305,priority=60),(address=localhost:3306,
priority=100);

// Example without priority and with multiple ports
host=10.10.10.10:3306,192.101.10.2:3305,localhost:3306;uid=test;passwo
rd=xxxx;

       If the priority is not included, or if multiple hosts
       have the same priority, Connector/NET selects a host at
       random. The same random selection behavior also applies
       to connections made using X Protocol, which previously
       selected hosts sequentially when no priority was
       specified.

Bugs Fixed


     * Clone connections did not process all connection settings
       as expected. (Bug #30502718)

     * Connector/NET files displayed an unlikely date after the
       NuGet package containing them was installed in a project.
       (Bug #30471336, Bug #97390)

     * The inclusion of the System.Resources.Extensions
       dependency was transient and now is removed from the
       MySql.Data NuGet package. (Bug #30421657, Bug #97218)

On behalf of Oracle/MySQL Release Engineering Team,
Tvarita Jain

Leave a Reply

Your email address will not be published. Required fields are marked *