K7 Total Security 歷史版本列表
更新時間：2024-01-04
更新細節：
What's new in this version:
- Update the VueJS JavaScript library Core to the latest 3.4.5 version (debug and production) for the apps' template. This release of VueJS Core has a lot of changes, fixes and enhancements, so our apps' template.
更新時間：2024-01-03
更新細節：
What's new in this version:
- Update the VueJS JavaScript library Core to the latest 3.4.4 version (debug and production) for the apps' template. This release of VueJS Core has a lot of changes, fixes and enhancements, so our apps' template.
更新時間：2024-01-01
更新細節：
What's new in this version:
- This is a major release of this product and require a new license (or upgrade license) if you purchase it before 01-01-2023. You can purchase a license from our store, and, an upgrade license (if you needed) from your DecSoft customer area, with a 50% off discount. Also from your DecSoft customer area you can get the outdated releases of the product.
- Update the VueJS JavaScript library Core to the latest 3.4.3 version (debug and production) for the apps' template. This release of VueJS Core has a lot of changes, fixes and enhancements, so our apps' template.
- Update the VueJS JavaScript library Core to the latest 3.4.2 version (debug and production) for the apps' template. This release of VueJS Core has a lot of changes, fixes and enhancements, so our apps' template.
- Update the VueJS JavaScript library Core to the latest 3.4.1 version (debug and production) for the apps' template. This release of VueJS Core has a lot of changes, fixes and enhancements, so our apps' template.
- Update the VueJS JavaScript library Core to the latest 3.4.0 version (debug and production) for the apps' template. This release of VueJS Core has a lot of changes, fixes and enhancements, so our apps' template. This is a major release of the VueJS JavaScript library Core, which contains a lot of changes, fixes and enhancements.
更新時間：2023-12-20
更新細節：
What's new in this version:
- Update the VueJS JavaScript library Core to the latest 3.3.13 version (debug and production) for the apps' template. This release of VueJS Core has a lot of changes, fixes and enhancements, so our apps' template.
- Fix a rare bug in the Carousel control when use it in a mobile device in which we shown (in other view) the device keyboard. In this specific case, when go back to the view in which the Carousel control is shown, they don't appear as expected.
更新時間：2023-12-11
更新細節：
What's new in this version:
- Update the VueJS JavaScript library Core to the latest 3.3.11 version (debug and production) for the apps' template. This release of VueJS Core has a lot of changes, fixes and enhancements, so our apps' template.
更新時間：2023-12-06
更新細節：
What's new in this version:
- Update the VueJS JavaScript library Core to the latest 3.3.10 version (debug and production) for the apps' template. This release of VueJS Core has a lot of changes, fixes and enhancements, so our apps' template.
- Replace the "text-davinci-003" model for code generation in the Open AI assistant with the recommended model "gpt-3.5-turbo-instruct". The "text-davinci-003" model has been marked as deprecated and become not available in January 2024.
更新時間：2023-11-27
更新細節：
What's new in this version:
- Update the VueJS JavaScript library Core to the latest 3.3.9 version (debug and production) for the apps' template. This release of VueJS Core has a lot of changes, fixes and enhancements, so our apps' template.
更新時間：2023-11-19
更新細節：
更新時間：2023-11-19
更新細節：
更新時間：2023-11-18
更新細節：
What's new in this version:
dotConnect for PostgreSQL Professional 8.2.0
- PostgreSQL 16 is supported
- Visual Studio 2022 version 17.8 Preview is supported
- The error during installation on the 32-bit version of Windows has been fixed
- The bug with IPv6 host in the connection string is fixed
- The bug with unhandled NullReferenceException is fixed
Entity Framework support:
- Entity Framework Core 7.0.5 is supported
- Entity Framework Core 6.0.16 is supported
- The bug with incorrect SQL translation of reused LINQ query, which includes array.Contains() and other expressions, in EF Core 5/6/7 is fixed
- The bug with throwing Microsoft.EntityFrameworkCore.Infrastructure.ManyServiceProvidersCreatedWarning by the UsePostgreSql(DbConnection connection) extension method of DbContextOptionsBuilder in EF Core 6 and EF Core 7 is fixed
- The bug with using custom converters in mapping in EF Core 3 and higher is fixed
Entity Developer:
- The bug with detecting the numeric default value of string columns as function-based column default value in EF Core Model is fixed
dotConnect for PostgreSQL Professional 8.1.151
- Visual Studio 2022 version 17.7 Preview is supported
- The bug with throwing the "Unexpected server response" error when executing INSERT into a non-existing table is fixed
- The bug in DataSet designer is fixed
Entity Framework support:
- Entity Framework Core 7.0.5 is supported
- Entity Framework Core 6.0.16 is supported
- The bug with incorrect SQL translation of reused LINQ query, which includes array.Contains() and other expressions, in EF Core 5/6/7 is fixed
Entity Developer:
- The behavior is changed: the primitive properties by default have Inheritance Modifier = None
- The bug with the detection of non-existent changes while updating a model from a database is fixed
- The bug with creating Devart Entity Model in Visual Studio 2022 is fixed
- The bug with missing model context namespace in EntityFrameworkUnitOfWork.cs produced by the Repository And Unit of Work template (C#) in EF Core is fixed
- The bug with generating incorrect scale in mapping for decimal columns by the EF Core template (Visual Basic) in EF Core 5 and higher is fixed
dotConnect for PostgreSQL Professional 8.1.134
- Visual Studio 2022 version 17.5 Preview is supported
- .NET 7 compatibility
- PostgreSQL 15 is supported
- The сonnection to PostgreSQL 12 and higher via SSH using SHA-256/512 algorithms is supported
- Bug with processing PgSQL block in within SQL script is fixed
- Bug with processing numeric field type is fixed
- Bug with processing inet[] field type is fixed
- Bug with processing BIT field type to BitArray is fixed
Entity Framework support:
- Entity Framework Core 7.0.2 is supported
- Entity Framework Core 6.0.13 is supported
- Entity Framework Core 3.1.32 is supported
- The bug with missing the CREATE TABLE statement for __EFMigrationsHistory in EF Core 5 and EF Core 6 Migrations is fixed
Entity Developer:
- The new extended properties Do Not Generate Serializable Attribute and Do Not Serialize are added for complex types in EF Core Model
- The bug with applying the Generate Serializable Attributes and Serialization Library settings of the EF Core template to the generated complex types is fixed
dotConnect for PostgreSQL Professional 8.0.0
- NET 6 compatibility
- macOS 11 Arm64 (or "Apple Silicon" or "Apple M1") support
- Windows 11 is supported
- Visual Studio 2022 version 17.2 is supported
- Visual Studio 2022 version 17.3 Preview is supported
- The incorrect dump of sequence value is fixed
- The bug with IPv6 host in the connection string is fixed.The bug when mapping PostgreSQL inet and macaddr types in Entity Framework Core Model is fixed.
Entity framework:
- Entity Framework Core 6.0.5 is supported
- Entity Framework Core 5.0.17 is supported
- Entity Framework Core 3.1.25 is supported
Entity Developer:
- 64-bit version of standalone Entity Developer application is added
- 64-bit version of console Entity Developer application is added
dotConnect for PostgreSQL Professional 7.24.2066
- The KeepConnected connection string parameter is implemented to determine the number of seconds of connection inactivity before the client sends a ping request
- The Load Balancing support is implemented: now several hosts with their ports can be specified in the Host parameter of the connection string
- The Target Session connection string parameter is added for managing Load Balancing functionality, possible values are SuppressLoadBalancing, Any, PreferStandby, PreferPrimary, Primary, Standby
- The TargetSession property is added to the PgSqlCommand class to provide the possibility to overwrite the behavior of the same option set in the connection object
Entity Developer:
- The bug when mapping PostgreSQL inet and macaddr types in Entity Framework Core Model is fixed
- The behavior is changed: turning off the "Save connection to" option in Model Settings of EF Core Model wipes out connection string literal from the generated code
- The behavior is changed: Devart.Data.MySql.Entity.EF5.dll compiled with .NET Framework 4.7 is used now in EF5 models
Entity Framework support:
- The new EntityEF5net47Devart.Data.PostgreSql.Entity.EF5.dll assembly compiled with .NET Framework 4.7 is added
- The new EntityEF5net47Devart.Data.PostgreSql.Entity.Migrations.EF5.dll assembly compiled with .NET Framework 4.7 is added
- The new EntityEF5net47Devart.Data.PostgreSql.Entity.Spatials.EF5.dll assembly compiled with .NET Framework 4.7 is added
- 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
- The bug with throwing the "schema does not exist" error by Database.EnsureDeleted() in EF Core is fixed
- The bug with saving and reading string value NULL to/from HSTORE data type in PostgreSQL mapped to Dictionary<string, string> or ImmutableDictionary<string, string> or SortedDictionary<string, string> or ImmutableSortedDictionary<string, string> in EF Core 3, EF Core 5, EF Core 6 is fixed
dotConnect for PostgreSQL Professional 7.23.2042
- The bug with reading SSL certificates from MemCryptStorage is fixed
Entity Developer:
- The model validation is improved: the errors are generated for all entities with QueryType=True in EF Core Model when EF Core version=EF Core 1 in Model Settings
- The bug with wrong automatic assigning QueryType=True for views added to EF Core Model, when EF Core version=EF Core 1 in Model Settings, is fixed
- The bug with throwing System.NullReferenceException when saving the changed value of the "Save connection to" option in Model Settings of EF Core Model is fixed
Entity Framework support:
- Entity Framework Core 6.0.1 is supported
- Entity Framework Core 5.0.13 is supported
- Entity Framework Core 3.1.22 is supported
- The config.SpatialOptions settings are supported in EF Core
- NetTopologySuite 2.4.0 is supported in EF Core 3, EF Core 5, and EF Core 6
- The bug with throwing the "Expression in SQL tree does not have type mapping assigned" error with NetTopologySuite in EF Core is fixed
- The bug with generating the "Value cannot be null" error when adding or dropping FK via Code-First Migrations in EF Core is fixed
dotConnect for PostgreSQL Professional 7.22.2014
The new features of PostgreSQL Server 14 are supported:
- multirange data types
the database types int4multirange, int8multirange, nummultirange, datemultirange, tsmultirange, - tstzmultirange can be used with the provider now
the new members IntMultirange, BigIntMultirange, NumericMultirange, TimeStampMultirange, - TimeStampTZMultirange, DateMultirange are added to the PgSqlType enum
PgSqlReader.GetProviderSpecificValue returns provider-specific range types: PgSqlIntRange[] for int4multirange, PgSqlBigIntRange[] for int8multirange, PgSqlNumericRange[] for nummultirange, PgSqlTimeStampRange[] for datemultirange, PgSqlTimeStampTZRange[] for tsmultirange, - PgSqlDateRange[] for tstzmultirange
NaN, Infinity, -Infinity values of numeric data types generate a NotSupportedException to avoid - inconsistency
- OUT parameters of stored procedures
- The start value and the current value of the sequence are saved correctly by PgSqlDump
Entity Developer:
- The bug with parsing discriminator value as string, even when its type is different, in TPH inheritance of EF Core Model is fixed
Entity Framework support:
- Entity Framework Core 5.0.12 is supported
- Entity Framework Core 3.1.21 is supported
dotConnect for PostgreSQL Professional 7.21.2001
- Visual Studio 2019 Preview support is discontinued
- The bug with throwing Devart.Common.LicenseException, when Devart.Data.PostgreSql.dll is embedded into a single file application, is fixed
- The bug with applying .NET Standard licensing to .NET 6 projects is fixed
Entity Developer:
- The bug with launching Entity Developer after applying Windows 10 Update KB5006670 and Windows 11 Update KB5006674 is fixed
LinqConnect (formerly known as LINQ to PostgreSQL):
- The bug with parsing TypeName values in XML mapping generated by Visual Basic template is fixed
Entity Framework support:
- Entity Framework Core 5.0.11 is supported
- Entity Framework Core 3.1.20 is supported
- The implementation of config.CodeFirstOptions.TruncateLongDefaultNames in EF6 .NET Standard compliant assemblies is improved: the generated names are constant, independent on a current domain and workstation
- The bug with using DateTime.Today, DateTime.Now, DateTime.UtcNow, DateTimeOffset.Now within LINQ query in EF Core 5 is fixed
dotConnect for PostgreSQL Professional 7.21.1985
Entity Developer:
- The new property Validation Framework is implemented in the Data Transfer Object template for generating DataAnnotations attributes
- The Uri data type is supported in EF Core Model
- 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 with code generation for the Constrained option of Association Editor in the case of 0..1 -> 1 association in EF Core Model is fixed
- The bug throwing "Unknown property 'DoNotSerialize'.", when complex types and VB.NET template are used in EF Core Model, is fixed
Entity Framework support:
- Entity Framework Core 5.0.10 is supported
- Entity Framework Core 3.1.19 is supported
The SQL translation of the following class members used in LINQ query is supported in EF
Core 3 and EF Core 5:
- static method IsNullOrWhiteSpace() of the String class
- static property Today and instance properties DayOfWeek, Ticks of the DateTime class
- static methods Max(), Min(), Sqrt(), Log(), Log10(), Sin(), Cos(), Tan(), Asin(), Acos(), Atan() of the Math class
The SQL translation of the following class members used in LINQ query is supported in EF Core 5:
- static method Parse() of the System.Net.IPAddress class
- static method Parse() of the System.Net.NetworkInformation.PhysicalAddress class
- static methods Abs(), Round(), Truncate(), Floor(), Ceiling(), Max(), Min(), Pow(), Sqrt(), Log(), Log10(), Sin(), Cos(), Tan(), Asin(), Acos(), Atan() of the MathF class
- Mapping of System.Decimal to PostgreSQL DECIMAL with specified precision and scale in EF Core 5 is supported
- Mapping of the PostgreSQL HSTORE data type to Dictionary, SortedDictionary, ImmutableDictionary, ImmutableSortedDictionary is supported in EF Core 3 and EF Core 5
- The HasFilter extension on IndexBuilder in EF Core Migrations is supported in EF Core 3 and EF Core 5
- Mapping of internet/intranet data type System.Uri to PostgreSQL TEXT is supported in EF Core 3 and EF Core 5
- Mapping of network data types System.Net.IPAddress and System.Net.NetworkInformation.PhysicalAddress to PostgreSQL INET and MACADDR/MACADDR8 is supported in EF Core 5
- The definition of System.ICloneable is removed from .NET Framework assembly EntityEFCore3Devart.Data.PostgreSql.Entity.EFCore.dll
dotConnect for PostgreSQL Professional 7.20.1944
LinqConnect (formerly known as LINQ to PostgreSQL):
- The new methods IsNotDistinctFrom() and IsDistinctFrom() are added to the Devart.Data.Linq.SqlMethods class
Entity Framework support:
- Entity Framework Core 5.0.8 is supported
- Entity Framework Core 3.1.17 is supported
dotConnect for PostgreSQL Professional 7.20.1930
- Visual Studio 2019 version 16.11 Preview 2.0 is supported
- The "WITH OIDS" clause was excluded from dump results for PostgreSQL version 12 and higher
- The bug with converting the timestamp with time zone value to DateTimeOffset by PgSqlDataReader is fixed
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
- The bug with updating TIMESTAMP WITH TIME ZONE, BOOLEAN, DOUBLE PRECISION, NUMERIC, CHARACTER(1) columns via Update To Database Wizard is fixed
Entity Framework support:
- Entity Framework Core 5.0.7 is supported
- Entity Framework Core 3.1.16 is supported
- The bug with comparing enum values in EF Core 3 and EF Core 5 is fixed
- The bug with .Contains and .Length in EF Core 3 and EF Core 5, when using NetTopologySuite spatial functionality, is fixed
dotConnect for PostgreSQL Professional 7.20.1905
- The bug with the "Failed to merge object(s). Object reference not set to an instance of an object…" error during create DataSet with View objects is fixed
Entity Developer:
- The new extended property Use Generic DbContextOptions Constructor Argument is added to model properties of EF Core Model
- The new extended property Do Not Generate Constructor With DbContextOptions Argument is added to model properties of EF Core Model
- The bug with generating the Equals method for entities with Record Type=True by C# EF Core template is fixed
- The bug with cleaning values of Length and Precision/Scale column's attributes by Update From Database Wizard in EF Core Model is fixed
- The bug with ignoring template's Validation Error Messages values in the generated code, when class property's Validate Expression is initialized and Validate Format is set to a non-default value, is fixed
- The bug with creating app.config in Visual Studio .NET Framework projects, when the "Rewrite connection string during regeneration" option is turned off in Model Settings, is fixed
Entity Framework support:
- Entity Framework Core 5.0.6 is supported
- Entity Framework Core 3.1.15 is supported
- The EF6 provider registration used with .NET Framework compliant assemblies is improved: the [DbConfigurationType(typeof(PgSqlEntityProviderServicesConfiguration))] attribute set for DbContext descendant allows now calling the DbContext constructor, that accepts a connection string, with no need to register a custom IDbConnectionFactory implementation
- The bug with connection recovery after the initial connection attempt failure in EF Core is fixed
dotConnect for PostgreSQL Professional 7.20.1866
Entity Developer:
- The new hotkey Alt+E is implemented in Property Editor for opening Column Editor in EF Core Model
- The bug with throwing "bufferAdapter is not a VsTextDocData" when saving a model in .NET Core, .NET Standard, .NET 5, .NET 6 projects of Visual Studio 2019 is fixed
- The bug with missing .NET Framework, .NET Core 1, .NET Core 2 options for the Target Framework property in Model Settings of EF Core Model in a standalone Entity Developer is fixed
- The bug with preserving Target Framework=.NET Framework in Model Settings of EF Core Model in a standalone Entity Developer is fixed
dotConnect for PostgreSQL Professional 7.20.1812
- The bug with blocking thread during retrieving a connection from the pool, when connections from the same pool are used in several threads, is fixed
- The bug with inserting JSONB value via a parameter of PgSqlCommand is fixed
dotConnect for PostgreSQL Professional 7.20.1792
Entity Framework support:
- Entity Framework Core 5.0.1 is supported
- The bug with creating savepoints in EF Core 5 is fixed
dotConnect for PostgreSQL Professional 7.20.1782
- Visual Studio 2019 version 16.9 Preview is supported
- The bug with loading data into the JSONB column via PgSqlLoader in the PgSqlLoaderMode.Binary mode is fixed
- The bug with updating projects that reference EF6 provider assembly via Upgrade Wizard is fixed
Entity Developer:
The new features are supported in Entity Framework 5.0:
- TPT inheritance
- Many-to-many associations
- The new types of properties IPAddress and PhysicalAddress
- The Model Refactoring functionality is supported for classes in EF Core Model
- The behavior is changed in a standalone Entity Developer: by default the Target Framework model property in EF Core Model is set to .NET 5 instead of .NET Framework
- The bug with saving non-default value of Target Framework model property in EF6 model modified with a standalone Entity Developer is fixed
- The bug with adding new arguments at the end of argument list instead of actual position in method signature by Update From Database Wizard is fixed
Entity Framework support:
- Entity Framework Core 5.0 is supported
- Entity Framework Core 3.1.10 is supported
- The behavior is changed: EF Core 3 assemblies available via NuGet package are compiled for .NET Standard 2.0 instead of .NET Standard 2.1
- The behavior is changed: EF Core 2 assemblies are no longer available via NuGet package but created in the provider installation folder
- The bug with using another context's connection in DbContextOptionsBuilder.UsePostgreSql(connection) in EF Core is fixed
dotConnect for PostgreSQL Professional 7.19.1759
- PostgreSQL 13 is supported
- The behavior is changed: metadata returned by the GetSchema("Tables") and GetSchema("Columns") methods of PgSqlConnection are supplemented now with the list of Foreign tables and columns correspondingly
- The bug with Visual Studio 2019 integration, when both v16.7 RTM and v16.8 Preview are installed on the same computer, is fixed
- The bug with missing Name and Owner properties of the PgSqlConnection class in .NET Standard compliant assemblies is fixed
Entity Developer:
- The bug with reading templates from *.edps by console Entity Developer is fixed
Entity Framework support:
- Entity Framework Core 3.1.9 is supported
- The bug with detecting FK relationship by the Scaffold-DbContext functionality in EF Core 3 is fixed
dotConnect for PostgreSQL Professional 7.18.1739
- Visual Studio 2019 version 16.8 Preview is supported
Entity Developer:
- EF Core 3 spatial data types support is improved: in addition to Geometry and Geography, specific .NET NetTopologySuite types like GeographyPoint, GeographyLine are now available property types
- The 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
dotConnect for PostgreSQL Professional 7.18.1730
- The SendCallStack property is added to the Devart.Common.DbMonitor class for possibility to turn off resource-demanding logging of CallStack
- The Filter property is added to the Devart.Common.DbMonitor class for possibility to choose events being logged
- The Devart.Common.DbMonitor class is improved: now values of the DateTime parameters sent to the dbMonitor tool are supplemented with milliseconds
- The bug with updating projects in folders below the main project by Upgrade Wizard is fixed
- The bug with connecting via Amazon RDS Proxy is fixed
Entity Developer:
- The error message in console Entity Developer is improved: now the text includes the list of all available templates if the specified name of template was incorrect
- The bug with saving a new model, which has never been saved before, after some time of work in a standalone Entity Developer is fixed
- The bug with generating mapping for the properties with Shadow=True in EF Core Model is fixed
- The bug with using spatial types inside complex types in EF Core Model is fixed
Entity Framework support:
- Support for spatial data types in EF Core 3 is implemented
- Entity Framework Core 3.1.8 is supported
- The new NuGet package Devart.Data.PostgreSql.EFCore.NetTopolosySuite with a .NET Standard 2.1 assembly, that is compatible with .NET Core 3, is added
- The new EntityEFCore3Devart.Data.PostgreSql.Entity.EFCore.NetTopolosySuite.dll assembly compiled with EF Core 3.1 and .NET Framework 4.6.1 is added
- The PgSqlFunctions class, which allows using PostgreSQL-specific functions in LINQ to Entities, is supported in EF Core
- The PgSqlTextFunctions class, which allows using PostgreSQL full-text search functionality in LINQ to Entities, is supported in EF Core
dotConnect for PostgreSQL Professional 7.17.1696
- The bug with throwing System.NullReferenceException when opening *.edmx with invalid associations is fixed
dotConnect for PostgreSQL Professional 7.17.1686
- The behavior is changed: ReadOnly=true is no longer set for all columns in PgSqlDataTable.Columns when the query joins several tables
Entity Developer:
- The bug with detecting FK relationships to tables in other schemas by Create Model Wizard and Update From Database Wizard is fixed
- LinqConnect (formerly known as LINQ to PostgreSQL)
- The overload of Compare() method, that accepts StringComparison as an argument, is supported
- The "Could not find element type in model" bug when loading XML mapping in .NET Standard LinqConnect assemblies is fixed
- The bug with using enums via .NET Standard compliant assemblies is fixed
Entity Framework support:
- The bug with incorrect SQL generation when using .Substring() in a .Select() statement in EF Core 2 is fixed
dotConnect for PostgreSQL Professional 7.17.1666
- Visual Studio 2019 version 16.7 Preview is supported
Entity Developer:
- .NET 5 is added to the list of available Target Framework versions in Create Model Wizard and Model Settings in EF6, EF Core, LinqConnect models
- The new option "Execute procedures for result set detection" is added to Model Settings of EF Core Model to control obtaining metadata of a procedure or function result set
- The new option "Use NULL parameter values" is added to Model Settings of EF Core Model to specify whether NULL parameter values are used for stored procedure execution
- The new option "Add complex types to diagram" is added to Model Settings of EF Core Model to control behavior of Create Model Wizard and Update Model From Database Wizard
- The new option "Add new complex types to the current diagram" is added to Update Model From Database Wizard of EF Core Model
- The new Primitive Default Value Generation property is added to EF, EF Core templates to determine whether to generate initialization for a primitive property based on database DEFAULT column value
- The new property Collection Property Type is added to EF template "DbContext" and EF Core template "EF Core" to determine .NET type used as a property type for the Many end of associations
- The new property Collection Initialization Type is added to EF template "DbContext" and EF Core template "EF Core" to determine .NET type used for initialization of the Many end of association; if it is set to None, then no initialization is generated
- The new property "Nullable Reference Types" is added to C# templates of EF, EF Core models to specify whether C# 8 nullable reference types and non-nullable reference types must be generated
- The new partial method is added to the OnModelCreating(DbModelBuilder modelBuilder) method generated by DbContext template of EF model
- The EF Core model deserialization is improved: Entity Developer shows the full list of detected errors and tries to load the model with invalid elements or ignores such elements if their deserialization is not possible
Console Entity Developer improvements:
- Import of stored procedures and functions via Create-Model command is supported
- The new options --Procedures and --Functions are added to Create-Model command for filtering stored procedures and functions; by default all procedures/functions are imported
- The new option --Execute is added to Create-Model command for executing procedures/functions to get metadata from result set
- The asterisk symbol (*) is supported in --Tables and --Views parameters of Create-Model to include all objects
- The bug with opening connection via some supported providers is fixed
- The bug with enumerating values separated with comma and without whitespace in --Templates, --Schemas, --Tables parameters is fixed
- The list of keywords and reserved words of PostgreSQL being quoted by Entity Developer is updated
- The DbProviderFactories registration is implemented in Create Model Wizard for EF6 models and .NET Framework provider assemblies
- The new property Target Framework is added to Create Model Wizard and Model Settings of EF6 models
- The compatibility issue with JetBrains ReSharper is fixed
- The behavior is changed: the definition of auto-implemented property is put now on the single line with
- C# DbContext template of Devart Entity Model when ImplementINotifyPropertyChanging=False and ImplementINotifyPropertyChanged=False and PropertyChangePartialMethods=False
- C# EF Core template of Devart EF Core Model when PropertyChangeNotifiers=False and PropertyChangePartialMethods=False
- The behavior for the new EF, EF Core models is changed: Primitive Default Value Generation is set to Literal now instead of LiteralOrExpression
- The behavior is changed: the names of system types are generated without "System." prefix now in EF Core models; for example, it is DateTime instead of System.DateTime
- The behavior is changed: only one confirmation for executing stored procedure is requested by Entity Developer when drag&drop-ing procedure from Database Explorer to Model Explorer or diagram surface
- The behavior is changed: now the EF Core template generates an additional partial class for the context class when "File Per Class" and "Generate Partial Class" are set to True
- The bug with detecting strings, being expressions, as string literals when generating initialization of string properties basing on database columns' default values in EF, EF Core models is fixed
- The bug with detecting numbers, being quoted string literals, as strings when generating initialization of numeric properties basing on database columns' default values in EF, EF Core models is fixed
- The bug with missing default value in the generated code basing on DEFAULT value in a database, when any of ImplementINotifyPropertyChanging, ImplementINotifyPropertyChanged, PropertyChangePartialMethods options of DbContext template in EF is turned on, is fixed
- The bug with code generation for zero-or-one to zero-or-one association in the EF6 model with the DbContext template (Fluent Mapping=True) is fixed
- The bug with generating .HasMany end of one-to-many association in EF Core Model is fixed
- The bug with generating TPH mapping in EF Core 3 model is fixed
- The bug with false appearing the "Table or view '...' has no primary key columns, and the entity key for the corresponding storage entity was calculated automatically from other fields." warning in the Error List window is fixed
- The bug with generating new Guid() with Primitive Default Value Generation=Literal in EF, EF Core models is fixed
LinqConnect (formerly known as LINQ to PostgreSQL):
- The overloads of Contains(), StartsWith(), EndsWith(), IndexOf(), Equals() methods, that accept StringComparison as an argument, are supported
- The bug with materializing elements, the types of which are explicitly converted from non-nullable to nullable on the client side, is fixed
- The bug with incorrect detection of altered column comment in a many-to-many association join table by Update From Database Wizard is fixed
Entity Framework support:
- Entity Framework 6.4.4 is supported
- The translation of the DateTime.AddMinutes() method in LINQ query into SQL statement in EF Core is supported
- The EF6 provider registration used with .NET Standard compliant assemblies is improved: the [DbConfigurationType(typeof(PgSqlEntityProviderServicesConfiguration))] attribute set for DbContext descendant allows now calling the DbContext constructor, that accepts a connection string, with no need to register a custom IDbConnectionFactory implementation
- The bug with adding / subtracting DateTime and TimeSpan, DateTimeOffset and TimeSpan values in LINQ query in EF Core 3 is fixed
- The bug with SQL generation in EF Core 3, when enum values are used in CASE and COALESCE statements, is fixed
dotConnect for PostgreSQL Professional 7.17.1612
- The bug with setting multiple comma-delimited schemas via the Schema connection string parameter is fixed
- The bug with passing the PgSqlArray object with RAW element type as a parameter value is fixed
LinqConnect (formerly known as LINQ to PostgreSQL):
- The insert of the object, the type of which is an unmapped class inherited from a mapped class, is supported
- The bug with throwing System.NullReferenceException, when constructing the error saying that unmapped class is not supported, is fixed
Entity Developer:
- Command-line interface is implemented in a standalone Entity Developer
- The new property Context Name is added to Model Properties in EF Core Model
- The new property Target Framework is added to Model Properties in EF Core Model
- The provider registration is improved: requirement to put provider registration entry in the config file is not obligatory anymore
- Create Model Wizard is improved: now it allows installing multiple NuGet packages on the final step
- Model file tree in .NET Core / .NET Standard projects is improved: all generated code files and model files are nested under the same node in Solution Explorer
Entity Framework support:
- Entity Framework Core 3.1.3 is supported
- The .ToString() call for numbers, DateTime/DateTimeOffset properties and values in LINQ queries in EF Core is supported
- The call of Convert.ToString(value) in LINQ queries in EF Core is supported
dotConnect for PostgreSQL Professional 7.17.1583
- SQL Server Integration Services 2019 (SSIS 2019) is supported
- The PgSqlDataTable and PgSqlDataSet classes are supported in .NET Standard 2.0
- The behavior is changed: pool is automatically cleared when AppDomain is being closed
- The bug with initializing NHibernate configuration on .NET Standard 2.0 is fixed
Entity Developer:
- The bug with returning multiple result sets in code generated by the EF Core template is fixed
- The bug with detecting MySQL computed columns is fixed
Entity Framework support:
- Entity Framework Core 3.1.1 is supported
- The bug with using nullable enum properties with default mapping to integers in LINQ query in EF Core 3.1 is fixed
- The bug with using value converters detected automatically by .HasConversion() in EF Core 3 is fixed
- The bug with using NULL constant values in EF Core 3 is fixed
- The bug with using binary operators AND, OR in EF Core 3 is fixed
dotConnect for PostgreSQL Professional 7.16.1541
- Visual Studio 2019 version 16.5 Preview is supported
- The bug with using Toolbox component PgSqlDataSource 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
LinqConnect (formerly known as LINQ to PostgreSQL):
- The bug with using Toolbox component DbLinqDataSource in web projects of Visual Studio 2013, 2015, 2017, 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 EntityEFCore3Devart.Data.Oracle.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
- The bug with throwing the "Null TypeMapping in Sql Tree" error by methods in LINQ query in EF Core 3 is fixed
dotConnect for PostgreSQL Professional 7.15.1519
- The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported by Devart DataSet Editor
- The bug with using PgSqlArray of the Varchar type as a command parameter, when connection string includes "UnpreparedExecute=True;", is fixed
Entity Developer:
- The Self-Contained Entity Configuration property is added to VB.NET version of EF Core template
- The Entities Configuration Output property is added to VB.NET version of EF Core template
- The code generation for the class properties with Alternate Key=True by VB.NET version of EF Core template is supported in EF Core model
- The bug with code generation, when Raw SQL Query is initialized in class properties, in EF Core 3 model is fixed
- The bug with generating .HasNoKey(), when Self-Contained Entity Configuration is set to True in properties of EF Core template, in EF Core 3 model is fixed
- The bug with generating alternate keys, when Self-Contained Entity Configuration is set to True in C# version of EF Core template, in EF Core model is fixed
Entity Framework support:
- The SQL generation in case of config.QueryOptions.UseCSharpNullComparisonBehavior=true in EF1/EF4/EF5/EF6 is improved
- The bug with using Scaffold-DbContext in EF Core 3 is fixed
- The bug with the redundant empty ORDER BY clause in a subquery, when paging is used, in EF Core 3 is fixed
- The bug with using .Contains within .Select of LINQ query in EF Core 2 is fixed
- The bug with generating invalid SQL when calling members of owned type in EF Core 2 is fixed
dotConnect for PostgreSQL Professional 7.15.1504
- Visual Studio 2019 version 16.4 Preview is supported
Entity Developer:
- The DbContext template is improved: precision and scale for database types are generated now in EF4/EF5/EF6 models when Fluent Mapping=True and Mapping Generation Strategy=UseAttributes
- The bug with throwing the EntityFrameworkCoreVersion error in Create Model Wizard in a standalone Entity Developer is fixed
Entity Framework support:
- Entity Framework Core 2.2.6 is supported
- The bug with optimistic concurrency implementation in EF Core is fixed
dotConnect for PostgreSQL Professional 7.15.1499
- PostgreSQL 12 is supported
- The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported by Devart DataSet Manager
- The bug with inserting data into GEOMETRY columns is fixed
- The bug with updating TEXT columns in UTF8 databases is fixed
Entity Developer:
The DbContext template is improved for using Entity Framework 6.3:
- The "Configuration Type Name" property, which specifies the descendant of DbConfiguration class that should be used for code-based configuration, is added
- The "Use DbConfigurationType Attribute" property, which determines whether to register the configuration type specified in the ConfigurationTypeName property of the DbConfigurationType attribute, is added
- The DbProviderFactories.RegisterFactory method is generated when UseDbConfigurationTypeAttribute=true and ConfigurationTypeName='%Default%'
- With UseDbConfigurationTypeAttribute=false, the static constructor for registering factory and the new partial method OnStaticConfigured are generated
- The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported
- The compatibility issue with JetBrains ReSharper is fixed
Entity Framework support:
- Entity Framework Core 3.0 is supported
- Entity Framework 6.3 is supported
- The lock for Microsoft.EntityFrameworkCore dependency is added to the NuGet package Devart.Data.PostgreSql.EFCore
- The bug with invoking DbFunctions with the DateTime and DateTimeOffset parameters is fixed
dotConnect for PostgreSQL Professional 7.14.1470
- The integration with Visual Studio 2019 is improved: now the installation detects both 2019 Release and 2019 Preview versions
- The bug with throwing System.NullReferenceException instead of actual error in Workflow Foundation is fixed
Entity Developer:
- Entity Framework 6.3 Preview 9 is supported for projects with target framework .NET Core 3 or .NET Standard 2.1
- The behaviour is changed: a plural form of names ending with "s" now has a longer version (for example, status -> statuses)
- The bug with applying the new Foreign Key's Delete Rule values SET DEFAULT and SET NULL by the Update Database From Model and Update Model From Database wizards is fixed (Entity Framework)
- The bug with copying a property with Primary Key=True / Entity Key=True to a complex type is fixed (Entity Framework)
- The bug with naming of a composing unique key by Create Model Wizard / Update From Database Wizard in EF Core is fixed (Entity Framework)
- The bug with invalid attempt to cast unsupported Visual Studio project to type 'VSLangProj.VSProject' is fixed
Entity Framework support:
- Entity Framework 6.3 Preview 9 is supported
- A new NuGet package Devart.Data.PostgreSql.EF6 with a .NET Standard 2.1 assembly, compatible with .NET Core 3, is added
- The bug with using the same database connection in several EF Core contexts is fixed
- The bug with applying a value converter to .Where expression with .Contains on nullable enum in EF Core 2 is fixed
- The bug with casting the DateTimeOffset value passed to a function as an argument in EF6 is fixed
dotConnect for PostgreSQL Professional 7.13.1437
Entity Framework support:
- The bug with applying a value converter to a nullable column in EF Core 2 is fixed
- The bug with applying config.QueryOptions.ComparisonCollation to the update statements in EF6 is fixed
dotConnect for PostgreSQL Professional 7.13.1422
- The bug with throwing "Operation is not supported" by web providers, when the cookie is used, is fixed
Entity Developer:
- The ability to disable generation of the byte order mark (BOM) in the beginning of code files in a standalone Entity Developer is implemented
- The bug with design time copy/cut/paste functionality for entities is fixed
- The bug with invalid integer to enum conversion by a generated method, which is based on SQL query and returns a collection of entities, in EF Core 2 is fixed
Entity Framework support:
- The bug with applying a filter to the nullable property with implicit EnumToStringConverter via LINQ queries in EF Core 2 is fixed
- The bug with missing brackets around SELECT inside the generated CASE statement in EF Core 2 is fixed
- The bug with nullable parameters in EF Core 2 is fixed
- The bug with reopening connections in EF Core 2 is fixed
dotConnect for PostgreSQL Professional 7.13.1402
- Deprecated design-time Synchronous API calls are no longer used with Visual Studio 2019 and Visual Studio 2017
- The behaviour is changed: now PgSqlDataAdapter performs inserts in a batch with protocol 3 when the UpdateBatchSize property is used and UnpreparedExecute is true for InsertCommand
- The bug with missing schema name in a function return type when the function is backed up via PgSqlDump.Backup is fixed
- The bug with creating foreign key constraints before primary key constraints in a PgSqlDump.Backup result script is fixed
- The bug with adding timestamp(6) instead of timestamp to a PgSqlDump.Backup result script is fixed
- The bug with connecting to a PostgreSQL server on Google Cloud Platform is fixed
LinqConnect (formerly known as LINQ to PostgreSQL):
- The bug with running stored procedure in PostgreSQL Server 11 or higher is fixed
- The bug with executing incorrect SQL request (cached during one of the previous calls), when a variable initialized with an empty collection participates in LINQ query, is fixed
Entity Framework support:
- Entity Framework Core 2.2.4 is supported
- The bug with closing database connection by context.Dispose() in the scope of a distributed transaction in EF Core 2 is fixed
- The bug with using a value converter, when the .NET data type remains the same, within the WHERE clause in EF Core 2 is fixed
dotConnect for PostgreSQL Professional 7.13.1366
- Visual Studio 2019 is supported
- Entity Developer: the bug with processing DBNull returned by the function in EF Core is fixed
- Entity Framework support: the bug with using the "Generate Database from Model" wizard when working with Entity Framework 6 Tools is fixed
dotConnect for PostgreSQL Professional 7.12.1357
- Visual Studio 2019 Release Candidate 4 is supported
- The bug with corrupting not Latin-1 characters by Migration Wizard for files with non-unicode encoding is fixed
Entity Framework support
- Entity Framework Core 2.2.3 is supported
- The translation of DateTimeOffset literal into SQL statement is supported
- The SQL translation of the following method overloads, that accept the StringComparison argument and return bool, in the System.String class is supported in EF Core 2: Contains, StartsWith, EndsWith, Equals
- The bug with removing an empty __EFMigrationsHistory table by EnsureDeleted() in EF Core 2 for PostgreSQL 9.0 and higher is fixed
- The bug with generating the COALESCE expression in EF Core is fixed
- The bug with calling DbExecutionStrategy.ShouldRetryOn(Exception), when the first connection fails to open, is fixed
dotConnect for PostgreSQL Professional 7.12.1328
- The bug with PgSqlLoader.LoadTable(IDataReader) for .NET Standard 1.3 and .NET Standard 2 is fixed
- The bug with applying Convert.IsDBNull() to PgSqlParameter.Value is fixed
LinqConnect (formerly known as LINQ to PostgreSQL):
- The bug with executing incorrect SQL request (cached during one of the previous calls), when .Contains() is invoked in the multithreaded application, is fixed
Entity Developer:
- The bug with generating fluent mapping for the one-to-one association by the DbContext template in EF4/EF5/EF6 is fixed
Entity Framework support:
- The translation of single-char literal into SQL statement in EF Core is supported
- The bug with SQL generation, when optionsBuilder.UseLoggerFactory() is used, in EF Core is fixed
- The bug with using a value converter for the property used in .Contains() in EF Core 2 is fixed
- The bug with translating String.IndexOf() into SQL statement in EF Core is fixed
- The bug with updating a null value of the concurrency check column with some non-null value in EF Core is fixed
dotConnect for PostgreSQL Professional 7.12.1307
- PostgreSQL 11 is supported
- The bug with connecting to database with .NET Standard 1.3 compatible assemblies on .NET Framework 4.6.0 run-time is fixed
LinqConnect (formerly known as LINQ to PostgreSQL):
- The new overload DataContext.Refresh(bool ignoreErrors, RefreshMode mode, object entity) is added for ignoring errors during refresh
- The existing overload DataContext.Refresh(RefreshMode mode, object entity) is improved: its check avoids the try to refresh the entity that is added to the context but not submitted to the database
- The type and text of the error generated by the DataContext.Refresh(RefreshMode mode, object entity) method, when the passed entity doesn't exist in database, is fixed
Entity Developer:
- The multiple select functionality in EF Core Model is improved: now it allows setting PrimaryKey, ValueGenerated, Concurrency for several properties simultaneously
- The bug with detecting order of columns in composite primary key with two or more columns by Update To Database and by Update From Database wizards in EF Core is fixed
- The bug with using ASP.NET Core Web Application (.NET Framework) and Azure Functions v1 (.NET Framework) projects in Visual Studio 2017 is fixed
Entity Framework support:
- Entity Framework Core 2.2.1 is supported
- The new extension method Database.IsPostgreSql() in EF Core 2 is implemented
- The bug with applying config.Workarounds.IgnoreSchemaName=true to the .ToTable() functionality in EF Core 2 is fixed
- The bugs with using the GuidToStringConverter, EnumToStringConverter, ValueConverter classes in EF Core 2 are fixed
- The bug with constructing the LIKE clause in EF Core 2 is fixed
- The bug with generating a subselect within the SELECT list in EF Core 2 is fixed
- The bug with applying an aggregate function to the result of a subselect in EF Core 2 is fixed