dotConnect for DB2	[email protected]
History

4.2.190 27-Dec-24

• .NET 9 compatibility
• Supported Visual Studio 2022 version 17.13 Preview
• Fixed an issue with applying the license key on Red Hat-based Linux systems (Red Hat 9, AlmaLinux 9, Rocky Linux 9) when the system-wide cryptographic policy was set to DEFAULT
• Fixed an issue with the missing Name and Owner properties in the DbCommandBase class within .NET Standard 2.0 compliant assemblies

Entity Framework support

• Supported Entity Framework Core 9
• Updated support for Entity Framework Core 8 to version 8.0.11
• Updated support for Entity Framework Core 6 to version 6.0.36
• Updated support for Entity Framework 6 (EF6) to version 6.5.1

Entity Developer

• .NET 9 has been added to the list of available Target Framework versions in the Create Model Wizard and Model Settings for EF and EF Core models
• Added the "Nullable Reference Types" property to C# Data Transfer Object templates to control whether C# 8 nullable and non-nullable reference types should be generated
• Fixed an issue with incorrect One-to-One relation multiplicity in EF Core models
• Fixed a bug with the incorrect detection of two unique indexes on the same column in the Update From Database wizard for EF Core models

4.1.104 08-Nov-24

• Supported Visual Studio 2022 version 17.12 Preview
• Fixed an issue with integration in Visual Studio 2015 and earlier versions
• Fixed the DataSet Wizard crash in Visual Studio 2022
• Fixed a design-time bug with the DB2DataTable Tasks interface element in Visual Studio 2022

Entity Framework support

• Updated support for Entity Framework Core 8 to version 8.0.10
• Updated support for Entity Framework Core 6 to version 6.0.35

Entity Developer

• Fixed an issue where the Update From Database Wizard reset navigation property names in EF Core models

4.1.21 06-Jun-24

Entity Framework support

• Updated support for Entity Framework Core 8 to version 8.0.6
• Updated support for Entity Framework Core 7 to version 7.0.20
• Updated support for Entity Framework Core 6 to version 6.0.31

4.1.20 29-May-24

• Supported Visual Studio 2022 version 17.11 Preview

Entity Framework support

• Updated support for Entity Framework Core 8 to version 8.0.5
• Updated support for Entity Framework Core 7 to version 7.0.19
• Updated support for Entity Framework Core 6 to version 6.0.30

4.1.10 17-Jan-24

• .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

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 and EF Core models
• The new extended property Do Not Generate OnConfiguring Method is added for the model in EF Core Model
• The bug with naming of local variables in the code generated for invoking stored procedures and functions with parameters in EF Core is fixed
• 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

4.0.0 16-Nov-23

• Visual Studio 2022 version 17.8 Preview is supported
• .NET Core is supported
• .NET 5, .NET 6, and .NET 7 compatibility
• The NuGet package 'Devart.Data.DB2' with .NET Core compliant assemblies is uploaded to www.nuget.org

Entity Framework support

• EF Core 5, EF Core 6, and EF Core 7 are supported
• The NuGet package 'Devart.Data.DB2.EFCore' with .NET Core compliant assemblies is uploaded to www.nuget.org
• The bug with using custom converters in mapping in EF Core 3 and higher is fixed

Entity Developer

• The bug with detecting the numeric default value of string columns as function-based column default value in EF Core Model is fixed

3.0.151 01-Jun-23

• Visual Studio 2022 version 17.7 Preview is supported

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

3.0.134 01-Mar-23

• Visual Studio 2022 version 17.5 Preview is supported

Entity Framework support

• 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

3.0.0 30-Jun-22

• 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 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.

2.6.1434 25-Jan-22

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

Entity Framework support

• 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

2.6.1410 21-Dec-21

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 3.1.22 is supported
• The bug with generating the "Value cannot be null" error when adding or dropping FK via Code-First Migrations in EF Core is fixed

2.6.1382 09-Nov-21

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 3.1.21 is supported

2.6.1369 21-Oct-21

• Visual Studio 2019 Preview support is discontinued

Entity Developer

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

Entity Framework support

• Entity Framework Core 3.1.20 is supported

2.6.1353 28-Sep-21

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 3.1.19 is supported
• Mapping of System.Decimal to DB2 DECIMAL with specified precision and scale in EF Core 5 is supported
• The definition of System.ICloneable is removed from .NET Framework assembly \Entity\EFCore3\Devart.Data.DB2.Entity.EFCore.dll

2.6.1312 30-Jul-21

Entity Framework support

• Entity Framework Core 3.1.17 is supported

2.6.1298 08-Jul-21

• 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 3.1.16 is supported
• The bug with comparing enum values in EF Core 3

2.6.1273 03-Jun-21

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 3.1.15 is supported
• The EF6 provider registration used with .NET Framework compliant assemblies is improved: the [DbConfigurationType(typeof(DB2EntityProviderServicesConfiguration))] 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

2.6.1234 09-Apr-21

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

2.6.1228 01-Apr-21

• Visual Studio 2019 version 16.10 Preview is supported
• 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

• 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 detecting the existing classes with QueryType=True by Update From Database Wizard in EF Core Model is fixed

Entity Framework support

• Entity Framework Core 3.1.13 is supported

2.6.1204 18-Feb-21

• 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 3.1.12 is supported
• The bug with translating Enum.HasFlag to SQL in EF Core 3 is fixed

2.6.1180 14-Jan-21

• SQL validation in Devart DB2 Source Editor is improved in SSIS project: Int and Double parameters are now quoted to avoid "syntax error" hover text
• 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
• The bug with fetching metadata of some schemas by Devart DB2 Source Editor in SSIS project 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

Entity Framework support

• 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

2.6.1160 17-Dec-20

• Compatible with other dotConnect providers

2.6.1150 03-Dec-20

• Visual Studio 2019 version 16.9 Preview is supported
• The bug with updating projects that reference EF6 provider assembly via Upgrade Wizard is fixed
• The bug with loading provider package during Visual Studio 2019 integration is fixed

Entity Developer

• The Model Refactoring functionality is supported for classes in EF Core Mode
• 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 3.1.10 is supported
• The bug with using another context's connection in DbContextOptionsBuilder.UseDB2(connection) in EF Core is fixed

2.6.1127 29-Oct-20

• The bug with Visual Studio 2019 integration, when both v16.7 RTM and v16.8 Preview are installed on the same computer, 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

2.6.1107 01-Oct-20

• Visual Studio 2019 version 16.8 Preview is supported

Entity Developer

• 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

2.6.1098 17-Sep-20

• 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

Entity Framework support

• Entity Framework Core 3.1.8 is supported
• The DB2Functions class, which allows using DB2-specific functions in LINQ to Entities, is supported in EF Core

2.6.1064 30-Jul-20

Entity Developer

• The bug with throwing System.NullReferenceException when opening *.edmx with invalid associations is fixed

2.6.1054 16-Jul-20

Entity Developer

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

Entity Framework support

• The bug with incorrect SQL generation when using .Substring() in a .Select() statement in EF Core 2 is fixed

2.6.1034 17-Jun-20

• Visual Studio 2019 version 16.7 Preview is supported

Entity Developer

• 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 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 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 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

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 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

2.6.980 02-Apr-20

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

2.6.951 20-Feb-20

• SQL Server Integration Services 2019 (SSIS 2019) is supported
• The behavior is changed: pool is automatically cleared when AppDomain is being closed

Entity Developer

• The bug with returning multiple result sets in code generated by the EF Core template 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<string>() 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

2.5.909 23-Dec-19

• Visual Studio 2019 version 16.5 Preview is supported
• The bug with using Toolbox component DB2DataSource in web projects of Visual Studio 2013, 2015, 2017, 2019 is fixed
• The bug with enabling Devart DataSet Editor in Visual Studio 2017 and Visual Studio 2019 is fixed

Entity Developer

• The bug with creating one-to-one association basing on an optional FK in EF Core Model is fixed
• The bug with code generation for oneOrZero-to-one and one-to-many associations based on an optional FK in EF Core Model is fixed
• The bug with generating a mapping for a unique constraint specified in owned type property of EF Core Model is fixed

Entity Framework support

• Entity Framework 6.4 is supported
• Entity Framework Core 3.1 is supported
• The new \Entity\EFCore3\Devart.Data.DB2.Entity.EFCore.dll assembly compiled with EF Core 3.1 and .NET Framework 4.6.1 is added
• The new config.CodeFirstOptions.TruncateAllLongNames option (default value is False) is added to use EF Core 2/EF Core 3 implementation for truncating long names of columns and PK/FK/IX/UX
• The config.DatabaseScript.ForeignKey.IndexCreation configuration option is supported in EF Core 1/EF Core 2/EF Core 3
• The bug with creating a unique constraint in the database via EF Core Code-First Migrations is fixed
• The bug with applying .ValueGeneratedOnAdd() to the string, guid, byte[] properties with .Key() and without .HasDefaultValueSql() in EF Core is fixed
• The bug with detecting implicit database column type, when model mapping and migration mapping are different, via EF Core Code-First Migrations is fixed
• The bug with generating SQL when using explicit cast in LINQ queries in EF Core 1/EF Core 2 is fixed

2.4.887 21-Nov-19

• The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported by Devart DataSet Editor

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 .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

2.4.872 31-Oct-19

• 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

2.4.867 24-Oct-19

• The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported by Devart DataSet Manager

Entity Developer

• The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported
• The compatibility issue with JetBrains ReSharper is fixed

2.4.838 12-Sep-19

• The integration with Visual Studio 2019 is improved: now the installation detects both 2019 Release and 2019 Preview versions

Entity Developer

• 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
• The bug with copying a property with Primary Key=True / Entity Key=True to a complex type is fixed
• The bug with naming of a composing unique key by Create Model Wizard / Update From Database Wizard in EF Core is fixed
• The bug with invalid attempt to cast unsupported Visual Studio project to type 'VSLangProj.VSProject' is fixed

Entity Framework support

• 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

2.4.805 25-July-19

Entity Framework support

• The bug with applying a value converter to a nullable column in EF Core 2 is fixed

2.4.790 04-July-19

• 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

2.4.770 06-Jun-19

• Deprecated design-time Synchronous API calls are no longer used with Visual Studio 2019 and Visual Studio 2017

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 inserting data into MigrationHistory__ by EF6 Code-First Migrations for an enormous model is fixed

2.4.734 11-Apr-19

• 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

2.3.725 28-Mar-19

• Visual Studio 2019 Release Candidate 4 is supported

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
• The bug with calling DbExecutionStrategy.ShouldRetryOn(Exception), when the first connection fails to open, is fixed

2.3.696 14-Feb-19

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 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

2.3.675 10-Jan-19

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 .HasComputedColumnSql functionality for the CreateTable operation in EF Core Code-First Migrations is supported
• The new extension method Database.IsDB2() 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

2.3.646 29-Nov-18

Entity Developer

• The new Generate GeneratedCode Attributes option (by default, False) is added to the DbContext template in EF4/EF5/EF6 and the EF Core template
• The new Generate Dummy Comments option (by default, False) is added to the DbContext template in EF4/EF5/EF6
• The code formatting is fixed in the DbContext template in EF4/EF5/EF6 and the EF Core template
• The code generation of a default value for the String property mapped to the column with a default value, that contains a unicode literal with N-prefix, is supported in EF and EF Core
• The bug with generating fluent mapping for the TPC inheritance by VB.NET version of DbContext template in EF4/EF5/EF6 is fixed

Entity Framework support

• The bug with quoting the table alias, that includes an invalid character, in the SQL query generated by EF Core is fixed
• The bug with generating a subquery within the IN clause in EF Core 2 is fixed
• The bug with generating a subselect within the CASE clause in EF Core 2 is fixed
• The bug with comparing columns, that use a value converter, to parameters and constants in EF Core 2 is fixed

2.3.621 25-Oct-18

Entity Framework support

• Entity Framework Core 2.1.4 is supported
• The bit-wise functions OR, AND in EF Core are supported
• The bug with throwing "Collection was modified; enumeration operation may not execute" by EF Core provider in multithreaded applications is fixed

2.3.597 20-Sep-18

Entity Developer

• Using an extended property of type OutputInfo is supported
• Code generated for nullable properties is simplified: now T? is generated instead of System.Nullable<T>
• An additional constructor that accepts DbContextOptions as an argument is added to the DbContext class descendant in the VB.NET version of the DbContext template for EF Core
• The bug with "No database provider has been configured for this DbContext." in the DbContext template for EF Core is fixed
• The bug with code generation for nullable properties for EF1/EF4/EF5/EF6 is fixed

Entity Framework support

• Entity Framework Core 2.1.3 is supported
• The bug with throwing an error by context.Database.Migrate(), when the __EFMigrationsHistory table already exists but tables being mapped by model classes are not created yet, in EF Core 2 is fixed
• The bug with a memory leak in EF Core 2, when a connection is set for DbContext as an DB2Connection instance, and not via a connection string, is fixed
• The bug with creating database objects in the same schema by several EF Core contexts in Code-First approach is fixed

2.3.584 30-Aug-18

Entity Developer

• The bug with setting password as clear text in connection string when "Persist Security Info=False;" is fixed

Entity Framework support

• Entity Framework Core 2.1.2 is supported
• The misleading "The current provider does not support ambient transactions." warning, generated by TransactionScope in EF Core 2.1, is disabled
• The bug with using Scaffold-DbContext against multicolumn PK, FK, IX, UX in EF Core 2 is fixed

2.3.570 09-Aug-18

Entity Framework support

• The behavior is changed: the default value of config.QueryOptions.UseCSharpNullComparisonBehavior is true now in EF Core
• The bug with using the RenameIndex operation, when index name exceeds a max length allowed by the server and has to be transformed to a shorter name, in EF Core Code-First Migrations is fixed
• The bug with incorrect generation of shortened PK/FK/IX/UX names in EF Core when using .NET Standard provider assemblies is fixed
• The bug with SQL generation for comparing column with parameter in EF Core 2 is fixed

2.3.558 19-Jul-18

Entity Framework support

• The bug with paging in EF Core 2.1 is fixed
• The bug with using the aggregate functions in EF Core 2.1 is fixed
• The bug with processing arguments of functions mapped via .HasDbFunction in EF Core 2 is fixed
• The bug with applying a filter with implicit EnumToStringConverter via LINQ queries in EF Core 2 is fixed
• The bug with using the String.CompareTo method via LINQ queries in EF Core is fixed

2.3.540 21-Jun-18

Entity Developer

• Entity Framework Core 2.1 is supported
• Query type support is added: classes now have the Query Type property, and if it is set to true, this class is generated as a query type
• Lazy loading for Entity Framework Core 2.1 is supported:
• Model now has the Use Lazy-Loading Proxies property, which enables lazy loading on the model level
• Navigation properties now have the Lazy property, which enables lazy loading for a specific navigation property
• Properties now have the Constructor Parameter property, for configuring a parameterized constructor of the class
• The "Include Environment Variables" property, determining whether context configuration will be extended with environment variables when a connection string from the appsettings.json file is used, is added to the EF Core template
• The "Json File Base Path" property, specifying the base path for file-based providers when a connection string from the appsettings.json file is used, is added to the EF Core template

Entity Framework support

• Entity Framework Core 2.1.1 is supported
• The bug with applying the updated provider behavior after changing connection string options in EF Core 2 is fixed
• The bug with generating incorrect SQL when using IndexOf expression in EF Core is fixed

2.2.520 24-May-18

Entity Framework support

• Entity Framework Core 1.1.5 is supported
• Entity Framework Core 2.0.3 is supported

2.2.502 27-Apr-18

Entity Developer

• The new Controller Area extended class property is added to EF Core Model
• The check of conditions for setting optionsBuilder.Use... in the generated OnConfiguring method by the EF Core template is improved

Entity Framework support

• The bug with retrieving the DateTimeOffset and TimeSpan data in EF Core is fixed

2.2.483 29-Mar-18

• The bug with throwing the "IDE not supported" exception by DataSet Manager in Visual Studio 2017 of versions 15.6.* is fixed

Entity Developer

• The new SQL Type, Size, Precision, Scale options are added to the Parameters tab in Method Editor of EF Core Model
• The process of synchronizing methods and parameters with database stored procedures in EF Core Model is improved
• The bug with adding entry to appsettings.json, when "Use the following connection string from App.Config" and "Rewrite connection string during regeneration" in Model Settings are turned on, is fixed
• The bug with throwing the "Multiple constructors accepting all given argument types have been found in type '...'. There should only be one applicable constructor." error by the code generated with the MVC Controller template in ASP.NET Core Web Application is fixed
• The bug with missing DataMember attribute on the Many end of an association, when using the EF Core template with "Generate Data Contracts=True", is fixed
• The bug with the Retrieve Data functionality on the base class of TPH inheritance is fixed
• The bug with the Find Next functionality of T4 Editor embedded into Visual Studio is fixed
• The bug with throwing the "IDE not supported" exception by Entity Developer in Visual Studio 2017 of versions 15.6.* is fixed

Entity Framework support

• Entity Framework Core 2.0.2 is supported

2.2.454 15-Feb-18

Entity Developer

• Support for ASP.NET Core MVC is added to the Data Annotations Metadata template
• The bug with applying the DevartEFCoreGenerator custom tool in Visual Basic .NET Core projects is fixed

2.2.429 11-Jan-18

• The type of the Offset and Length properties of the ScriptProgressEventArgs class is changed from Int32 to Int64

Entity Developer

• The ModelNameAsFilesPrefix property is implemented in the RepositoryAndUnitOfWork template
• The code generation for async method calls in the EF Core template is improved
• Support for ASP.NET Core MVC is added to the MVC Controller template

Entity Framework support

• Entity Framework Core 1.1.4 is supported
• Entity Framework Core 2.0.1 is supported
• The bug with using bool properties in the Where() clause of LINQ query in EF Core 2 is fixed
• The bug with ignoring the maxLength, precision, scale property settings by update-database in EF Core is fixed
• The bug with using enumerations in EF Core model is fixed
• The bug with LIKE (.StartsWith/.Contains./EndsWith) is fixed
• The bug with case-insensitive comparison is fixed

2.2.399 23-Nov-17

• The CancelEditRowIfUpdateFailed property, determining whether to call CancelEdit for the row after update of the row is failed when data binding is used, is added to DB2DataTable

Entity Developer

• The new "Detect function-based column default value" option is implemented in Model Settings of EF Core model
• The code generation for async method calls is added to the EF Core template
• The usage of long identifiers (up to 140 symbols) for naming model objects is supported

Entity Framework support

• Entity Framework 6.2 is supported
• The SQL generation for subselects, when using Distinct(), in EF1/EF4/EF5/EF6 is optimized
• The Code-First Migrations functionality in EF Core is improved:
• the operations InsertData / UpdateData / DeleteData (introduced in EF Core 2), CreateSequence, AlterSequence, RestartSequence, DropSequence are supported
• The bug with using UseDB2(DbConnection) extension method of DbContextOptionsBuilder in EF Core is fixed
• The bug with using Add-Migration in Package Manager Console for adding code-based Code-First Migrations in EF Core 2 is fixed
• The bug with using collections in a .Contains() method in EF Core 2 is fixed
• The bug with JOIN conditions in SQL generated from LINQ query in EF1/EF4/EF5/EF6 is fixed
• The bug with using multiple .Include() in EF Core 2 is fixed
• The bug with processing conditions in LINQ queries with joins in EF Core is fixed

2.2.381 30-Oct-17

Entity Developer

• Entity Framework Core 2.0 is supported
• The Retrieve Data functionality via Model Explorer for EF Core 2 is implemented
• The bug with escaping invalid XML characters in the comments generated by templates is fixed

Entity Framework support

• Entity Framework Core 1.1.3 is supported
• Entity Framework Core 2.0 is supported

2.2.348 06-Sep-17

• The integration with Visual Studio 2017 is improved: the installation is now silent, without VSIX Installer prompt window
• The new menu Tools > DB2 > Upgrade Wizard, which allows to update project for using the newer provider version, is implemented

Entity Developer

• The Devart Visual Studio packages registration into Visual Studio 2017 is improved: the packages are now available for all Windows accounts
• The bug with losing Toolbar and docking customizations of a standalone designer during reinstall is fixed

Entity Framework support

• The new config.DatabaseScript.Column.NumericIdentityBehavior configuration option is implemented to manage a generation of columns with StoreGeneratedPattern="Identity"
• The bug with using a variable with null value in LINQ query in EF Core is fixed
• The bug with missing schema prefix in the name of index created by EF Code-First Migrations is fixed

2.2.326 03-Aug-17

Entity Developer

• The new Raw SQL Query class property and SQL method property with the corresponding editors are implemented in Entity Framework Core
• The bug with generating code for the PropertyChanging event is fixed
• The bug with applying Custom Tool by Devart Entity Model (*.edml) in VS 2017 .NET Core projects is fixed
• The bug with quoting default table and column names in EF Core is fixed
• The bug with registering DevartEntityDeploy on the workstation with just Build Tools for Visual Studio 2017 installed is fixed

Entity Framework support

• The bug with inserting data into MigrationHistory__ by EF6 Code-First Migrations for large model is fixed
• The bug with using Contains() in multiple LINQ queries in EF Core is fixed
• The bug with comparison and binary operations in EF Core is fixed

2.2.314 13-Jul-17

Entity Developer

• The behaviour is changed: IsRequired(false / true) for navigation properties is always generated in EF Core fluent mapping now
• The bug with throwing "Can't load provider assembly." by EF6 model in a standalone Entity Developer is fixed
• The bug with serializing user defined extended properties for associations is fixed
• The bug with a Devart provider not found in Entity Developer as a standalone application when the provider is installed without placing Devart assemblies to the GAC is fixed

2.2.299 22-Jun-17

• The compatibility with Visual Studio 2017 Updates is improved
• The bug with using the 'Do not install assemblies in the GAC' install wizard functionality for Visual Studio 2017 is fixed

Entity Developer

• The bug related to the conflict of Entity Developer with dbForge SQL Complete is fixed

2.2.280 25-May-17

• The bug with previewing a DataSet is fixed

Entity Developer

• The .NET Core projects in Visual Studio 2017 are supported
• The Snake case in both Model and Database naming rules is supported via the new "Add underscore" option

Entity Framework support

• Entity Framework Core 1.1.2 is supported
• The support of EF Core models with string columns, which are defined without length limit and participate in PKs, FKs, indices, is improved
• The possibility to use command interception for EF6 commands executed within batch updates is implemented
• The compatibility with ASP.NET Core Identity is improved
• The behavior is changed: System.DateTime is mapped now to TIMESTAMP(7) instead of TIMESTAMP via EF Code-First Migrations for DB2 for LUW 9.7 and higher
• The bug with using config.CodeFirstOptions.TruncateLongDefaultNames in EF Core is fixed
• The bug with using the ForDB2HasColumnName and ForDB2HasColumnType modelBuilder methods with the value-type properties in EF Core is fixed
• The bug with generating database type name via EF Code-First Migrations in case of System.Byte[] is fixed
• The bug with paging in EF Core is fixed

2.2.230 16-Mar-17

• Visual Studio 2017 is supported

Entity Developer

• The bug with generating the virtual keyword when Inheritance Modifier=None is fixed

Entity Framework support

• Entity Framework Core 1.1.1 is supported
• The bug with generating DDL for Guid properties by EF Code-First Migrations is fixed

2.1.220 02-Mar-17

• Visual Studio 2017 Release Candidate 4 is supported

Entity Developer

• The bug with throwing the "Stack empty" error after stopping validation before code generation in a standalone version is fixed
• The bug with a workability of the "Validate on Build" option in Model Settings is fixed
• The bug with compilation of the EF Core template after copying it to model folder is fixed

Entity Framework support

• The translation of collection's Contains method in LINQ query to SQL statement in EF Core is supported

2.1.205 09-Feb-17

• Visual Studio 2017 Release Candidate 3 is supported

2.1.200 02-Feb-17

Entity Framework support

• The AddUniqueConstraintOperation and DropUniqueConstraintOperation operations are supported in EF Core Code-First Migrations
• The bug with creating a predefined Migrations History table in EF Core, when config.Workarounds.DisableQuoting = true, is fixed

2.1.187 16-Jan-17

• Visual Studio 2017 Release Candidate is supported

Entity Framework support

• The bug with comparing non-nullable properties in LINQ query when config.QueryOptions.UseCSharpNullComparisonBehavior=true is fixed
• The bug with using AddForeignKeyOperation and DropForeignKeyOperation in EF Core Code-First Migrations is fixed
• The bug with throwing the "Operation is not valid due to the current state of the object" error with Batch Updates in EF1/EF4/EF5/EF6, if the previous SaveChanges() failed, is fixed

2.1.172 22-Dec-16

Entity Framework support

• The bug with grouping by constant expression in EF1/EF4/EF5/EF6 when using DevExpress.XtraGrid.GridControl is fixed
• The bug with creating indices by EF Core Code-First migrations is fixed

2.1.162 08-Dec-16

• The 'Do not install assemblies in the GAC' check box that allows disabling placing the provider assemblies to the GAC is added to the Install Wizard
• The bug with generating an error when using DB2Monitor on Linux is fixed
• The bug with not using parameters value in ParentRelation data in DB2DataTable.SelectCommand is fixed

Entity Developer

• The possibility to choose whether to add new entities to a diagram or not in Update From Database Wizard is implemented
• The behaviour is changed: now the DbContext template generates an additional partial class for the context class when "File Per Class" and "Generate Partial Class" are set to True

Entity Framework support

• Entity Framework Core 1.1.0 is supported
• The Scaffold-DbContext NuGet command of Package Manager Console for generating a model basing on the existing database schema is supported in EF Core
• Batch Updates support in EF Core is added
• The config.DatabaseScript.Schema.DeleteDatabaseBehaviour option is supported in EF Core
• The behaviour is changed: the errors thrown by executing SQL statement DROP SCHEMA are ignored now
• The bug with shortening PK, FK, IX, UX names in the Code-First CreateDatabase/CreateDatabaseScript functionality when config.CodeFirstOptions.TruncateLongDefaultNames=True is fixed
• The bug with comparison in LINQ query when config.QueryOptions.UseCSharpNullComparisonBehavior=true is fixed

2.1.131 20-Oct-16

• Compatible with other dotConnect providers

2.1.121 06-Oct-16

Entity Developer

• The generation of static methods by the EntityObject template is supported via the new property Direct Call of EntityMethod

Entity Framework support

• The bug with generating autoincrement fields in DDL script for Int16 properties via Code-First Migrations is fixed
• The bug with comparing bool class property with some value in EF Core is fixed

2.1.111 22-Sep-16

• The bug with binary serialization of DB2Exception is fixed

Entity Developer

• The bug with moving mapping from abstract base class to child classes of TPH inheritance in the fluent mapping generated by the DbContext template is fixed

Entity Framework support

• Entity Framework Core 1.0.1 is supported
• The new optional parameter Action<DB2DbContextOptionsBuilder> is added to UseDB2() extension method of DbContextOptionsBuilder in EF Core
• The bug with processing IN expressions in EF Core is fixed
• The bug with retrieving objects of TPH hierarchy in EF Core is fixed

2.1.97 01-Sep-16

• The bug with data preview in the DB2DataTable designer when the command text was changed is fixed

Entity Framework support

• The DatabaseFacade.GetDB2Connection() extension method, which returns DB2Connection, is implemented in EF Core
• The bug with using the DatabaseFacade.UseTransaction() method in EF Core is fixed
• The bug with nullable parameters in EF Core is fixed
• The bug with throwing System.NullReferenceException when using TPH inheritance in EF Core is fixed
• The bug with not throwing concurrency check exception on invoking DbContext.SaveChangesAsync() is fixed

2.1.82 11-Aug-16

Entity Developer

• The bug with setting value of the Value Generated property attribute in the EF Core model is fixed

Entity Framework support

• The bug with executing the UseDB2(DbConnection connection) extension method of DbContextOptionsBuilder in EF Core is fixed
• The bug with using the DbContext(DbConnection connection) overload in EF Core is fixed
• The bug with using EF Core logging is fixed
• The bug with using enum values in EF Core is fixed
• The bug with throwing DbUpdateConcurrencyException in EF Core is fixed
• The bug with using comparisons in LINQ queries in EF Core is fixed

2.1.67 21-Jul-16

Entity Framework support

• DB2CSharpMigrationCodeGenerator and DB2VisualBasicMigrationCodeGenerator for code-based migrations are implemented for EF4, EF5, EF6
• The bug with convertation of enum values in parameters when using EF Core is fixed

2.1.55 07-Jul-16

Entity Developer

• The possibility to set values of stored procedure parameters for getting metadata to generate automatically the corresponding complex type is implemented
• Entity Framework Core 1.0 RTM is supported
• The behaviour is changed: the ObservableCollection navigation properties are initialized now in a default class constructor

Entity Framework support

• Entity Framework Core 1.0 RTM is supported

2.1.45 23-Jun-16

• The bug with not adding records to the RSPreviewPolicy.config and RSReportDesigner.config files for correct work in Reporting Services(SSRS) projects is fixed

Entity Framework support

• The DB2ConventionSetBuilder class is implemented in the Entity Framework Core support

2.1.35 09-Jun-16

• Microsoft SQL Server Data Tools Business Intelligence (SSDT-BI) project templates for Analysis Services, Reporting Services, and Integration Services (mapping wizards) in Visual Studio 2015 are supported
• Microsoft SQL Server 2016 is supported in SSIS DataFlow components

2.0.26 26-May-16

Entity Developer

• Entity Framework Core support is added
• The DbProviderFactory provider registration in application's *.config is supported by the Entity Developer version integrated into Visual Studio

Entity Framework support

• Entity Framework Core RC2 is supported

2.0.17 12-May-16

• Compatible with other dotConnect providers

2.0.12 05-May-16

Entity Framework support

• Upgrade Wizard is improved for upgrading projects with the Entity Framework functionality

2.0.7 21-Apr-16

• The Run Once Command connection string parameter, which specifies a command to execute when the connection is opened the first time and not executed when the connection is taken from the pool, is added
• The new LoadTable overloads for loading data from a IDataReader, array of rows, or only rows with a specific RowState from a DataTable are added to the DB2Loader class
• Truncate member that represents the TRUNCATE TABLE statement is added to the SqlStatementType enum

Entity Framework support

• Entity Framework Core RC1 is supported
• Entity Framework-related assemblies are renamed

1.8.717 17-Mar-16

• Compatible with other dotConnect providers

1.8.703 25-Feb-16

• Compatible with other dotConnect providers

1.8.693 11-Feb-16

Entity Developer

• The code generation by the DbContext template (fluent mapping) for navigation properties is fixed

Entity Framework support

• The bug with executing the same queries in multithreaded applications is fixed

1.8.684 21-Jan-16

• Compatible with other dotConnect providers

1.8.664 24-Dec-15

• Compatible with other dotConnect providers

1.8.659 17-Dec-15

• Compatible with other dotConnect providers

1.8.644 26-Nov-15

Entity Framework support

• The bug with applying config.QueryOptions.CaseInsensitiveComparison for non SELECT queries is fixed
• The bug with some DB2Functions within LINQ queries is fixed

1.8.636 12-Nov-15

• The bug with throwing the "Unknown connection string parameter" exception is fixed

1.8.622 22-Oct-15

Entity Developer

• The bug with applying naming rules for model properties is fixed

1.8.607 01-Oct-15

• Compatible with other dotConnect providers

1.8.598 17-Sep-15

Entity Developer

• The bug with wrong diagram layout is fixed
• The bug with checking the evaluation period in the trial version is fixed

1.8.593 10-Sep-15

• The bug with throwing the "IDE not supported" exception by DataSet Manager in Visual Studio 2015 is fixed

1.8.579 20-Aug-15

Entity Developer

• The Use ObservableCollection property of the DbContext template is implemented

Entity Framework support

• The bug with throwing System.NullReferenceException when applying logical OR operator to the results of several IEnumerable<T>.Contains(T t) is fixed

1.8.565 30-Jul-15

• Visual Studio 2015 is supported

Entity Developer

• The bug with generating namespace for the IsExternal enum is fixed

1.7.558 16-Jul-15

Entity Developer

• The bug with freezing Visual Studio when using the Find dialog in large models is fixed

Entity Framework support

• The performance of generating SQL for Enumerable.Contains in LINQ queries is improved by supporting a new expression type, DbInExpression, in Entity Framework 6

1.7.548 02-Jul-15

• Compatible with other dotConnect providers

1.7.538 18-Jun-15

Entity Framework support

• The bug with loosing elements within the IN clause of the generated SQL for the LINQ Contains clause is fixed

1.7.523 28-May-15

• Visual Studio 2015 Release Candidate is supported

Entity Developer

• The bug with detecting the default values of attributes added via the Attributes menu is fixed
• The bug with generating code by MVC Controller template is fixed

1.7.508 07-May-15

• Compatible with other dotConnect providers

1.7.498 23-Apr-15

Entity Framework support

• The bug with generating columns in subqueries of a complex LINQ to Entities query containing limit expressions is fixed

1.7.490 09-Apr-15

Entity Developer

• The bug with ignoring the "Delete Cascaded" property of the association when performing the Update Database From Model and Update Model From Database wizards is fixed

1.7.480 26-Mar-15

• Microsoft SQL Server Data Tools Business Intelligence (SSDT-BI) project templates for Analysis Services and Integration Services in Visual Studio 2013 are supported
• SSIS DataFlow Source and Destination components are supported in SSDT-BI for Visual Studio 2013

Entity Developer

• The behaviour is changed: now the default values are not set for string properties, that correspond to fields with the default values like expressions
• The bug with missing settings for the LazyLoadingEnabled property in the generated code when working with the Self-Tracking Entity template is fixed
• The bug related to working with the Table Per Type (TPT) and abstract entity classes when synchronization is enabled is fixed

Entity Framework support

• The bug with reading the second and consequent result sets, returned by stored procedure, is fixed

1.7.460 26-Feb-15

• The bug with using System.Runtime.CompilerServices.ExtensionAttribute in Devart.Data.Synchronization.dll for the projects with 3.5 and higher versions of .NET Framework is fixed

1.7.453 12-Feb-15

Entity Developer

• The bug with the wrong code generation for Table Per Concrete Type (TPC) hierarchy when DbContext template is used with Fluent Mapping=True and Mapping Generation Strategy=UseConfigurationClasses (or UseOnModelCreatingMethod) options is fixed

1.7.445 02-Feb-15

Entity Developer

• The bug with "Trial period expired" is fixed

1.7.443 29-Jan-15

• The bug in Sync Framework support with synchronization scopes, having a filter based on a template, is fixed

Entity Developer

• The bug with generating code by the MVC Controller template for multiple self-associations is fixed

1.7.434 15-Jan-15

• The bug with throwing System.InvalidOperationException by connection pooling in multithreaded applications under high loads is fixed

Entity Developer

• The bug with generating connection string supplied to constructor in case of placing the model in a subfolder of the project is fixed

1.7.414 18-Dec-14

• Compatible with other dotConnect providers

1.7.404 04-Dec-14

Entity Developer

• The bug with the incorrect code generation, when the "Enable WinForms Data Binding" property of the DbContext template (Visual Basic) is set to True, is fixed
• The bug with missing attributes for the enum members when generating code with the DbContext template is fixed

Entity Framework support

• The bug related to working with the customized Migration History table and Entity Framework 6 is fixed

1.7.394 20-Nov-14

• ADO.NET implementation of ASP.NET Identity 2.0 support is improved
• The new IQueryableUserStore interface is implemented in the UserStore class
• The new IQueryableRoleStore interface is implemented in the RoleStore class
• The enableExpiredSessionAutoDeletion and expiredSessionAutoDeletionInterval options for deleting expired sessions are added to the session-state store provider definition in the web.config file
• The behaviour is changed: the DB2Monitor now hides information about the password connection string parameter
• The bug with the conflict between versions of Devart.Data.DB2.Web.dll assembly for ASP.NET 2 and ASP.NET 4 is fixed

Entity Developer

• The bug related to script generation by the "Generate Database Script" wizard with the "Include Drop" option is fixed
• The bug related to resetting enum arguments of custom attributes in the standalone version is fixed
• The bug with incorrect execution of the "Create Storage and Mapping" command for an association is fixed

1.7.384 06-Nov-14

• The new \Web\ASP.NET 45\Devart.Data.DB2.Web.dll assembly (its revision number is 5) is added to the provider installation folder to support SimpleMembership in MVC5

Entity Developer

• The bug related to disappearance of the foreign key property when performing "Create Storage and Mapping" from the context menu of the association is fixed
• The bug related to the "'End Class' must be preceded by a matching 'Class'" error when adding stored procedure to the model and using DbContext template in Visual Basic projects is fixed
• The bug with reading all constructor parameters for attributes when opening model is fixed

1.7.375 23-Oct-14

• The bug with applying the CurrentSchema connection string parameter to the names of stored procedures used in DB2Command is fixed

1.7.365 09-Oct-14

• The Enterprise Library 6 support is added; all previous versions of Enterprise Library are no longer maintained

1.7.355 25-Sep-14

Entity Developer

• The behaviour is changed: now the default value for the 'File Per Class' option of the DbContext template is True
• The behaviour is changed: Generate Database Script From Model saves the output in ASCII format if there are no unicode symbols in the script; UTF-8 is used otherwise
• The bug with model creation when using multiple naming rules (suffixes, prefixes) is fixed
• The bug with generating .HasPrecision for decimal types when using non-attribute fluent mapping (DbContext template) is fixed

1.7.345 11-Sep-14

Entity Framework support

• The bug with throwing the error with the "Connection must be opened" text instead of the message which explains the problem is fixed

1.7.340 04-Sep-14

• The bug with invalid script when table has only primary key columns for Sync Framework support is fixed

Entity Developer

• The Remove Invalid Characters option (by default, True) is added to the Model Naming rules; if it is set to False, all invalid characters will be replaced with underscores
• The Enable WinForms Data Binding property of the DbContext template is implemented
• The Property Change Partial Methods property of the DbContext template is implemented for generating partial methods On%PropertyName%Changing and On%PropertyName%Changed for each primitive property of entity classes
• The behaviour is changed: now partial configuration classes are generated when DbContext template is used with Fluent Mapping=True and Mapping Generation Strategy=UseConfigurationClasses options
• The bug with the wrong code generation for associations when DbContext template is used with Fluent Mapping=True and Mapping Generation Strategy=UseAttributes options is fixed
• The bug with generating DatabaseGeneratedAttribute for non-EntityKey properties when using attribute mapping (DbContext template) is fixed
• The bug with generating DatabaseGeneratedAttribute for all EntityKey properties when using fluent mapping (DbContext template) is fixed

1.7.326 14-Aug-14

Entity Developer

• The possibility to use relative paths to assemblies in code generation templates is implemented
• The Implement Equals property is added to the DbContext, ObjectContext, and POCO Entity templates
• The bug related to detecting nullable foreign key as non-nullable is fixed

1.7.316 31-Jul-14

• The bug with throwing "Unspecified error" by Migration Wizard when working with Windows Store (WinRT), XNA, Windows Phone, and Silverlight projects is fixed

Entity Developer

• The bug with a format of generated DataAnnotations.RegularExpression for Numeric validate format is fixed
• The bug with displaying Entity Set in the Class Editor dialog is fixed
• The bug with applying changes after editing the list of the extended properties via the Model Settings dialog is fixed
• The bug with adding references to both EntityFramework.dll and System.Data.Entity.dll assemblies simultaneously by Create Model Wizard, when Entity Framework version is set to Entity Framework 6 in the wizard, is fixed

Entity Framework support

• The bug with generating DDL for creating TPH tables, when the value of discriminator is not set, in the Code-First/Code-First Migrations functionality is fixed
• The bug with applying custom HistoryContext settings is fixed

1.7.302 10-Jul-14

Entity Developer

• The View Generation option of the model with Entity Framework version = Entity Framework 6 is supported for the DbContext (only with XML mapping), EntityObject, POCO, and Self-Tracking Entities templates
• The bug with "DevartEntityDeploy" task, when .NET Framework 2.0 and .NET Framework 3.5 are not installed on the target workstation, is fixed

1.7.292 26-Jun-14

Entity Developer

• The bug with storing custom settings in stored procedure mapping is fixed
• The bug with ordering properties in the .HasKey configuration mapping in case of composite primary key is fixed

1.7.282 12-Jun-14

• ADO.NET implementation of ASP.NET Identity 2.0 support is improved
• The new IUserStore<T>, IUserClaimStore<T>, IUserLoginStore<T>, IUserPasswordStore<T>, IUserRoleStore<T>, IUserEmailStore<T>, IUserPhoneNumberStore<T> interfaces are implemented in the DB2UserStore and DB2UserStore<TIdentityUser, TIdentityRole> classes
• The new IRoleStore<T> interface is supported in the DB2RoleStore and DB2RoleStore<TIdentityUser, TIdentityRole> classes

Entity Framework support

• The bug with throwing System.NullReferenceException when disposing an ObjectResult is fixed
• The bug with performing "Generate Database from Model" wizard when working with Entity Framework 6.1.0 Tools for Visual Studio 2012/Visual Studio 2013 is fixed

1.7.272 29-May-14

• The bug with deserialization of a license resource in ASP.NET applications, running with medium or high trust level is fixed

Entity Developer

• The bug related to the opening of the *.edmx files is fixed

Entity Framework support

• The bug with throwing the "Unexpected query batch command" exception when using the Batch Updates functionality is fixed
• The bug with generating extra condition for limiting subselect by one record in generated subqueries with grouping is fixed

1.7.262 15-May-14

• The DB2Script.Cancel() method is added to stop query execution

Entity Developer

• The bug related to performing queries via Query Editor/Retrieve Data when working with the 'Enterprise Library' validation framework is fixed

Entity Framework support

• The behaviour is changed: now a semicolon (;) after the very last statement is generated in the Code-First CreateDatabaseScript() functionality

1.7.247 24-Apr-14

• The ADO.NET implementation of ASP.NET Identity 2.0 support is added
• The new \Web\ASP.NET Identity 2\Devart.Data.DB2.Web.Identity.dll assembly (its revision number is 2) is added to the provider installation folder
• The new \Web\ASP.NET Identity 2\Install_identity_tables.sql and \Web\ASP.NET Identity 2\Uninstall_identity_tables.sql files are added to the provider installation folder
• The new \Web\ASP.NET Identity 2\Upgrade_identity_tables_from_v1_to_v2.sql file is added to the provider installation folder
• The new IUserEmailStore, IUserPhoneNumberStore, IUserTwoFactorStore, IUserLockoutStore interfaces are implemented in the UserStore class
• The bug with 'Load Test Editor' is fixed

Entity Developer

• The behaviour is changed: now a property in the generated code is initialized basing on the default value in CSDL only (instead of default values in any of SSDL and CSDL)
• The bug related to the incorrect value setting for the "Has Stream" property when working with the WCF Data Services projects is fixed

Entity Framework support

• The database server version is added to the generated Code-First Migrations script
• The bug with the explicitly named primary keys in Code-First Migrations, when the primary key is defined via the PrimaryKey() method of the CreateTable() operation, is fixed
• The bug with generating SQL for EntitySQL ANYELEMENT is fixed

1.7.236 10-Apr-14

• The ADO.NET implementation of ASP.NET Identity support is improved
• The ICloneable interface is implemented in the IdentityUser and IdentityRole classes
• The User_Id column in the AspNetUserClaims table is renamed to UserId
• The bug with using parameters when generating commands is fixed

Entity Developer

• The bug related to the models creation when working with DB2 for z/OS is fixed

Entity Framework support

• The UpdateDatabaseOperation operation in Code-First Migrations for Entity Framework 6.x is supported
• The RenameIndexOperation operation in Code-First Migrations for Entity Framework 6.1 is supported
• Multiple EntityContainers in the Code-First CreateDatabase()/CreateDatabaseScript()/DeleteDatabase() functionality are supported
• The Database.Delete(DbConnection) functionality is supported: all objects in the current schema (specified in Current Schema or set with Initialization Command connection string parameter) are removed if DatabaseScript.Schema.DeleteDatabaseBehaviour = AllSchemaObjects
• The Database.Exists(DbConnection) functionality is supported: the method returns true if DatabaseScript.Schema.DeleteDatabaseBehaviour = AllSchemaObjects and at least one table exists in the current schema (specified in Current Schema or set with Initialization Command connection string parameter)
• Determining correct datatypes of data retrieved by EntitySQL queries with UNION ALL and similar constructions is improved
• The compatibility with Hibernating Rhinos EntityFramework Profiler is improved
• The bug with throwing System.NullReferenceException when enumerating an ObjectResult returned by a stored procedure is fixed

1.7.226 27-Mar-14

Entity Developer

• The override modifier for DbSet class properties generated by DbContext templates is added
• The bug with setting nullable type for EnumType property by the Data Transfer Object template is fixed

Entity Framework support

• Entity Framework 6.1.0 RTM is supported
• Entity Framework 6.1.0 Tools for Visual Studio 2012 & 2013 are supported
• The releasing of memory, which was allocated for commands and readers of ObjectContext / DbContext, is improved

1.7.216 06-Mar-14

• The ADO.NET implementation of ASP.NET Identity support is added

Entity Developer

• The information message about availability of NuGet Package Manager on the workstation is added in the Entity Developer version integrated into Visual Studio
• The behaviour is changed: now paths to assemblies with attributes (Model Settings -> Model -> Attributes) are saved and used as relative paths
• The bug with generating the entities namespace in fluent mapping configuration classes is fixed
• The bug with generating DatabaseGeneratedOption.Computed for non-EntityKey properties in fluent mapping is fixed

1.6.204 18-Feb-14

Entity Developer

• More information messages, when validating EF6 models basing on the EntityFramework.dll functionality, are added
• The bug with using Create Model Wizard for EF6 models is fixed

1.6.201 13-Feb-14

Entity Developer

• The "WCF DataMember Attribute on Navigation Properties" property is added to the Data Transfer Object template for pointing the end (-s) where the attribute should be generated
• The behaviour is changed: the validation of EF6 models depends on the EntityFramework.dll functionality only (.NET Framework 4.5 is not required any more)
• The bug related to the "Version string portion was too short or too long" error is fixed
• The bug with parsing inheritances in *.edmx is fixed

Entity Framework support

• The generation of SQL literals for TimeSpan values is improved: shortened form is used now if possible
• The behaviour is changed: Code-First Migrations generates DEFAULT values for new NOT NULL columns of Boolean, DateTime, TimeSpan types when adding them in the existing table
• The bug with generation of SQL literals for TimeSpan values is fixed
• The bug with "Update Model From Database" wizard in Entity Framework 6 Tools for Visual Studio 2012 and Visual Studio 2013 is fixed

1.6.191 30-Jan-14

• Compatible with other dotConnect providers

1.6.181 16-Jan-14

Entity Developer

• The bug with creating models for Entity Framework 6 on the workstation without .NET Framework 4.5 installed is fixed
• The bug with association mapping in the DbContext template is fixed
• The bug with composite keys mapping in the DbContext template is fixed

Entity Framework support

• The bug with changing the MigrationHistory table when migrating from EF4/EF5 to EF6, when config.Workarounds.DisableQuoting = True, is fixed

1.6.166 26-Dec-13

• The bug with retrieving views in Business Intelligence Solutions projects is fixed

Entity Developer

• The bug related to the "Custom tool error: Unknown namespace or alias (NamespaceName.NamespaceName)" error when setting return type of the method to complex type is fixed

1.6.156 12-Dec-13

• Compatible with other dotConnect providers

1.6.146 28-Nov-13

• The bug with disabling some properties in Devart components in Visual Studio Express is fixed
• The bug with calling the RowUpdating event of DB2DataTable and DB2DataAdapter classes when no data is changed is fixed
• The bug with installing provider assemblies for the x64 version of SQL Server Integration Services is fixed

Entity Developer

• The new "Provider Manifest Token" model property is implemented to identify the target server
• The behaviour is changed: the values of "Target Server" and "Server Version" can be reset via the Model Settings > Synchronization > Mapping dialog despite the fact whether connection is specified in Database Explorer or not

Entity Framework support

• The compatibility of Entity Framework provider for EF v1, v4, v5 with medium trust level environment is improved
• The bug related to the NRE on the CreateDatabaseScript() method, when the Code-First model is not configured completely, is fixed

1.6.137 14-Nov-13

• Compatible with other dotConnect providers

1.6.127 31-Oct-13

• Visual Studio 2013 is supported
• The behaviour is changed: installation with the /VERYSILENT install parameter will uninstall the other version of the provider without any dialog box if it is installed
• The bug with using ExtendedMembership provider in a multithreaded application is fixed

Entity Developer

• Entity Framework 6 is supported
• The bug with IntelliSense when working with T4 Editor in Visual Studio 2012 is fixed

Entity Framework support

• The 6.0.0 and 6.0.1 versions of Entity Framework are supported
• The DB2 for Linux/Unix servers are supported in Entity Data Model Wizard and Code-First functionality
• The behaviour is changed: Entity Data Model Wizard shows a more detailed error message in case of connecting to unsupported database or using incorrect provider manifest tokens

1.5.118 17-Oct-13

• Microsoft Sync Framework support is implemented

Entity Developer

• The bug with "DevartEntityDeploy" task, which generates mapping files, in Visual Studio 2013 Release Candidate is fixed

Entity Framework support

• The behaviour is changed: Code-First Migrations generates DEFAULT 0 for new NOT NULL columns of numeric types when adding them in the existing table
• The behaviour is changed: Code-First Migrations generates DEFAULT '' for new NOT NULL columns of string types when adding them in the existing table

1.0.101 23-Sep-13

• Visual Studio 2013 Release Candidate is supported

Entity Developer

• The bug with releasing memory after closing the Retrieve Data window is fixed
• The bug with the Overwrite.Merge template option is fixed
• The bug related to the "Value cannot be null" error when selecting "Regenerate storage and mapping" from the shortcut menu in Model Explorer in Visual Studio is fixed

1.0.90 05-Sep-13

• The bug with an error occurring during opening a connection, and then this connection getting into the pool is fixed
• The bug with the Caption property of the DataGridView column with the Devart DataTable component is fixed

Entity Developer

• The "Rewrite connection string during regeneration" option (default value is True) of model settings is added to provide the possibility to turn off modifying connection string in *.config after model is saved first time
• The design time support for model-defined functions is added
• The "Close the window when the generation completes successfully" option in the Generation Process window is implemented in the standalone Entity Developer
• The behaviour is changed: now connection string is configured with the name of the assembly, where the model is located, in case when the context class is located in another assembly
• The bug with the Retrieve Data functionality of the model with the DbContext template, when its Fluent Mapping property is set to True, is fixed
• The bug related to the detection of Table Per Type inheritances as Table Per Concrete Type inheritances when opening an existing model is fixed
• The bug with availability of the New Blank Template option of the Templates context menu in Model Explorer in the Entity Developer version integrated into Visual Studio is fixed
• The bug with parsing *.edmx is fixed
• The bug with generating "An item with the same key has already been added" error when using DbContext Template is fixed
• The bug with DbContext template, when its MappingGenerationStrategy is set to UseConfigurationClasses, generating fluent mapping for an association with turned off generation of one navigation property is fixed
• The bug with generating invalid code when using MVC View Advanced template is fixed

Entity Framework support

• Entity Framework 6 Release Candidate 1 is supported
• The bug with generating NRE when adding parameter to a command in IDbCommandInterceptor.ReaderExecuting in Entity Framework 6 is fixed

1.0.69 08-Aug-13

• First release of dotConnect for DB2 data provider

 

 

---

© 2013-2024 Devart. All rights reserved.