Remote Desktop Manager Enterprise 歷史舊版本 Page33

更新時間：2019-11-01
更新細節：

What's new in this version:

- Added Super Audio CD ISO (SACD ISO) decoder (stereo | stereo+multichannel | multichannel, DSD | DST)
- Added 5.0 support for DFF / DSF / WAVPACK DSD outputs, so no intermediate DXD conversion is needed when converting from 5.0 SACD/DSD files
- Upmix 5.0 PCM/DSD to 5.1 PCM in Auto mode, previously 5.0 was downmixed to 4.0 in Auto mode
- Fixed the bug where converting DSD to DSD with DSP options other than Calculate Replaygain enabled (intermediate conversion via DXD) did not work
- Fixed the bug where extracting Cue Sheet w/DSD to individual DSD files with Calculate ReplayGain did not work

更新時間：2019-11-01
更新細節：

更新時間：2019-11-01
更新細節：

更新時間：2019-11-01
更新細節：

What's new in this version:

- Visual Studio 2019 version 16.4 Preview is supported
- Long object names support in Oracle 12.2 and higher is added
- The bug with calling overloaded stored procedures and functions is fixed

Entity Developer:
- The DbContext template is improved: precision and scale for database types are generated now in EF4/EF5/EF6 models when Fluent Mapping=True and Mapping Generation Strategy=UseAttributes
- The bug with throwing the EntityFrameworkCoreVersion error in Create Model Wizard in a standalone Entity Developer is fixed
- The bug with incorrect detecting DatabaseGeneratedOption.Identity for the properties with DEFAULT NULL in a database, when "Detect function-based column default value" is selected in Create Model Wizard, is fixed in EF4/EF5/EF6

Entity Framework support:
- Entity Framework Core 2.2.6 is supported

更新時間：2019-11-01
更新細節：

What's new in this version:

dotConnect for PostgreSQL Professional 7.15.1504
- Visual Studio 2019 version 16.4 Preview is supported

Entity Developer:
- The DbContext template is improved: precision and scale for database types are generated now in EF4/EF5/EF6 models when Fluent Mapping=True and Mapping Generation Strategy=UseAttributes
- The bug with throwing the EntityFrameworkCoreVersion error in Create Model Wizard in a standalone Entity Developer is fixed

Entity Framework support:
- Entity Framework Core 2.2.6 is supported
- The bug with optimistic concurrency implementation in EF Core is fixed


dotConnect for PostgreSQL Professional 7.15.1499
- PostgreSQL 12 is supported
- The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported by Devart DataSet Manager
- The bug with inserting data into GEOMETRY columns is fixed
- The bug with updating TEXT columns in UTF8 databases is fixed

Entity Developer:
The DbContext template is improved for using Entity Framework 6.3:
- The "Configuration Type Name" property, which specifies the descendant of DbConfiguration class that should be used for code-based configuration, is added
- The "Use DbConfigurationType Attribute" property, which determines whether to register the configuration type specified in the ConfigurationTypeName property of the DbConfigurationType attribute, is added
- The DbProviderFactories.RegisterFactory method is generated when UseDbConfigurationTypeAttribute=true and ConfigurationTypeName='%Default%'
- With UseDbConfigurationTypeAttribute=false, the static constructor for registering factory and the new partial method OnStaticConfigured are generated
- The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported
- The compatibility issue with JetBrains ReSharper is fixed

Entity Framework support:
- Entity Framework Core 3.0 is supported
- Entity Framework 6.3 is supported
- The lock for Microsoft.EntityFrameworkCore dependency is added to the NuGet package Devart.Data.PostgreSql.EFCore
- The bug with invoking DbFunctions with the DateTime and DateTimeOffset parameters is fixed


dotConnect for PostgreSQL Professional 7.14.1470
- The integration with Visual Studio 2019 is improved: now the installation detects both 2019 Release and 2019 Preview versions
- The bug with throwing System.NullReferenceException instead of actual error in Workflow Foundation is fixed

Entity Developer:
- Entity Framework 6.3 Preview 9 is supported for projects with target framework .NET Core 3 or .NET Standard 2.1
- The behaviour is changed: a plural form of names ending with "s" now has a longer version (for example, status -> statuses)
- The bug with applying the new Foreign Key's Delete Rule values SET DEFAULT and SET NULL by the Update Database From Model and Update Model From Database wizards is fixed (Entity Framework)
- The bug with copying a property with Primary Key=True / Entity Key=True to a complex type is fixed (Entity Framework)
- The bug with naming of a composing unique key by Create Model Wizard / Update From Database Wizard in EF Core is fixed (Entity Framework)
- The bug with invalid attempt to cast unsupported Visual Studio project to type 'VSLangProj.VSProject' is fixed

Entity Framework support:
- Entity Framework 6.3 Preview 9 is supported
- A new NuGet package Devart.Data.PostgreSql.EF6 with a .NET Standard 2.1 assembly, compatible with .NET Core 3, is added
- The bug with using the same database connection in several EF Core contexts is fixed
- The bug with applying a value converter to .Where expression with .Contains on nullable enum in EF Core 2 is fixed
- The bug with casting the DateTimeOffset value passed to a function as an argument in EF6 is fixed


dotConnect for PostgreSQL Professional 7.13.1437
Entity Framework support:
- The bug with applying a value converter to a nullable column in EF Core 2 is fixed
- The bug with applying config.QueryOptions.ComparisonCollation to the update statements in EF6 is fixed


dotConnect for PostgreSQL Professional 7.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 PostgreSQL Professional 7.13.1402
- Deprecated design-time Synchronous API calls are no longer used with Visual Studio 2019 and Visual Studio 2017
- The behaviour is changed: now PgSqlDataAdapter performs inserts in a batch with protocol 3 when the UpdateBatchSize property is used and UnpreparedExecute is true for InsertCommand
- The bug with missing schema name in a function return type when the function is backed up via PgSqlDump.Backup is fixed
- The bug with creating foreign key constraints before primary key constraints in a PgSqlDump.Backup result script is fixed
- The bug with adding timestamp(6) instead of timestamp to a PgSqlDump.Backup result script is fixed
- The bug with connecting to a PostgreSQL server on Google Cloud Platform is fixed

LinqConnect (formerly known as LINQ to PostgreSQL):
- The bug with running stored procedure in PostgreSQL Server 11 or higher is fixed
- 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


dotConnect for PostgreSQL Professional 7.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 PostgreSQL Professional 7.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 Framework support
- Entity Framework Core 2.2.3 is supported
- The translation of DateTimeOffset literal into SQL statement 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 removing an empty __EFMigrationsHistory table by EnsureDeleted() in EF Core 2 for PostgreSQL 9.0 and higher 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 PostgreSQL Professional 7.12.1328

- The bug with PgSqlLoader.LoadTable(IDataReader) for .NET Standard 1.3 and .NET Standard 2 is fixed
- The bug with applying Convert.IsDBNull() to PgSqlParameter.Value is fixed

LinqConnect (formerly known as LINQ to PostgreSQL):
- 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 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 SQL generation, when optionsBuilder.UseLoggerFactory() is used, in EF Core is fixed
- 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 PostgreSQL Professional 7.12.1307
- PostgreSQL 11 is supported
- 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 PostgreSQL):
- 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

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.IsPostgreSql() in EF Core 2 is implemented
- 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

更新時間：2019-11-01
更新細節：

What's new in this version:

dotConnect for SQLite Professional 5.14.1504
Entity Developer:
- The DbContext template is improved: precision and scale for database types are generated now in EF4/EF5/EF6 models when Fluent Mapping=True and Mapping Generation Strategy=UseAttributes
- The bug with throwing the EntityFrameworkCoreVersion error in Create Model Wizard in a standalone Entity Developer is fixed

Entity Framework support:
- Entity Framework Core 2.2.6 is supported


dotConnect for SQLite Professional 5.14.1499
- The sqlite3.dll library that is included into the installation package is updated to version 3.30.1
- The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported by Devart DataSet Manager

Entity Developer:
The DbContext template is improved for using Entity Framework 6.3:
- The "Configuration Type Name" property, which specifies the descendant of DbConfiguration class that should be used for code-based configuration, is added
- The "Use DbConfigurationType Attribute" property, which determines whether to register the configuration type specified in the ConfigurationTypeName property of the DbConfigurationType attribute, is added
- The DbProviderFactories.RegisterFactory method is generated when UseDbConfigurationTypeAttribute=true and ConfigurationTypeName='%Default%'
- With UseDbConfigurationTypeAttribute=false, the static constructor for registering factory and the new partial method OnStaticConfigured are generated
- The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported
- The compatibility issue with JetBrains ReSharper is fixed

Entity Framework support:
- Entity Framework Core 3.0 is supported
- Entity Framework 6.3 is supported
- The lock for Microsoft.EntityFrameworkCore dependency is added to the NuGet package Devart.Data.SQLite.EFCore


dotConnect for SQLite Professional 5.13.1470
Entity Developer:
- Entity Framework 6.3 Preview 9 is supported for projects with target framework .NET Core 3 or .NET Standard 2.1
- The behaviour is changed: a plural form of names ending with "s" now has a longer version (for example, status -> statuses)
- The bug with applying the new Foreign Key's Delete Rule values SET DEFAULT and SET NULL by the Update Database From Model and Update Model From Database wizards is fixed (Entity Framework)
- The bug with copying a property with Primary Key=True / Entity Key=True to a complex type is fixed (Entity Framework)
- The bug with naming of a composing unique key by Create Model Wizard / Update From Database Wizard in EF Core is fixed (Entity Framework)
- The bug with invalid attempt to cast unsupported Visual Studio project to type 'VSLangProj.VSProject' is fixed

Entity Framework support:
- Entity Framework 6.3 Preview 9 is supported
- A new NuGet package Devart.Data.SQLite.EF6 with a .NET Standard 2.1 assembly, compatible with .NET Core 3, is added
- The bug with using the same database connection in several EF Core contexts is fixed
- The bug with applying a value converter to .Where expression with .Contains on nullable enum in EF Core 2 is fixed


dotConnect for SQLite Professional 5.12.1437
- The bug with throwing System.IndexOutOfRangeException when OracleParameter.Size=-1 is fixed

Entity Framework support:
- The bug with applying a value converter to a nullable column in EF Core 2 is fixed
- The bug with using the binary operator Add for the types 'System.String' and 'System.String' within LINQ query in EF Core 2 is fixed


dotConnect for SQLite Professional 5.12.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
- The bug with incorrect exception message on opening connection, when ConnectionString is not set, by .NET Standard compliant assemblies is fixed


dotConnect for SQLite Professional 5.12.1402
- The sqlite3.dll library that is included into the installation package is updated to version 3.28.0
- 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


dotConnect for SQLite Professional 5.12.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 SQLite Professional 5.11.1357

- Visual Studio 2019 Release Candidate 4 is supported
- The sqlite3.dll library that is included into the installation package is updated to version 3.27.2
- The behavior is changed: reader.GetValue("text_column_with_nonstandard_typename") returns now the System.String object
- The bug with loss of changes, applied in different concurrent transactions, when journaling is not in the WAL mode, is fixed

LinqConnect (formerly known as LINQ to SQLite):
- The bug with using the System.Char argument as literal or variable in LINQ query 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 generating the COALESCE expression in EF Core is fixed


dotConnect for SQLite Professional 5.11.1328

- The sqlite3.dll library that is included into the installation package is updated to version 3.27.1

LinqConnect (formerly known as LINQ to SQLite):
- 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 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 throwing Devart.Common.LicenseException when using config.Workarounds.ProviderManifestToken in EF Core is fixed
- 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 Professional SQLite 5.11.1307
- The sqlite3.dll library that is included into the installation package is updated to version 3.26.0
- 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 SQLite):
- 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

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.IsSQLite() in EF Core 2 is implemented
- 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

更新時間：2019-11-01
更新細節：

What's new in this version:

dotConnect for MySQL Professional 8.15.1504
Entity Developer:
- The DbContext template is improved: precision and scale for database types are generated now in EF4/EF5/EF6 models when Fluent Mapping=True and Mapping Generation Strategy=UseAttributes
- The bug with throwing the EntityFrameworkCoreVersion error in Create Model Wizard in a standalone Entity Developer is fixed

Entity Framework support:
- Entity Framework Core 2.2.6 is supported


dotConnect for MySQL Professional 8.15.1499
- The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported by Devart DataSet Manager

Entity Developer:
The DbContext template is improved for using Entity Framework 6.3:
- The "Configuration Type Name" property, which specifies the descendant of DbConfiguration class that should be used for code-based configuration, is added
- The "Use DbConfigurationType Attribute" property, which determines whether to register the configuration type specified in the ConfigurationTypeName property of the DbConfigurationType attribute, is added
- The DbProviderFactories.RegisterFactory method is generated when UseDbConfigurationTypeAttribute=true and ConfigurationTypeName='%Default%'
- With UseDbConfigurationTypeAttribute=false, the static constructor for registering factory and the new partial method OnStaticConfigured are generated
- The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported
- The compatibility issue with JetBrains ReSharper is fixed

Entity Framework support:
- Entity Framework Core 3.0 is supported
- Entity Framework 6.3 is supported
- The lock for Microsoft.EntityFrameworkCore dependency is added to the NuGet package Devart.Data.MySql.EFCore
- The bug with adding the datetime precision to the generated queries in EF6 is fixed


dotConnect for MySQL Professional 8.14.1470
Entity Developer:
- Entity Framework 6.3 Preview 9 is supported for projects with target framework .NET Core 3 or .NET Standard 2.1
- The behaviour is changed: a plural form of names ending with "s" now has a longer version (for example, status -> statuses)
- The bug with applying the new Foreign Key's Delete Rule values SET DEFAULT and SET NULL by the Update Database From Model and Update Model From Database wizards is fixed (Entity Framework)
- The bug with copying a property with Primary Key=True / Entity Key=True to a complex type is fixed (Entity Framework)
- The bug with naming of a composing unique key by Create Model Wizard / Update From Database Wizard in EF Core is fixed (Entity Framework)
- The bug with invalid attempt to cast unsupported Visual Studio project to type 'VSLangProj.VSProject' is fixed

Entity Framework support:
- Entity Framework 6.3 Preview 9 is supported
- A new NuGet package Devart.Data.MySql.EF6 with a .NET Standard 2.1 assembly, compatible with .NET Core 3, is added
- The bug with using the same database connection in several EF Core contexts is fixed
- The bug with applying a value converter to .Where expression with .Contains on nullable enum in EF Core 2 is fixed
- The bug with converting binary(16) to System.Guid in EF6 is fixed


dotConnect for MySQL Professional 8.13.1437
Entity Framework support:
- The bug with applying a value converter to a nullable column in EF Core 2 is fixed
- The bug with applying config.QueryOptions.ComparisonCollation to the update statements in EF6 is fixed


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

更新時間：2019-10-31
更新細節：

更新時間：2019-10-31
更新細節：

What's new in this version:

- Fixed a crash that occurred when executing a new view on the canvas

更新時間：2019-10-31
更新細節：