Devart dotConnect for PostgreSQL v7.20.1836 Professional
Devart dotConnect for PostgreSQL v7.20.1836 Professional
dotConnect for PostgreSQL is a high-performance ORM enabled data provider for PostgreSQL that builds on ADO.NET technology to present a complete solution for developing PostgreSQL-based database applications. It introduces new approaches for designing application architecture, boosts productivity, and facilitates the development of database applications.
Our ADO.NET PostgreSQL provider supports a wide range of PostgreSQL-specific features, such as secure SSL connections, PostgreSQL notifications, PostgreSQL bulk data loading, GEOMETRY, PostgreSQL ARRAY types, and others.
Advanced Visual Studio Integration
dotConnect for PostgreSQL provides a vast number of GUI tools that increase your productivity. For example, it includes DataSet tools, such as DataSet Wizard, DataSet Editor, DataSet Manager, provide you an easy way to create and edit typed and untyped DataSets.
PostgreSQL ADO.NET Provider supports advanced Visual Studio integration (DDEX), and provides convenient visual component editors to simplify component tweaking.
Broad Compatibility
dotConnect for PostgreSQL was the first PostgreSQL database provider to support .NET Core and Entity Framework Core, and we work hard to support new platforms and development technologies as soon as they are released.
PostgreSQL support: from 7.1 to 12
Visual Studio support: 2008 – 2019
Platforms support:
Full .NET Framework 2.0 – 4.8
.NET Core 1.x, 2.x, and 3.0
.NET Compact Framework 2.0 and above
Mono 2.0 and above
Enhanced ORM Support
dotConnect for PostgreSQL offers enhanced ORM support with a bundled visual designer for ORM models - Entity Developer. Our PostgreSQL ADO.NET Provider supports the following ORMs:
Entity Framework v1 - v6
Entity Framework Core 1.x, 2.x, and 3.1
NHibernate
LinqConnect
7.20.1836 18-Feb-21
The new command line option /disablegac that disables adding assemblies to GAC is added
The bug in PgSqlDependency when created a lot of dependences is fixed
The bug with applying the "Unprepared Execute=True;" connection string parameter to the command object created with PgSqlCommand.Clone() is fixed
Entity Developer
The behavior is changed in Entity Developer embedded into Visual Studio: lower versions in the EF Core version property of Model Settings are not hidden any more
The behavior is changed in EF Core Model: QueryType=True is set now for all classes without PK
C# code generation is improved: the using directives are generated instead of full namespaces in the names of attributes for DataAnnotations, NHibernate Validator, and Enterprise Library validation frameworks
Code generation is improved: OnModelCreating(modelBuilder) of the base class is invoked now if the Base Context Type property of EF Core Model is initialized
Entity Framework support
Entity Framework Core 5.0.3 is supported
Entity Framework Core 3.1.12 is supported
The bug with translating Enum.HasFlag to SQL in EF Core 3 and EF Core 5 is fixed
The new command line option /disablegac that disables adding assemblies to GAC is added
The bug in PgSqlDependency when created a lot of dependences is fixed
The bug with applying the "Unprepared Execute=True;" connection string parameter to the command object created with PgSqlCommand.Clone() is fixed
Entity Developer
The behavior is changed in Entity Developer embedded into Visual Studio: lower versions in the EF Core version property of Model Settings are not hidden any more
The behavior is changed in EF Core Model: QueryType=True is set now for all classes without PK
C# code generation is improved: the using directives are generated instead of full namespaces in the names of attributes for DataAnnotations, NHibernate Validator, and Enterprise Library validation frameworks
Code generation is improved: OnModelCreating(modelBuilder) of the base class is invoked now if the Base Context Type property of EF Core Model is initialized
Entity Framework support
Entity Framework Core 5.0.3 is supported
Entity Framework Core 3.1.12 is supported
The bug with translating Enum.HasFlag to SQL in EF Core 3 and EF Core 5 is fixed
Only for V.I.P Warning! You are not allowed to view this text.