dotConnect for MySQL

What's new in this version:

dotConnect for MySQL Professional 9.3.10
- NET 8 compatibility
- Visual Studio 2022 version 17.9 Preview is supported

Entity Framework support:
- Entity Framework Core 8.0.0 is supported
- Entity Framework Core 7.0.14 is supported
- Entity Framework Core 6.0.25 is supported

LinqConnect (formerly known as LINQ to SQLite):
- .NET 8 compatibility

Entity Developer:
- EF Core 8 is added to the list of available Entity Framework versions in Create Model Wizard and Model Settings in EF Core Model
- .NET 8 is added to the list of available Target Framework versions in Create Model Wizard and Model Settings in EF, EF Core, and LinqConnect models
- The new extended property Do Not Generate OnConfiguring Method is added for the model in EF Core Model
- The bug with unnecessary generation of the GetByKey() method in a repository for entities without primary key (QueryType=True) in EF Core is fixed
- The bug with wrongly turned on without the ability to turn off options "Detect Many-to-Many associations" and "Detect Table-Per-Type inheritances" in Model Settings of EF Core 1, 2, 3 models is fixed
- The bug with the availability of the "Table-Per-Type Hierarchy (TPT)" option in the "Model Refactoring" dialog of EF Core 1, 2, 3 models is fixed
- The bug with the availability of the "Table-Per-Concrete-Type Hierarchy (TPC)" option in the "Model Refactoring" dialog of EF Core 1, 2, 3, 5, 6 models is fixed
- The hang of Visual Studio 2022 when saving the model is fixed


dotConnect for MySQL Professional 9.2.0
- MariaDB 11 is supported
- Visual Studio 2022 version 17.8 Preview is supported
- The error during installation on the 32-bit version of Windows has been fixed
- The bug with inserting milliseconds via prepared command is fixed

Entity Framework support:
- Entity Framework Core 7.0.5 is supported
- Entity Framework Core 6.0.16 is supported
- The bug with throwing "Unexpected null value in SQL fragments", when LINQ query has multiple .Include() with spatial DbGeometry and DbGeography properties, in EF4/EF5/EF6 is fixed
- The bug with throwing Microsoft.EntityFrameworkCore.Infrastructure.ManyServiceProvidersCreatedWarning by the UseMySql(DbConnection connection) extension method of DbContextOptionsBuilder in EF Core 6 and EF Core 7 is fixed
- The bug with using custom converters in mapping in EF Core 3 and higher is fixed

Entity Developer:
- The bug with detecting TINYINT(1) NOT NULL DEFAULT 1 as function-based column default value in EF Core Model is fixed
- The bug with detecting TINYINT(1) NOT NULL DEFAULT 1 as function-based column default value in EF Core Model is fixed
- The bug with detecting the numeric default value of string columns as function-based column default value in EF Core Model is fixed


dotConnect for MySQL Professional 9.1.151
- Visual Studio 2022 version 17.7 Preview is supported
- The bug with SSL certificates in .NET Standard (.NET Core) Projects is fixed

Entity Framework support:
- Entity Framework Core 7.0.5 is supported
- Entity Framework Core 6.0.16 is supported
- The bug with generating parameter prefixed by a double colon in EF Core 7 is fixed
- The bug with incorrect SQL translation of reused LINQ query, which includes array.Contains() and other expressions, in EF Core 5/6/7 is fixed

Entity Developer:
- The behavior is changed: the primitive properties by default have Inheritance Modifier = None
- The bug with the detection of non-existent changes while updating a model from a database is fixed
- The bug with creating Devart Entity Model in Visual Studio 2022 is fixed
- The bug with missing model context namespace in EntityFrameworkUnitOfWork.cs produced by the Repository And Unit of Work template (C#) in EF Core is fixed


dotConnect for MySQL Professional 9.1.134
- Visual Studio 2022 version 17.5 Preview is supported
- .NET 7 compatibility
- In-built encryption support for SQLite databases implemented: AES-128, AES-192, AES-256, Blowfish, CAST-128, RC4, Triple DES
- Description of the password field in SQLite connection editor is updated

Entity Framework support:
- Entity Framework Core 7.0.2 is supported
- Entity Framework Core 6.0.13 is supported
- Entity Framework Core 3.1.32 is supported

Entity Developer:
- The new extended properties Do Not Generate Serializable Attribute and Do Not Serialize are added for complex types in EF Core Model
- The bug with applying the Generate Serializable Attributes and Serialization Library settings of the EF Core template to the generated complex types is fixed


dotConnect for MySQL Professional 9.0.0
- NET 6 compatibility
- macOS 11 Arm64 (or "Apple Silicon" or "Apple M1") support
- Windows 11 is supported
- Visual Studio 2022 version 17.2 is supported
- Visual Studio 2022 version 17.3 Preview is supported

Entity framework:
- Entity Framework Core 6.0.5 is supported
- Entity Framework Core 5.0.17 is supported
- Entity Framework Core 3.1.25 is supported

Entity Developer:
- 64-bit version of standalone Entity Developer application is added
- 64-bit version of console Entity Developer application is added


dotConnect for MySQL Professional 8.21.2066
Entity Developer:
- The behavior is changed: turning off the "Save connection to" option in Model Settings of EF Core Model wipes out connection string literal from the generated code
- The behavior is changed: Devart.Data.MySql.Entity.EF5.dll compiled with .NET Framework 4.7 is used now in EF5 models

Entity Framework support:
- Mapping of internet/intranet data type System.Uri to MySQL string data types is supported in EF Core 3, EF Core 5, EF Core 6
- Mapping of network data types System.Net.IPAddress and System.Net.NetworkInformation.PhysicalAddress to MySQL string data types is supported in EF Core 5 and EF Core 6

The SQL translation of the following class members used in LINQ query is supported in EF Core 3, EF Core 5, EF Core 6:
- static method IsNullOrWhiteSpace() of the String class
- static property Today and instance property DayOfWeek of the DateTime class
- static methods Sqrt(), Max(), Min(), Log(), Log10(), Sin(), Cos(), Tan(), Asin(), Acos(), Atan(), Atan2() of the Math class

The SQL translation of the following class members used in LINQ query is supported in EF Core 5 and EF Core 6:
- static methods Abs(), Round(), Truncate(), Floor(), Ceiling(), Pow(), Sqrt(), Max(), Min(), Log(), Log10(), Sin(), Cos(), Tan(), Asin(), Acos(), Atan(), Atan2() of the MathF class

The SQL translation of the following class members used in LINQ query is supported in EF Core 6:
- static method Log2() of the Math and MathF classes
- The new EntityEF5net47Devart.Data.MySql.Entity.EF5.dll assembly compiled with .NET Framework 4.7 is added
- The new EntityEF5net47Devart.Data.MySql.Entity.Migrations.EF5.dll assembly compiled with .NET Framework 4.7 is added
- The new EntityEF5net47Devart.Data.MySql.Entity.Spatials.EF5.dll assembly compiled with .NET Framework 4.7 is added
- The new methods ExtractAsByte(), ExtractAsSByte(), ExtractAsInt16(), ExtractAsInt32(), ExtractAsInt64(), ExtractAsSingle(), ExtractAsDouble(), ExtractAsDecimal(), ExtractAsDateTime() are added to the MySqlJsonFunctions class for working with the JSON data type in LINQ to Entities queries
- The bug with generating the "Value cannot be null" error when dropping indexes via Code-First Migrations in EF Core is fixed
- The bug with a materialization used within the Let operator of LINQ query in EF6 is fixed
- The bug with using .Contains with a collection within .Select of LINQ query in EF Core 2 is fixed


dotConnect for MySQL Professional 8.20.2042
- The bug with reading SSL certificates from MemCryptStorage is fixed

Entity Developer:
- The model validation is improved: the errors are generated for all entities with QueryType=True in EF Core Model when EF Core version=EF Core 1 in Model Settings
- The bug with wrong automatic assigning QueryType=True for views added to EF Core Model, when EF Core version=EF Core 1 in Model Settings, is fixed
- The bug with throwing System.NullReferenceException when saving the changed value of the "Save connection to" option in Model Settings of EF Core Model is fixed

Entity Framework support:
- Entity Framework Core 6.0.1 is supported
- Entity Framework Core 5.0.13 is supported
- Entity Framework Core 3.1.22 is supported
- NetTopologySuite 2.4.0 is supported in EF Core 3, EF Core 5, and EF Core 6
- The bug with throwing the "Expression in SQL tree does not have type mapping assigned" error with NetTopologySuite in EF Core is fixed
- The bug with generating the "Value cannot be null" error when adding or dropping FK via Code-First Migrations in EF Core is fixed


dotConnect for MySQL Professional 8.19.2014
Entity Developer:
- The bug with parsing discriminator value as string, even when its type is different, in TPH inheritance of EF Core Model is fixed

Entity Framework support:
- Entity Framework Core 5.0.12 is supported
- Entity Framework Core 3.1.21 is supported
- The bug with ignoring .HasComputedColumnSql value by EnsureCreated() in EF Core is fixed


dotConnect for MySQL Professional 8.19.2001
- Visual Studio 2019 Preview support is discontinued
- The bug with throwing Devart.Common.LicenseException, when Devart.Data.MySql.dll is embedded into a single file application, is fixed
- The bug with applying .NET Standard licensing to .NET 6 projects is fixed

Entity Developer:
- The bug with launching Entity Developer after applying Windows 10 Update KB5006670 and Windows 11 Update KB5006674 is fixed

LinqConnect (formerly known as LINQ to MySQL):
- The bug with parsing TypeName values in XML mapping generated by Visual Basic template is fixed

Entity Framework support:
- Entity Framework Core 5.0.11 is supported
- Entity Framework Core 3.1.20 is supported
- The implementation of config.CodeFirstOptions.TruncateLongDefaultNames in EF6 .NET Standard compliant assemblies is improved: the generated names are constant, independent on a current domain and workstation
- The bug with using DateTime.Now, DateTime.UtcNow, DateTimeOffset.Now within LINQ query in EF Core 5 is fixed


dotConnect for MySQL Professional 8.19.1985
Entity Developer:
- The new property Validation Framework is implemented in the Data Transfer Object template for generating DataAnnotations attributes
- The new option "Save connection to" is implemented in Model Settings of EF Core Model to provide the ability to store the connection string in "Model file", "Entity Developer storage", "Environment variable"
- The new option "Enum Output" is added to the EF Core template to specify output for the generated enums
- The new property Generate UnitOfWork Repository Properties (by default, True) is implemented in the Repository and Unit Of Work template of EF Core Model for accessing the collections of entities
- The representation of one-to-one association with non-nullable properties on both ends is changed from 1 -> 1 to 0..1 -> 1 on a diagram in EF Core Model
- The bug throwing "Unknown property 'DoNotSerialize'.", when complex types and VB.NET template are used in EF Core Model, is fixed
- The bug with code generation for the Constrained option of Association Editor in the case of 0..1 -> 1 association in EF Core Model is fixed

Entity Framework support:
- Entity Framework Core 5.0.10 is supported
- Entity Framework Core 3.1.19 is supported
- Mapping of System.Decimal to MySQL DECIMAL with specified precision and scale in EF Core 5 is supported
- The definition of System.ICloneable is removed from .NET Framework assembly EntityEFCore3Devart.Data.MySql.Entity.EFCore.dll


dotConnect for MySQL Professional 8.19.1944
LinqConnect (formerly known as LINQ to MySQL):
- The new methods IsNotDistinctFrom() and IsDistinctFrom() are added to the Devart.Data.Linq.SqlMethods class

Entity Framework support:
- Entity Framework Core 5.0.8 is supported
- Entity Framework Core 3.1.17 is supported


dotConnect for MySQL Professional 8.19.1930
- Visual Studio 2019 version 16.11 Preview 2.0 is supported

Entity Developer:
- The behavior of the Regenerate Storage and Mapping functionality in EF Core Model is changed: the NOT NULL attribute of the column is reset to undefined now; after that, the behavior depends on the Nullable attribute of the class property only
- The bug with applying the Default Precision and Default Scale values from Model Settings to the non-decimal data types by Update To Database Wizard in EF Core is fixed

Entity Framework support:
- Entity Framework Core 5.0.7 is supported
- Entity Framework Core 3.1.16 is supported
- The bug with comparing enum values in EF Core 3 and EF Core 5 is fixed
- The bug with .Contains and .Length in EF Core 3 and EF Core 5, when using NetTopologySuite spatial functionality, is fixed


dotConnect for MySQL Professional 8.19.1905
- A new connection string parameter BinaryUuidOrder that allows using binary MySQL UUID order of bytes when converting binary(16) to System.Guid is added

Entity Developer:
- The new extended property Use Generic DbContextOptions Constructor Argument is added to model properties of EF Core Model
- The new extended property Do Not Generate Constructor With DbContextOptions Argument is added to model properties of EF Core Model
- The bug with generating the Equals method for entities with Record Type=True by C# EF Core template is fixed
- The bug with cleaning values of Length and Precision/Scale column's attributes by Update From Database Wizard in EF Core Model is fixed
- The bug with ignoring template's Validation Error Messages values in the generated code, when class property's Validate Expression is initialized and Validate Format is set to a non-default value, is fixed
- The bug with creating app.config in Visual Studio .NET Framework projects, when the "Rewrite connection string during regeneration" option is turned off in Model Settings, is fixed

Entity Framework support:
- Entity Framework Core 5.0.6 is supported
- Entity Framework Core 3.1.15 is supported
- The EF6 provider registration used with .NET Framework compliant assemblies is improved: the [DbConfigurationType(typeof(MySqlEntityProviderServicesConfiguration))] attribute set for DbContext descendant allows now calling the DbContext constructor, that accepts a connection string, with no need to register a custom IDbConnectionFactory implementation
- The bug with connection recovery after the initial connection attempt failure in EF Core is fixed


dotConnect for MySQL Professional 8.19.1866
Entity Developer:
- The new hotkey Alt+E is implemented in Property Editor for opening Column Editor in EF Core Model
- The bug with throwing "bufferAdapter is not a VsTextDocData" when saving a model in .NET Core, .NET Standard, .NET 5, .NET 6 projects of Visual Studio 2019 is fixed
- The bug with missing .NET Framework, .NET Core 1, .NET Core 2 options for the Target Framework property in Model Settings of EF Core Model in a standalone Entity Developer is fixed
- The bug with preserving Target Framework=.NET Framework in Model Settings of EF Core Model in a standalone Entity Developer is fixed
- The bug with adding tables to a model by Create Model Wizard, when the Database connection string parameter is not set, is fixed


dotConnect for MySQL Professional 8.19.1860
- Visual Studio 2019 version 16.10 Preview is supported
- Using SslStream to create SSL connections for .NET Standard (.NET Core) Projects is implemented
- Additional mode of parameter substitution in the query in the SSIS Data Flow Source component: substitution as is, without escaping
- The bug with a DateTime variable in the SSIS Source component is fixed

Entity Developer:
- .NET 6.0 is added to the list of available Target Framework versions in Create Model Wizard and Model Settings in EF Core, EF6, LinqConnect models
- The new extended property Record Type is added for classes in the case of C# EF Core template to generate records instead of classes in C# 9.0 or higher and .NET 5 or higher
- The new options "Private setter for store generated properties" and "Constructor parameter" are added to Model Settings in EF Core for controlling visibility of setter for store generated properties
- The new options "Don't show this message again" in the prompt window and "Prompt before generating code when there are model validation warnings" in the menu Options are implemented in a standalone Entity Developer to provide the ability not to stop code generation by warnings
- The new extended property Do Not Generate Default Constructor is added to EF Core Model for model, classes, and complex types
- The new extended property Do Not Generate Mapping is added to EF Core Model for class properties
- The JSON (Newtonsoft.Json, Microsoft.Text.Json) and YAML (YamlDotNet) serializations are supported in EF Core (via EF Core template) and EF6 (via DbContext template):
- The new template property Serialization Library is added for specifying the library used for serialization
- The new template property Serialize Original Column Names is added for controlling the appearance of original column names in serialization
- The new template property Serialize Navigation Properties is added for controlling the appearance of navigation properties in serialization
- The new template property Serialize Null Value is added for managing the behavior of nullable properties
- The new extended property Do Not Serialize is added for properties and navigation properties to exclude them from serialization
- The new extended property Serialization Name is added for properties and navigation properties to set custom names in serialization
- The Data Transfer Object template is improved:
- The new template property Serialization Library is added for specifying library used for serialization, possible values are Data Contract, JSON (Newtonsoft.Json), JSON (Microsoft.Text.Json), YamlDotNet
- The new extended property Do Not Serialize is added for properties and navigation properties to exclude them from serialization
- The new extended property Serialization Name is added for properties and navigation properties to set custom names in serialization
- The behavior is changed: WCF Data Contract Attributes is set to False by default now
- The following properties are marked as obsolete:
- the Generate Data Contracts property of the EF Core template
- the Do Not Generate Data Contract Attribute extended property of navigation properties in EF Core Model
- the WCF Data Contract Attributes property of the DbContext and Data Transfer Object templates
- the WCF DataMember Attribute on Navigation Properties property of the DbContext and Data Transfer Object templates
- The bug with creating app.config in Visual Studio .NET Core projects is fixed
- The bug with detecting the existing classes with QueryType=True by Update From Database Wizard in EF Core Model 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 5.0.4 is supported
- Entity Framework Core 3.1.13 is supported


dotConnect for MySQL Professional 8.19.1836
- The new command line option /disablegac that disables adding assemblies to GAC is added

Entity Developer:
- The behavior is changed in Entity Developer embedded into Visual Studio: lower versions in the EF Core version property of Model Settings are not hidden any more
- The behavior is changed in EF Core Model: QueryType=True is set now for all classes without PK
- C# code generation is improved: the using directives are generated instead of full namespaces in the names of attributes for DataAnnotations, NHibernate Validator, and Enterprise Library validation frameworks
- Code generation is improved: OnModelCreating(modelBuilder) of the base class is invoked now if the Base Context Type property of EF Core Model is initialized

Entity Framework support:
- Entity Framework Core 5.0.3 is supported
- Entity Framework Core 3.1.12 is supported
- The bug with translating Enum.HasFlag to SQL in EF Core 3 and EF Core 5 is fixed


dotConnect for MySQL Professional 8.19.1812
- The bug with blocking thread during retrieving a connection from the pool, when connections from the same pool are used in several threads, is fixed

Entity Developer:
- The new attribute DisplayName is implemented for model objects' extended properties which are available via template properties
- The new options --ContextNamespace and --DefaultNamespace are added to the Create-Model command of Console Entity Developer
- The new extended model property Base Context Type is added for specifying a parent class for the generated context in EF Core Model
- The new extended properties Base Type for complex types and Base Complex Type for model are implemented in EF Core Model
- The %type name% keyword is supported in the Base Type extended property of entities and complex types, and in Base Complex Type, Base Entity Type, Base Context Type extended model properties for setting generic base type in EF Core Model
- Code generation is improved: RelationalIndexBuilderExtensions.HasDatabaseName is generated now instead of RelationalIndexBuilderExtensions.HasName in EF Core 5
- Display names of extended properties in EF Core Model are updated: Entity Base is renamed to Base Type in class properties, Entity Base is renamed to Base Entity Type in model properties, Context Base is renamed to Base Context Type in model properties
- The bug with setting additional keyboard mapping scheme via menu Options on Windows with German display language is fixed

LinqConnect (formerly known as LINQ to SQLite):
- The new property Local is added to the Table and Table classes to return a collection of the entities attached to the context
- The new method GetEntityState(object entity) is added to Table class and ITable interface to return one of the EntityState values
- The bug with throwing "Bad key member '...' in association '...' of type '...'." in runtime by .NET Standard compliant assemblies is fixed

Entity Framework support:
- Entity Framework Core 5.0.2 is supported
- Entity Framework Core 3.1.11 is supported
- The new metadata to describe autoincremental columns via annotations in EF Core Code-First Migrations are implemented


dotConnect for MySQL Professional 8.19.1792
Entity Framework support:
- Entity Framework Core 5.0.1 is supported
- The bug with creating savepoints in EF Core 5 is fixed


dotConnect for MySQL Professional 8.19.1782
- Visual Studio 2019 version 16.9 Preview is supported
- The bug with updating projects that reference EF6 provider assembly via Upgrade Wizard is fixed

Entity Developer:
The new features are supported in Entity Framework 5.0:
- TPT inheritance
- Many-to-many associations
- The new types of properties IPAddress and PhysicalAddress

- The Model Refactoring functionality is supported for classes in EF Core Model
- The behavior is changed in a standalone Entity Developer: by default the Target Framework model property in EF Core Model is set to .NET 5 instead of .NET Framework
- The bug with saving non-default value of Target Framework model property in EF6 model modified with a standalone Entity Developer is fixed
- The bug with adding new arguments at the end of argument list instead of actual position in method signature by Update From Database Wizard is fixed

Entity Framework support:
- Entity Framework Core 5.0 is supported
- Entity Framework Core 3.1.10 is supported
- The behavior is changed: EF Core 3 assemblies available via NuGet package are compiled for .NET Standard 2.0 instead of .NET Standard 2.1
- The behavior is changed: EF Core 2 assemblies are no longer available via NuGet package but created in the provider installation folder
- The bug with using another context's connection in DbContextOptionsBuilder.UseMySql(connection) in EF Core is fixed


dotConnect for MySQL Professional 8.18.1759
- The bug with Visual Studio 2019 integration, when both v16.7 RTM and v16.8 Preview are installed on the same computer, is fixed
- The bug with missing Name and Owner properties of the MySqlConnection class in .NET Standard compliant assemblies is fixed

Entity Developer:
- The bug with reading templates from *.edps by console Entity Developer is fixed

Entity Framework support:
- Entity Framework Core 3.1.9 is supported


dotConnect for MySQL Professional 8.18.1739
- Visual Studio 2019 version 16.8 Preview is supported

Entity Developer:
- EF Core 3 spatial data types support is improved: in addition to Geometry and Geography, specific .NET NetTopologySuite types like GeographyPoint, GeographyLine are now available property types
- The default mapping for spatial data types in Server's Options is updated
- The bug with throwing "EntityProperty does not contain a definition for IsSpatialType", when custom template from previous versions is used, in EF Core Model is fixed
- The bug with applying On Delete Action=Cascade set in Association Editor to the Generate Database Script functionality in EF Core Model is fixed
- The bug with reading settings from *.edps by console Entity Developer is fixed

Entity Framework support:
- The bug with throwing System.NullReferenceException by the Code-First CreateDatabase() / Code-First Migrations functionality in EF Core is fixed
- The bug with reading boolean values by LINQ queries with multiple .Include() in EF4/EF5/EF6 is fixed


dotConnect for MySQL Professional 8.18.1730
- The SendCallStack property is added to the Devart.Common.DbMonitor class for possibility to turn off resource-demanding logging of CallStack
- The Filter property is added to the Devart.Common.DbMonitor class for possibility to choose events being logged
- The Devart.Common.DbMonitor class is improved: now values of the DateTime parameters sent to the dbMonitor tool are supplemented with milliseconds
- The bug with updating projects in folders below the main project by Upgrade Wizard is fixed-

Entity Developer:
- The error message in console Entity Developer is improved: now the text includes the list of all available templates if the specified name of template was incorrect
- The bug with saving a new model, which has never been saved before, after some time of work in a standalone Entity Developer is fixed
- The bug with generating mapping for the properties with Shadow=True in EF Core Model is fixed
- The bug with using spatial types inside complex types in EF Core Model is fixed-

Entity Framework support:
- Support for spatial data types in EF Core 3 is implemented
- The new names of spatial functions in MySQL Server 8 are supported in EF5/EF6 provider
- Entity Framework Core 3.1.8 is supported
- The new NuGet package Devart.Data.MySql.EFCore.NetTopolosySuite with a .NET Standard 2.1 assembly, that is compatible with .NET Core 3, is added
- The new EntityEFCore3Devart.Data.MySql.Entity.EFCore.NetTopolosySuite.dll assembly compiled with EF Core 3.1 and .NET Framework 4.6.1 is added
- The MySqlFunctions class, which allows using MySQL-specific functions in LINQ to Entities, is supported in EF Core
- The MySqlTextFunctions class, which allows using MySQL full-text search functionality in LINQ to Entities, is supported in EF Core


dotConnect for MySQL Professional 8.17.1696
- The bug with throwing System.NullReferenceException when opening *.edmx with invalid associations is fixed


dotConnect for MySQL Professional 8.17.1686
- The MySqlDependency constructor and AddCommandDependency overload, specifying how MySqlDependency should check command tables for changes, are added to MySqlDependency class along with the corresponding MySqlDependencyCheckTime enum

Entity Developer:
- The bug with detecting FK relationships to tables in other schemas by Create Model Wizard and Update From Database Wizard is fixed

LinqConnect (formerly known as LINQ to MySQL):
- The "Could not find element type in model" bug when loading XML mapping in .NET Standard LinqConnect assemblies is fixed
- The bug with using enums via .NET Standard compliant assemblies is fixed

Entity Framework support:
- The bug with incorrect SQL generation when using .Substring() in a .Select() statement in EF Core 2 is fixed
- The bug with reading the BINARY(16) column mapped to the byte[] class property, when "Binary As Guid=True;" is set in the connection string, in EF Core is fixed


dotConnect for MySQL Professional 8.17.1666
- Visual Studio 2019 version 16.7 Preview is supported
- The bug with mapping INT without explicitly specified display width is fixed

Entity Developer:
- .NET 5 is added to the list of available Target Framework versions in Create Model Wizard and Model Settings in EF6, EF Core, LinqConnect models
- The new option "Execute procedures for result set detection" is added to Model Settings of EF Core Model to control obtaining metadata of a procedure or function result set
- The new option "Use NULL parameter values" is added to Model Settings of EF Core Model to specify whether NULL parameter values are used for stored procedure execution
- The new option "Add complex types to diagram" is added to Model Settings of EF Core Model to control behavior of Create Model Wizard and Update Model From Database Wizard
- The new option "Add new complex types to the current diagram" is added to Update Model From Database Wizard of EF Core Model
- The new Primitive Default Value Generation property is added to EF, EF Core templates to determine whether to generate initialization for a primitive property based on database DEFAULT column value
- The new property Collection Property Type is added to EF template "DbContext" and EF Core template "EF Core" to determine .NET type used as a property type for the Many end of associations
- The new property Collection Initialization Type is added to EF template "DbContext" and EF Core template "EF Core" to determine .NET type used for initialization of the Many end of association; if it is set to None, then no initialization is generated
- The new property "Nullable Reference Types" is added to C# templates of EF, EF Core models to specify whether C# 8 nullable reference types and non-nullable reference types must be generated
- The new partial method is added to the OnModelCreating(DbModelBuilder modelBuilder) method generated by DbContext template of EF model
- The code generation of assigning DateTime.Now to the DateTime property mapped to the MySQL datetime column with the default value CURRENT_DATE or CURDATE() in EF, EF Core models is supported when Primitive Default Value Generation=LiteralOrExpression
- The EF Core model deserialization is improved: Entity Developer shows the full list of detected errors and tries to load the model with invalid elements or ignores such elements if their deserialization is not possible
- Console Entity Developer improvements:
- Import of stored procedures and functions via Create-Model command is supported
- The new options --Procedures and --Functions are added to Create-Model command for filtering stored procedures and functions; by default all procedures/functions are imported
- The new option --Execute is added to Create-Model command for executing procedures/functions to get metadata from result set
- The asterisk symbol (*) is supported in --Tables and --Views parameters of Create-Model to include all objects
- The bug with opening connection via some supported providers is fixed
- The bug with enumerating values separated with comma and without whitespace in --Templates, --Schemas, --Tables parameters is fixed
- The list of keywords and reserved words of MySQL being quoted by Entity Developer is updated
- The DbProviderFactories registration is implemented in Create Model Wizard for EF6 models and .NET Framework provider assemblies
- The new property Target Framework is added to Create Model Wizard and Model Settings of EF6 models
- The compatibility issue with JetBrains ReSharper is fixed
- The behavior is changed: the definition of auto-implemented property is put now on the single line with
- C# DbContext template of Devart Entity Model when ImplementINotifyPropertyChanging=False and ImplementINotifyPropertyChanged=False and PropertyChangePartialMethods=False
- C# EF Core template of Devart EF Core Model when PropertyChangeNotifiers=False and PropertyChangePartialMethods=False
- The behavior for the new EF, EF Core models is changed: Primitive Default Value Generation is set to Literal now instead of LiteralOrExpression
- The behavior is changed: the names of system types are generated without "System." prefix now in EF Core models; for example, it is DateTime instead of System.DateTime
- The behavior is changed: only one confirmation for executing stored procedure is requested by Entity Developer when drag&drop-ing procedure from Database Explorer to Model Explorer or diagram surface
- The behavior is changed: now the EF Core template generates an additional partial class for the context class when "File Per Class" and "Generate Partial Class" are set to True
- The bug with detecting strings, being expressions, as string literals when generating initialization of string properties basing on database columns' default values in EF, EF Core models is fixed
- The bug with detecting numbers, being quoted string literals, as strings when generating initialization of numeric properties basing on database columns' default values in EF, EF Core models is fixed
- The bug with missing default value in the generated code basing on DEFAULT value in a database, when any of ImplementINotifyPropertyChanging, ImplementINotifyPropertyChanged, PropertyChangePartialMethods options of DbContext template in EF is turned on, is fixed
- The bug with code generation for zero-or-one to zero-or-one association in the EF6 model with the DbContext template (Fluent Mapping=True) is fixed
- The bug with retrieving metadata of string columns' default values in MySQL 8 is fixed
- The bug with generating .HasMany end of one-to-many association in EF Core Model is fixed
- The bug with generating TPH mapping in EF Core 3 model is fixed
- The bug with false appearing the "Table or view '...' has no primary key columns, and the entity key for the corresponding storage entity was calculated automatically from other fields." warning in the Error List window is fixed
- The bug with generating new Guid() with Primitive Default Value Generation=Literal in EF, EF Core models is fixed

LinqConnect (formerly known as LINQ to MySQL):
- The bug with materializing elements, the types of which are explicitly converted from non-nullable to nullable on the client side, is fixed
- The bug with incorrect detection of altered column comment in a many-to-many association join table by Update From Database Wizard is fixed

Entity Framework support:
- Entity Framework 6.4.4 is supported
- The translation of the DateTime.AddMinutes() method in LINQ query into SQL statement in EF Core is supported
- The EF6 provider registration used with .NET Standard compliant assemblies is improved: the [DbConfigurationType(typeof(MySqlEntityProviderServicesConfiguration))] attribute set for DbContext descendant allows now calling the DbContext constructor, that accepts a connection string, with no need to register a custom IDbConnectionFactory implementation
- The bug with adding / subtracting DateTime and TimeSpan, DateTimeOffset and TimeSpan values in LINQ query in EF Core 3 is fixed
- The bug with SQL generation in EF Core 3, when enum values are used in CASE and COALESCE statements, is fixed


dotConnect for MySQL Professional 8.17.1612
LinqConnect (formerly known as LINQ to MySQL):
- The insert of the object, the type of which is an unmapped class inherited from a mapped class, is supported
- The bug with throwing System.NullReferenceException, when constructing the error saying that unmapped class is not supported, is fixed

Entity Developer:
- Command-line interface is implemented in a standalone Entity Developer
- The new property Context Name is added to Model Properties in EF Core Model
- The new property Target Framework is added to Model Properties in EF Core Model
- The provider registration is improved: requirement to put provider registration entry in the config file is not obligatory anymore
- Create Model Wizard is improved: now it allows installing multiple NuGet packages on the final step
- Model file tree in .NET Core / .NET Standard projects is improved: all generated code files and model files are nested under the same node in Solution Explorer

Entity Framework support:
- Entity Framework Core 3.1.3 is supported
- The .ToString() call for numbers, DateTime/DateTimeOffset properties and values in LINQ queries in EF Core is supported
- The call of Convert.ToString(value) in LINQ queries in EF Core is supported


dotConnect for MySQL Professional 8.17.1583
- SQL Server Integration Services 2019 (SSIS 2019) is supported
- The MySqlDataTable and MySqlDataSet classes are supported in .NET Standard 2.0
- The behavior is changed: pool is automatically cleared when AppDomain is being closed
- The bug with initializing NHibernate configuration on .NET Standard 2.0 is fixed

Entity Developer:
- The bug with returning multiple result sets in code generated by the EF Core template is fixed
- The bug with detecting MySQL computed columns is fixed

Entity Framework support:
- Entity Framework Core 3.1.1 is supported
- The bug with using nullable enum properties with default mapping to integers in LINQ query in EF Core 3.1 is fixed
- The bug with using value converters detected automatically by .HasConversion() in EF Core 3 is fixed
- The bug with using NULL constant values in EF Core 3 is fixed
- The bug with using binary operators AND, OR in EF Core 3 is fixed


dotConnect for MySQL Professional 8.15.1519
- The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported by Devart DataSet Editor
- The bug with inserting fractional seconds of TIME, DATETIME, and TIMESTAMP values via parameters of a stored procedure is fixed

Entity Developer:
- The Self-Contained Entity Configuration property is added to VB.NET version of EF Core template
- The Entities Configuration Output property is added to VB.NET version of EF Core template
- The code generation for the class properties with Alternate Key=True by VB.NET version of EF Core template is supported in EF Core model
- The bug with code generation, when Raw SQL Query is initialized in class properties, in EF Core 3 model is fixed
- The bug with generating .HasNoKey(), when Self-Contained Entity Configuration is set to True in properties of EF Core template, in EF Core 3 model is fixed
- The bug with generating alternate keys, when Self-Contained Entity Configuration is set to True in C# version of EF Core template, in EF Core model is fixed

Entity Framework support:
- The SQL generation in case of config.QueryOptions.UseCSharpNullComparisonBehavior=true in EF1/EF4/EF5/EF6 is improved
- The bug with using Scaffold-DbContext in EF Core 3 is fixed
- The bug with the redundant empty ORDER BY clause in a subquery, when paging is used, in EF Core 3 is fixed
- The bug with using .Contains within .Select of LINQ query in EF Core 2 is fixed
- The bug with generating invalid SQL when calling members of owned type in EF Core 2 is fixed


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