dotConnect for DB2 4.2

• .NET 9.0 compatibility
• Added support for Visual Studio 2022 version 17.13 Preview

Entity Framework

• Added support for Entity Framework Core 9.0

dotConnect for DB2 4.1

• Added support for .NET 8
• Added support for Visual Studio 2022 version 17.11

Entity Framework

• Added support for Entity Framework Core 8.0.6
• Added support for Entity Framework Core 7.0.20
• Added support for Entity Framework Core 6.0.31

Entity Developer

• Added EF Core 8 to the list of available Entity Framework versions in Create Model Wizard and Model Settings in EF Core Model
• Added .NET 8 to the list of available Target Framework versions in Create Model Wizard and Model Settings in EF and EF Core models

dotConnect for DB2 4.0

• Added support for Visual Studio 2022 version 17.8 Preview
• Added support for .NET Core
• Added support for .NET 5, .NET 6, and .NET 7
• Uploaded the NuGet package 'Devart.Data.DB2' with .NET Core compliant assemblies to www.nuget.org

Entity Framework

• Added support for EF Core 5, EF Core 6, and EF Core 7
• Uploaded the NuGet package 'Devart.Data.DB2.EFCore' with .NET Core compliant assemblies to www.nuget.org

dotConnect for DB2 3.0 new features:

• Windows 11 is supported.
• Visual Studio 2022 version 17.7 Preview is supported

Entity Framework support

• Entity Framework Core 3.1.25 is supported.

Entity Developer:

• The behavior is changed: the primitive properties by default have Inheritance Modifier = None
• 64-bit version of standalone Entity Developer application is added.
• 64-bit version of console Entity Developer application is added.

dotConnect for DB2 2.6 new features:

• Visual Studio 2019 version 16.11 Preview 2.0 is supported
• SQL Server Integration Services 2019 (SSIS 2019) is supported
• Additional mode of parameter substitution in the query in the SSIS Data Flow Source component: substitution as is, without escaping
• The behavior is changed: pool is automatically cleared when AppDomain is being closed
• 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
• 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 new command line option /disablegac that disables adding assemblies to GAC is added

Entity Developer

• Command-line interface is implemented in a standalone Entity Developer

LinqConnect

• 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 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 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
• 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 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 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 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 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
• 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 a stored procedure is requested by Entity Developer when dragging the stored 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 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
• 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 Model Refactoring functionality is supported for classes in EF Core Model
• 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
• The new hotkey Alt+E is implemented in Property Editor for opening Column Editor 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 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 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
• 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 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
• 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
• 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 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 new extended properties Do Not Generate Serializable Attribute and Do Not Serialize are added for complex types in EF Core Model

Entity Framework support

• Entity Framework 6.4.4 is supported
• Entity Framework Core 3.1.1 is supported
• Entity Framework Core 3.1.3 is supported
• Entity Framework Core 3.1.8 is supported
• Entity Framework Core 3.1.9 is supported
• Entity Framework Core 3.1.10 is supported
• Entity Framework Core 3.1.11 is supported
• Entity Framework Core 3.1.12 is supported
• Entity Framework Core 3.1.13 is supported
• Entity Framework Core 3.1.15 is supported
• Entity Framework Core 3.1.16 is supported
• Entity Framework Core 3.1.17 is supported
• Entity Framework Core 3.1.19 is supported
• Entity Framework Core 3.1.20 is supported
• Entity Framework Core 3.1.21 is supported
• Entity Framework Core 3.1.22 is supported
• Entity Framework Core 3.1.32 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
• 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 new metadata to describe autoincremental columns via annotations in EF Core Code-First Migrations are implemented
• 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
• The translation of the DateTime.AddMinutes() method in LINQ query into SQL statement in EF Core is supported
• The DB2Functions class, which allows using DB2-specific functions in LINQ to Entities, is supported in EF Core

dotConnect for DB2 2.5 new features:

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

dotConnect for DB2 2.4 new features:

• Visual Studio 2019 is supported
• Deprecated design-time Synchronous API calls are no longer used with Visual Studio 2019 and Visual Studio 2017
• The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported by Devart DataSet Manager
• The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported by Devart DataSet Editor
• The integration with Visual Studio 2019 is improved: now the installation detects both 2019 Release and 2019 Preview versions

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 "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported
• 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 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 behaviour is changed: a plural form of names ending with "s" now has a longer version (for example, status -> statuses)

Entity Framework support

• Entity Framework Core 2.2.4 is supported
• Entity Framework Core 2.2.6 is supported
• The SQL generation in case of config.QueryOptions.UseCSharpNullComparisonBehavior=true in EF1/EF4/EF5/EF6 is improved

dotConnect for DB2 2.3 new features:

• Visual Studio 2019 Release Candidate 4 is supported

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
• 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 "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
• 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>
• 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 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 multiple select functionality in EF Core Model is improved: now it allows setting PrimaryKey, ValueGenerated, Concurrency for several properties simultaneously

Entity Framework support

• Entity Framework Core 2.1.1 is supported
• Entity Framework Core 2.1.2 is supported
• Entity Framework Core 2.1.3 is supported
• Entity Framework Core 2.1.4 is supported
• Entity Framework Core 2.2.1 is supported
• Entity Framework Core 2.2.3 is supported
• The bit-wise functions OR, AND in EF Core are 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 translation of single-char literal into SQL statement in EF Core 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 misleading "The current provider does not support ambient transactions." warning, generated by TransactionScope in EF Core 2.1, is disabled
• The behavior is changed: the default value of config.QueryOptions.UseCSharpNullComparisonBehavior is true now in EF Core

dotConnect for DB2 2.2 new features:

• Visual Studio 2017 is supported
• 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
• The type of the Offset and Length properties of the ScriptProgressEventArgs class is changed from Int32 to Int64

Entity Developer

• Entity Framework Core 2.0 is supported
• The new Raw SQL Query class property and SQL method property with the corresponding editors are implemented in Entity Framework Core
• The Snake case in both Model and Database naming rules is supported via the new "Add underscore" option
• The Retrieve Data functionality via Model Explorer for EF Core 2 is implemented
• 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
• 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
• Support for ASP.NET Core MVC is added to the Data Annotations Metadata template
• The new SQL Type, Size, Precision, Scale options are added to the Parameters tab in Method Editor of EF Core Model
• 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
• The process of synchronizing methods and parameters with database stored procedures in EF Core Model is improved
• The behaviour is changed: IsRequired(false / true) for navigation properties is always generated in EF Core fluent mapping now

Entity Framework support

• Entity Framework Core 1.1.2 is supported
• Entity Framework Core 1.1.3 is supported
• Entity Framework Core 1.1.4 is supported
• Entity Framework Core 1.1.5 is supported
• Entity Framework Core 2.0 is supported
• Entity Framework Core 2.0.1 is supported
• Entity Framework Core 2.0.2 is supported
• Entity Framework Core 2.0.3 is supported
• Entity Framework 6.2 is supported
• The possibility to use command interception for EF6 commands executed within batch updates is implemented
• 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 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

dotConnect for DB2 2.1 new features:

• Visual Studio 2017 Release Candidate 4 is supported
• 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
• 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

Entity Developer

• Entity Framework Core 1.0 RTM is supported
• The possibility to set values of stored procedure parameters for getting metadata to generate automatically the corresponding complex type is implemented
• The generation of static methods by the EntityObject template is supported via the new property Direct Call of EntityMethod
• 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
• The behaviour is changed: the ObservableCollection navigation properties are initialized now in a default class constructor

Entity Framework support

• Entity Framework Core 1.1.0 is supported
• The DB2ConventionSetBuilder class is implemented in the Entity Framework Core support
• Batch Updates support in EF Core is added
• DB2CSharpMigrationCodeGenerator and DB2VisualBasicMigrationCodeGenerator for code-based migrations are implemented for EF4, EF5, EF6
• The DatabaseFacade.GetDB2Connection() extension method, which returns DB2Connection, is implemented in EF Core
• The new optional parameter Action<DB2DbContextOptionsBuilder> is added to UseDB2() extension method of DbContextOptionsBuilder in EF Core
• The Scaffold-DbContext NuGet command of Package Manager Console for generating a model basing on the existing database schema is supported in EF Core
• The config.DatabaseScript.Schema.DeleteDatabaseBehaviour option is supported in EF Core
• The AddUniqueConstraintOperation and DropUniqueConstraintOperation operations are supported in EF Core Code-First Migrations
• The translation of collection's Contains method in LINQ query to SQL statement in EF Core 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 compatibility with ASP.NET Core Identity is improved
• The behaviour is changed: the errors thrown by executing SQL statement DROP SCHEMA are ignored now

dotConnect for DB2 2.0 new features:

• 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 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
• Entity Framework-related assemblies are renamed
• Upgrade Wizard is improved for upgrading projects with the Entity Framework functionality

dotConnect for DB2 1.8 new features:

• Visual Studio 2015 is supported

Entity Developer

• The Use ObservableCollection property of the DbContext template is implemented

dotConnect for DB2 1.7 new features:

• Visual Studio 2015 Release Candidate is supported

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

• The ICloneable interface is implemented in the IdentityUser and IdentityRole classes
• The User_Id column in the AspNetUserClaims table is renamed to UserId

• 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<TIdentityUser, TKey>, IUserPhoneNumberStore<TIdentityUser, TKey>, IUserTwoFactorStore<TIdentityUser, TKey>, IUserLockoutStore<TIdentityUser, TKey> interfaces are implemented in the UserStore class
• 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
• The new IQueryableUserStore interface is implemented in the UserStore class
• The new IQueryableRoleStore interface is implemented in the RoleStore class
• The DB2Script.Cancel() method is added to stop query execution
• The Enterprise Library 6 support is added; all previous versions of Enterprise Library are no longer maintained
• 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
• The enableExpiredSessionAutoDeletion and expiredSessionAutoDeletionInterval options for deleting expired sessions are added to the session-state store provider definition in the web.config file
• 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
• The behaviour is changed: the DB2Monitor now hides information about the password connection string parameter

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 override modifier for DbSet class properties generated by DbContext templates is added
• 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 Implement Equals property is added to the DbContext, ObjectContext, and POCO Entity templates
• The possibility to use relative paths to assemblies in code generation templates is implemented
• 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 behaviour is changed: now paths to assemblies with attributes (Model Settings -> Model -> Attributes) are saved and used as relative paths
• 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 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 behaviour is changed: now the default values are not set for string properties, that correspond to fields with the default values like expressions

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 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)
• The database server version is added to the generated Code-First Migrations script
• The releasing of memory, which was allocated for commands and readers of ObjectContext / DbContext, is improved
• 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 performance of generating SQL for Enumerable.Contains in LINQ queries is improved by supporting a new expression type, DbInExpression, in Entity Framework 6
• The behaviour is changed: now a semicolon (;) after the very last statement is generated in the Code-First CreateDatabaseScript() functionality

dotConnect for DB2 1.6 new features:

• 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

Entity Developer

• Entity Framework 6 is supported
• The new "Provider Manifest Token" model property is implemented to identify the target server
• 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
• More information messages, when validating EF6 models basing on the EntityFramework.dll functionality, are added
• 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
• 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)

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 compatibility of Entity Framework provider for EF v1, v4, v5 with medium trust level environment is improved
• The generation of SQL literals for TimeSpan values is improved: shortened form is used now if possible
• 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
• 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

dotConnect for DB2 1.5 new features:

• Microsoft Sync Framework support is implemented

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