LogMeIn Pro

What's new in this version:

dotConnect for MySQL Professional 8.13.1422
- The bug with throwing "Operation is not supported" by web providers, when the cookie is used, is fixed

Entity Developer:
- The ability to disable generation of the byte order mark (BOM) in the beginning of code files in a standalone Entity Developer is implemented
- The bug with design time copy/cut/paste functionality for entities is fixed
- The bug with invalid integer to enum conversion by a generated method, which is based on SQL query and returns a collection of entities, in EF Core 2 is fixed

Entity Framework support:
- The bug with applying a filter to the nullable property with implicit EnumToStringConverter via LINQ queries in EF Core 2 is fixed
- The bug with missing brackets around SELECT inside the generated CASE statement in EF Core 2 is fixed
- The bug with nullable parameters in EF Core 2 is fixed
- The bug with reopening connections in EF Core 2 is fixed


dotConnect for MySQL Professional 8.13.1402
- Deprecated design-time Synchronous API calls are no longer used with Visual Studio 2019 and Visual Studio 2017

LinqConnect (formerly known as LINQ to MySQL):
- The bug with executing incorrect SQL request (cached during one of the previous calls), when a variable initialized with an empty collection participates in LINQ query, is fixed

Entity Framework support:
- Entity Framework Core 2.2.4 is supported
- The bug with closing database connection by context.Dispose() in the scope of a distributed transaction in EF Core 2 is fixed
- The bug with using a value converter, when the .NET data type remains the same, within the WHERE clause in EF Core 2 is fixed
- The bug with setting default values for the DateTime and TimeSpan columns in the ALTER statements in EF Core 2 Code-First Migrations is fixed


dotConnect for MySQL Professional 8.13.1366
- Visual Studio 2019 is supported
- Entity Developer: the bug with processing DBNull returned by the function in EF Core is fixed
- Entity Framework support: the bug with using the "Generate Database from Model" wizard when working with Entity Framework 6 Tools is fixed


dotConnect for MySQL Professional 8.12.1357

- Visual Studio 2019 Release Candidate 4 is supported
- The bug with corrupting not Latin-1 characters by Migration Wizard for files with non-unicode encoding is fixed

Entity Developer:
- The bug with the Regenerate Storage / Generate Database Script / Update Database Script From Model functionality for the Geometry and Geography properties in EF5 / EF6 is fixed

Entity Framework support:
- Entity Framework Core 2.2.3 is supported
- The SQL translation of the following method overloads, that accept the StringComparison argument and return bool, in the System.String class is supported in EF Core 2: Contains, StartsWith, EndsWith, Equals
- The bug with inserting and updating string data, when config.QueryOptions.NullStringCollation is initialized, is fixed
- The bug with generating the COALESCE expression in EF Core is fixed
- The bug with calling DbExecutionStrategy.ShouldRetryOn(Exception), when the first connection fails to open, is fixed


dotConnect for MySQL Professional 8.12.1328

- Connection to MySQL 8.0 is supported in the Express edition
- The bug with MySqlLoader.LoadTable(IDataReader) for .NET Standard 1.3 and .NET Standard 2 is fixed

LinqConnect (formerly known as LINQ to MySQL):
- The bug with executing incorrect SQL request (cached during one of the previous calls), when .Contains() is invoked in the multithreaded application, is fixed

Entity Developer:
- The bug with quoting keywords and reserved words of MySQL 8.0 is fixed
- The bug with generating fluent mapping for the one-to-one association by the DbContext template in EF4/EF5/EF6 is fixed
- Entity Framework support"
- The translation of single-char literal into SQL statement in EF Core is supported
- The bug with using a value converter for the property used in .Contains() in EF Core 2 is fixed
- The bug with translating String.IndexOf() into SQL statement in EF Core is fixed
- The bug with updating a null value of the concurrency check column with some non-null value in EF Core is fixed


dotConnect for MySQL Professional 8.12.1307
- The behavior is changed: now "Unicode=true;" sets client character set to utf8mb4 for MySQL Server 5.5.3 and higher
- The bug with connecting to database with .NET Standard 1.3 compatible assemblies on .NET Framework 4.6.0 run-time is fixed

LinqConnect (formerly known as LINQ to MySQL):
- The new overload DataContext.Refresh(bool ignoreErrors, RefreshMode mode, object entity) is added for ignoring errors during refresh
- The existing overload DataContext.Refresh(RefreshMode mode, object entity) is improved: its check avoids the try to refresh the entity that is added to the context but not submitted to the database
- The type and text of the error generated by the DataContext.Refresh(RefreshMode mode, object entity) method, when the passed entity doesn't exist in database, is fixed
- The bug with generating the COALESCE expression is fixed

Entity Developer:
- The multiple select functionality in EF Core Model is improved: now it allows setting PrimaryKey, ValueGenerated, Concurrency for several properties simultaneously
- The bug with detecting order of columns in composite primary key with two or more columns by Update To Database and by Update From Database wizards in EF Core is fixed
- The bug with using ASP.NET Core Web Application (.NET Framework) and Azure Functions v1 (.NET Framework) projects in Visual Studio 2017 is fixed

Entity Framework support:
- Entity Framework Core 2.2.1 is supported
- The new extension method Database.IsMySql() in EF Core 2 is implemented
- The config.QueryOptions.NullStringCollation option is implemented to use the COLLATE operator with a required collation when comparing null strings in "equal" and "not equal" cases
- The bug with applying config.Workarounds.IgnoreSchemaName=true to the .ToTable() functionality in EF Core 2 is fixed
- The bugs with using the GuidToStringConverter, EnumToStringConverter, ValueConverter classes in EF Core 2 are fixed
- The bug with constructing the LIKE clause in EF Core 2 is fixed
- The bug with generating a subselect within the SELECT list in EF Core 2 is fixed
- The bug with applying an aggregate function to the result of a subselect in EF Core 2 is fixed