MySQL Connector/NET 6.10.3 rc has been released
August 18, 2017 11:57AM
Sorry, you can't reply to this topic. It has been closed.
Dear MySQL users, MySQL Connector/Net 6.10.3 rc is the fourth release which supports Scaffold-DbContext, that enables the creation of corresponding model classes from an existing database that are compatible with Entity Framework (EF) Core 1.1. To download MySQL Connector/Net 6.10.3 rc, see the "Development Releases" tab at http://dev.mysql.com/downloads/connector/net/ 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 connections. Connections using Unix sockets, 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 sockets was extended to include MySQL servers deployed on the Linux host operating system in .NET Core scenarios. To specify a Unix 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) Nuget packages are available at: https://www.nuget.org/packages/MySql.Data/6.10.3-rc https://www.nuget.org/packages/MySql.Web/6.10.3-rc https://www.nuget.org/packages/MySql.Data.Entity/6.10.3-rc https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/6.10.3-rc https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore.Design/6.10.3-rc Enjoy and thanks for the support! On behalf of the MySQL Release Team, Nawaz Nazeer Ahamed