dotConnect for Oracle

What's new in this version:

dotConnect for Oracle Professional 10.3.104
- 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 an issue with the Oracle Object Wizard in Visual Studio 2022
- Fixed a design-time bug with the OracleQueue component in Visual Studio 2022
- Fixed a design-time bug with the OracleDataTable Tasks interface element in Visual Studio 2022
- Resolved an issue with connecting to Oracle 19 and higher in Direct mode when using Oracle Encryption or Oracle Data Integrity

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
- Fixed an issue with incorrect conversion of single-element enum arrays in EF Core LINQ queries
- Resolved an issue causing an ORA-00920 error when generated SQL included duplicate WHEN CASE clauses in EF Core 8
- Resolved an issue with type mappings that occurred when config.CodeFirstOptions.UseNonLobStrings=true in EF Core 2.1 and later versions
- Resolved search query issues with geometry objects containing points in EF Core
- Resolved a bug that caused a MissingMethodException in EF Core versions 6, 7, and 8

Entity Developer:
- Fixed an issue where the Update From Database Wizard reset navigation property names in EF Core models


dotConnect for Oracle Professional 10.3.21
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


dotConnect for Oracle Professional 10.3.20
- Supported Visual Studio 2022 version 17.11 Preview
- Added the GetAuditActionBanner() and GetUnauthorizedAccessBanner() methods to the OracleConnection class
- Fixed an issue with passing a negative year number in OracleTimeStamp
- Fixed an issue where an incorrect comma was added before LEFT OUTER JOIN with OracleSelectStatement
- Fixed an issue with OracleSelectStatement that caused an exception after adding a WHERE condition and converting to ToString()

Entity Framework support:
- Updated support for Entity Framework Core 8 to version 8.0.5
- Updated support for Entity Framework Core 8 to version 8.0.5
- Updated support for Entity Framework Core 6 to version 6.0.30

Entity Developer:
- Resolved an issue with saving 'Version=Original' in the Stored Procedure Mapping menu for LinqConnect model


dotConnect for Oracle Professional 10.3.10
- NET 8 compatibility
- Visual Studio 2022 version 17.9 Preview is supported
- Added support for connect to servers with enabled Security Banners in the Direct mode
- The error in the string representation of the OracleSelectStatement containing a JOIN has been fixed
- The functionality of the OracleConnection.ChangePassword() method in the Direct mode has been corrected to enable the modification of expired passwords

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
- The bug with throwing ArgumentNullException when quering parent table in TPT inheritance in EF Core is fixed

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

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


dotConnect for Oracle Professional 10.2.0
- Oracle 23c is supportd
- Visual Studio 2022 version 17.8 Preview is supported
- The error during installation on the 32-bit version of Windows has been fixed

Entity Framework support:
- Entity Framework Core 7.0.10 is supported
- Entity Framework Core 6.0.21 is supported
- The behavior is changed: no additional connection is opened to the database before the first query in EF Core when config.Workarounds.ProviderManifestToken is set explicitly
- The bug with running LINQ queries to Oracle Server 11.2 and below in EF Core 5/6/7 is fixed
- The bug with a redundant requirement to register UseNetTopologySuite, when it is not used, in EF Core 7 is fixed
- The bug with generating invalid SQL when filtering on a boolean property in the Where clause of LINQ query in EF Core 5/EF Core 6/EF Core 7 is fixed
- The bug with using the Any clause of LINQ query in EF Core 7 is fixed
- The bug with throwing Microsoft.EntityFrameworkCore.Infrastructure.ManyServiceProvidersCreatedWarning by the UseOracle(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
- The bug with using the same __EFMigrationsHistory table by several contexts in EF Core Code-First Migrations is fixed

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


dotConnect for Oracle Professional 10.1.151
- Visual Studio 2022 version 17.7 Preview is supported
- Implemented IOracleCommandAdapter interface to access OracleCommand in IDbCommandInterceptor in EF6
- Implemented option config.QueryOptions.InitialLobFetchSize for EF4/EF5/EF6 and EF Core
- Fixed bug with InitialLobFetchSize in OracleCommand when calling Clone() method

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 generating parameter prefixed by a double colon in EF Core 7 is fixed
- The bug with assigning null to the NetTopologySuite property in EF Core is fixed
- The bug with using the .ExecuteDelete() functionality in EF Core 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
- The bug with code generation for TPT inheritance in the EF Core template is fixed
- The bug with retrieving metadata of functions, procedures, packages in Oracle Server 8i/9i/10g by Create Model Wizard is fixed


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

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

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


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

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

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


dotConnect for Oracle Professional 9.16.1434
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 SQL translation of the following class members used in LINQ query is supported in EF Core 3, EF Core 5, EF Core 6
- static method IsNullOrWhiteSpace() of the String class
- static property Today and instance property DayOfWeek of the DateTime class
- static methods Sqrt(), Max(), Min(), Log(), Log10(), Sin(), Cos(), Tan(), Asin(), Acos(), Atan(), Atan2(), Sinh(), Cosh(), Tanh() of the Math class

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

The SQL translation of the following class members used in LINQ query is supported in EF Core 6:
- static method Log2() of the Math and MathF classes

- Mapping of internet/intranet data type System.Uri to Oracle string data types is supported in EF Core 3, EF Core 5, EF Core 6
- Mapping of network data types System.Net.IPAddress and System.Net.NetworkInformation.PhysicalAddress to Oracle string data types is supported in EF Core 5 and EF Core 6
- Mapping of Oracle object types like MDSYS.SDO_GEOMETRY or Oracle user-defined object datatypes in a database to the OracleObject class in EF Core 3, EF Core 5, EF Core 6 is supported
- The config.SpatialOptions.PreferSpatialOperators configuration option is added (default value is False) to provide the possibility of using spatial operators instead of functions from the SDO_GEOM package
- The bug with auto savepoints enabled in EF Core 6 transactions is fixed
- The bug with generating the "Value cannot be null" error when dropping indexes via Code-First Migrations in EF Core is fixed
- The bug with a materialization used within the Let operator of LINQ query in EF6 is fixed
- The bug with using .Contains with a collection within .Select of LINQ query in EF Core 2 is fixed


dotConnect for Oracle Professional 9.15.1410
- The type converter of the OracleTimeStamp structure is improved for converting to/from DateTime and DateTimeOffset
- The bug with declaring several functions or procedures in the WITH clause executed via the OracleScript class is fixed
- The bug with AUDIT and NOAUDIT statements in the Direct mode 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
- The bug with calling methods and properties of the Geometry class and its child classes, when the type member returns bool, with NetTopologySuite in EF Core is fixed
- The bug with incomplete SQL generation by update-database -script when config.CodeFirstOptions.DropConstraintsByColumns=true in Entity Framework 6.4.4 is fixed
- The bug with throwing ORA-00920 by the GeometryCollection.Intersects method when using NetTopologySuite spatial service in EF Core 5 is fixed
- The bug with throwing ORA-00920 by the Geometry.Disjoint method when using NetTopologySuite spatial service in EF Core 3 and EF Core 5 is fixed
- The bug with throwing the "Unexpected primitive type kind 'r'." error when using NetTopologySuite spatial service with a geometric constant in EF Core 3 and EF Core 5 is fixed


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

Entity Framework support:
- Entity Framework Core 5.0.12 is supported
- Entity Framework Core 3.1.21 is supported
- The bug with incomplete SQL generation by update-database -script in Entity Framework 6.4.4 is fixed


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

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

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

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


dotConnect for Oracle Professional 9.14.1353
Fixed:
- The bug with a connection via a DNS name in an IPv6 network in the Direct mode using NuGet packages is fixed
- The bug with ORA-12899 error when using parameters with an Oracle 12 server in the Direct mode is fixed
- The bug with ORA-01461 error when using parameters with an Oracle 12 NLS_CHARACTERSET=WE8ISO8859P15 server in the Direct mode is fixed
- The bug with the System.NullReferenceException error in Event objects when using parameters with an Oracle 12 server in the Direct mode is fixed
- The bug with throwing ORA-01483 on Oracle Server 12.2 with NLS_CHARACTERSET = EE8MSWIN1250 when using parameters in the Direct mode is fixed

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

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


dotConnect for Oracle Professional 9.14.1312
LinqConnect (formerly known as LINQ to Oracle):
- The new methods IsNotDistinctFrom() and IsDistinctFrom() are added to the Devart.Data.Linq.SqlMethods class
- The bug with using out parameters of a stored procedure, when Mapping Mode is set to File in Model Settings, is fixed

Entity Framework support:
- Entity Framework Core 5.0.8 is supported
- Entity Framework Core 3.1.17 is supported
- The bug with ignoring schema set for indexes via RenameIndex() operation of EF Core Code-First Migrations is fixed
- The bug with missing N-prefix in the generated Unicode literal used in .Contains(), .EndsWith(), .StartsWith() within .Where() in EF6 is fixed


dotConnect for Oracle Professional 9.14.1298
- Visual Studio 2019 version 16.11 Preview 2.0 is supported

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

Entity Framework support:
- Entity Framework Core 5.0.7 is supported
- Entity Framework Core 3.1.16 is supported
- The bug with comparing enum values in EF Core 3 and EF Core 5 is fixed
- The bug with .Contains and .Length in EF Core 3 and EF Core 5, when using NetTopologySuite spatial functionality, is fixed
- The bug with missing N-prefix in the generated Unicode literal used in .Contains(), .EndsWith(), .StartsWith() within .Where() in EF Core 3 and EF Core 5 is fixed


dotConnect for Oracle Professional 9.14.1273
- The bug with ORA-03106 error in the Direct mode 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(OracleEntityProviderServicesConfiguration))] 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 Oracle Professional 9.14.1234
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 Oracle Professional 9.14.1228
- 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
- The bug with calling OracleObject.ExecuteMethod(), when OracleObject is created in application code without assigned attributes, is fixed
- The bug with string conversion by OracleTimeStamp.ToString(), when .ToString() includes FF fractional seconds format and the database column is TIMESTAMP(0), is fixed
- The bug with throwing AccessViolationException by OracleCommand.ExecuteScalar() in the OCI mode is fixed
- The ORA-01483 and ORA-03120 errors on a server with NLS_CHARACTERSET=WE8MSWIN1252 are fixed (Direct mode)

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

Entity Framework support:
- Entity Framework Core 5.0.4 is supported
- Entity Framework Core 3.1.13 is supported
- The bug with throwing ORA-00920, when using conditional operator within LINQ query, in EF Core 3 and EF Core 5 is fixed
- The bug with inserts and updates, when property mapping includes DatabaseGeneratedOption, in EF Core 5 is fixed


dotConnect for Oracle Professional 9.14.1204
- The new command line option /disablegac that disables adding assemblies to GAC is added
- The bug with using OracleCommand.CommandTimeout in the OCI mode, when Oracle Client leaves an open session to failed RAC node, is fixed
- The bug with character encoding in the Direct mode when InitialLobFetchSize is set is fixed
- Wrong timezone setting when opening a connection in the Direct mode is fixed


dotConnect for Oracle Professional 9.14.1180
- 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 memory leak when running a lot of queries in the OCI mode is fixed

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

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

Entity Framework support:
- Entity Framework Core 5.0.2 is supported
- Entity Framework Core 3.1.11 is supported
- The new metadata to describe autoincremental columns via annotations in EF Core Code-First Migrations are implemented
- The new config.DatabaseScript.Index.UseCurrentSchema option (default value is false) is added for ability to ignore schema set for indexes via EF Core Code-First Migrations
- The behavior is changed: config.DatabaseScript.Index.UseCurrentSchema is set to false by default; as a result, the schema argument in CreateIndex(), DropIndex(), AddUniqueConstraint(), DropUniqueConstraint() operations is now applied not only to the table name, but also to the index name, i.e. previously, the index was always created in the current schema, and now it is created in the schema of the table to which the index belongs
- The bug with ignoring schema set for indexes via CreateIndex(), DropIndex(), AddUniqueConstraint(), DropUniqueConstraint() operations of EF Core Code-First Migrations is fixed


dotConnect for Oracle Professional 9.14.1160
- The bug with retrieving the TIMESTAMP WITH LOCAL TIME ZONE values in the TZR (time zone region) format in the Direct mode is fixed
- The bug with throwing System.ArgumentOutOfRangeException, when OracleCommand.Prepare() has been called before and reader is reused with another query, in the Direct mode is fixed
- The bug with throwing ORA-00918 by OracleCommand.ExecutePageReader(), when SQL query returns several columns with the same name in the case of multiple result sets/multiple tables or views/subqueries, in Oracle 12c or higher is fixed


dotConnect for Oracle Professional 9.14.1150
- Visual Studio 2019 version 16.9 Preview is supported
- The bug with throwing the ORA-01483 error when updating the VARCHAR2 column on Oracle 12.2 with NLS_CHARACTERSET=UTF8 in the Direct 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
- The bug with placing procedure with no parameters in the Procedures node instead of being enlisted in its package's node of Update From Database Wizard tree in the case of Oracle 18c and higher 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 generating invalid SQL, when the sdo_geometry column is part of a subquery, in EF Core 3 is fixed
The bug with using another context's connection in DbContextOptionsBuilder.UseOracle(connection) in EF Core is fixed


dotConnect for Oracle Professional 9.13.1127
- 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 connecting to Oracle Real Application Clusters (RAC) in the Direct mode is fixed
- The bug with missing Name and Owner properties of the OracleConnection 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 incorrect SQL translation of .Contains with a collection of more than 1000 items in EF Core 3 is fixed
- The bug with generating invalid SQL for EF.Functions.Like in EF Core 3 is fixed


dotConnect for Oracle Professional 9.13.1107
- 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 Oracle Professional 9.13.1098
- The new DescribeStoredProcedure property is added to the OracleConnection class
- 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 detecting daylight saving time settings on a current workstation when reading the TIMESTAMP WITH LOCAL TIME ZONE values in the Direct mode is fixed
- The bug with double shifting timezone when retrieving the TIMESTAMP WITH LOCAL TIME ZONE values in the Direct mode 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.Oracle.EFCore.NetTopolosySuite with a .NET Standard 2.1 assembly, that is compatible with .NET Core 3, is added
- The new EntityEFCore3Devart.Data.Oracle.Entity.EFCore.NetTopolosySuite.dll assembly compiled with EF Core 3.1 and .NET Framework 4.6.1 is added
- The OracleFunctions class, which allows using Oracle-specific functions in LINQ to Entities, is supported in EF Core
- The OracleTextFunctions class, which allows using Oracle full-text search functionality in LINQ to Entities, is supported in EF Core
- The bug with generating invalid SQL when filtering on a boolean property that is assigned with .Any() in EF Core 3.1 is fixed
- The bug with generating invalid SQL when filtering on a boolean property that is assigned with comparing to Count() in EF Core 3.1 is fixed


dotConnect for Oracle Professional 9.12.1064
- The performance of fetching data in the Direct mode is improved
- The bug with throwing "ORA-03106: fatal two-task communication protocol error" on SELECT queries in the Direct mode is fixed
- The bug with opening database connection, when OS user name includes special symbols, in the Direct mode is fixed
- The bug with loading the Int32 value into a NUMBER column using OracleLoader via Oracle Client 19 is fixed
- The bug with calling stored procedure using OracleCommand.ExecuteArray() via Oracle Client v19.5 is fixed
- The bug with throwing "Cannot convert object of type 'Devart.Data.Oracle.OracleLob' to object of type 'Devart.Data.Oracle.OracleIntervalYM'." in the Direct mode is fixed


dotConnect for Oracle Professional 9.12.1054
- SSH is supported in the Direct mode

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 Oracle):
- The "Could not find element type in model" bug when loading XML mapping in .NET Standard LinqConnect assemblies is fixed
- The bug with using enums via .NET Standard compliant assemblies is fixed

Entity Framework support:
- The bug with incorrect SQL generation when using .Substring() in a .Select() statement in EF Core 2 is fixed
- The bug with casting a non-nullable numeric to an Enum during materialization of LINQ query in EF Core is fixed
- The bug with incorrect SQL generation when using .OrderBy() with comparison in EF Core is fixed


dotConnect for Oracle Professional 9.11.1034
- Visual Studio 2019 version 16.7 Preview is supported
- The bug with throwing System.OverflowException by OracleCommand.ExecuteArray(), when passing a large amount of data containing empty strings, in the OCI mode is fixed
- The bug with executing REVOKE statement via OracleScript in the Direct mode is fixed
- The bug with opening connection in the Direct mode via SSL/TLS is fixed
- The bug with throwing "ORA-03106: fatal two-task communication protocol error", when OracleCommand.InitialLobFetchSize is set to non-zero value, in the Direct mode is fixed

Entity Developer:
- .NET 5 is added to the list of available Target Framework versions in Create Model Wizard and Model Settings in EF6, EF Core, LinqConnect models
- The new option "Execute procedures for result set detection" is added to Model Settings of EF Core Model to control obtaining metadata of a procedure or function result set
- The new option "Use NULL parameter values" is added to Model Settings of EF Core Model to specify whether NULL parameter values are used for stored procedure execution
- The new option "Add complex types to diagram" is added to Model Settings of EF Core Model to control behavior of Create Model Wizard and Update Model From Database Wizard
- The new option "Add new complex types to the current diagram" is added to Update Model From Database Wizard of EF Core Model
- The new Primitive Default Value Generation property is added to EF, EF Core templates to determine whether to generate initialization for a primitive property based on database DEFAULT column value
- The new property Collection Property Type is added to EF template "DbContext" and EF Core template "EF Core" to determine .NET type used as a property type for the Many end of associations
- The new property Collection Initialization Type is added to EF template "DbContext" and EF Core template "EF Core" to determine .NET type used for initialization of the Many end of association; if it is set to None, then no initialization is generated
- The new property "Nullable Reference Types" is added to C# templates of EF, EF Core models to specify whether C# 8 nullable reference types and non-nullable reference types must be generated
- The new partial method is added to the OnModelCreating(DbModelBuilder modelBuilder) method generated by DbContext template of EF model
- The 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 Oracle 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 detecting numeric and string literals, specified within round brackets, when generating initialization of properties basing on Oracle columns' default values in EF, EF Core models is fixed
- The bug with SQL generation in EF Core 3, when enum values are used in CASE and COALESCE statements, 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 Oracle):
- 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(OracleEntityProviderServicesConfiguration))] 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 using Scaffold-DbContext in EF Core and EDM Wizard in EF with more than 1000 tables/views is fixed
- The bug with the opposite order of operands in case of less than, more than operators in the Where clause of LINQ query in EF Core 3 is fixed
- The bug with including several subcollections in LINQ query in EF 6.4 is fixed
- The bug with throwing "ORA-00907: missing right parenthesis" with Expression.Or, Expression.And in EF Core 3.1 is fixed


dotConnect for Oracle Professional 9.11.980
- The new connection string parameter SSL Key is added

The bug with using the following parameters of connection.GetSchema("Arguments", ...) is fixed:
- connection.GetSchema("Arguments", new string[] { "schema_name", null })
- connection.GetSchema("Arguments", new string[] { "schema_name", "%" })
- connection.GetSchema("Arguments", new string[] { "schema_name", "package_name", "procedure_name" })
- connection.GetSchema("Arguments", new string[] { "schema_name", null, "procedure_name" })

- The bug with calling OracleDataReader.IsDBNull() for a NULL value got from the ANYDATA column is fixed
- The bug with defining functions and procedures in the view body specified in OracleScript.ScriptText for Oracle 12c and higher is fixed

LinqConnect (formerly known as LINQ to Oracle):
- 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
- The bug with using collections with more than 1000 items in a .Contains() method in EF Core 3 is fixed
- The bug with the AlterColumn operation in EF Core Code-First Migrations, when data type is being changed but oldType is not specified, is fixed
- The bug with generating EXCEPT instead of MINUS in SQL produced by EF Core 3.1 is fixed


dotConnect for Oracle Professional 9.11.951
- SQL Server Integration Services 2019 (SSIS 2019) is supported
- SSL/TLS is supported in the Direct mode
- The new connection string parameters SSL Cert and SSL Server CertDN are added
- The new properties WalletMethod and WalletLocation are added to the DirectUtils class
- The new class OracleCredential is implemented to provide a more secure way to specify the password while opening connection in the OCI mode on Windows
- The new overload OracleConnection(string connectionString, OracleCredential credential) is added
- The new overload ChangePassword(SecureString newPassword) is added
- The new property DefaultExpressionCacheSize (by default, 100) is added to the OracleLoader class to specify the number of default expressions that are evaluated at a time
- The new property DefaultExpressionBehavior is added to the OracleLoader class to specify how the direct path API handles default expressions for columns that are not explicitly being loaded
- OCI Multiple Homes is supported in .NET Standard 2.1
- The OracleDataTable and OracleDataSet classes are supported in .NET Standard 2.0/2.1
- Connection pool performance counters are supported in .NET Standard 2.0/2.1
- .NET Standard 2.1 compatible assembly is added to the Devart.Data.Oracle NuGet package
- The new class OracleShardingKey is implemented to store one or more key values for sharding in the OCI Session Pooling mode with Oracle Client 12g Release 2 and higher
- The new methods SetShardingKey(OracleShardingKey shardingKey) and SetShardingKey(OracleShardingKey shardingKey, OracleShardingKey superShardingKey) are added to the OracleConnection class
- Query Result Change Notification (QRCN) is supported
- The new column QueryId is added to DataTable stored in OracleNotificationEventArgs.Details
- The new properties GroupingNotificationEnabled, GroupingType, GroupingInterval are added to the OracleNotificationRequest class
- The new properties RegisteredQueryIds, RegisteredResources, RegId are added to the OracleDependency class
- The new connection mode OracleConnectMode.SysRac is supported for managing Real Application Clusters in Oracle Server 12c Release 2 and higher
- The new property OracleUtils.ParameterValueTrimming (by default, false) is added to trim value that exceeds OracleParameter.Size
- The behavior is changed: OCIStmtPrepare2() is used now instead of OCIStmtPrepare() in the OCI mode to support the use of Application Continuity in an HA infrastructure
- The behavior is changed: pool is automatically cleared when AppDomain is being closed
- The bug with inserting Unicode N-prefixed string literal when using the "Unicode=true" connection string parameter in the Direct mode is fixed
- The bug with getter of OracleParameter.OracleValue, when it returns an empty array, is fixed
- The bug with initializing NHibernate configuration on .NET Standard 2.0 is fixed


dotConnect for Oracle Professional 9.9.887
- 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 config.DatabaseScript.PrimaryKey.IndexTablespace configuration option is added to specify the tablespace for implicit PK indices created via - the Code-First approach
- Support for changing NULL/NOT NULL constraint for LOB columns in the AlterColumn operation of EF Core Code-First Migrations is added
- 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 generating invalid SQL when calling members of owned type in EF Core 2 is fixed
- The bug with throwing "ORA-12704: character set mismatch" in case of UNION ALL over OUTER APPLY/CROSS APPLY in EF1/EF4/EF5/EF6 is fixed
- The bug with using .Contains within .Select of LINQ query in EF Core 2 is fixed