Devart dotConnect for MySQL Professional 8.3.135
Devart dotConnect for MySQL Professional 8.3.135 | 60 Mb
dotConnect for MySQL, formerly known as MyDirect .NET, is an enhanced ORM-enabled data provider for MySQL that builds on the ADO.NET technology to present a complete solution for developing MySQL-based database applications. It introduces new approaches for designing application architecture, boosts productivity, and leverages database applications.
Fast and Advanced ADO.NET Provider
dotConnect for Oracle offers both high performance native connectivity to the Oracle database and a number of innovative development tools and technologies. It supports a wide range of Oracle-specific features, such as Advanced Queuing, Alerts, Pipes, Direct Path Loading, Change notifications, Transparent Application Failover, REF cursors, objects, packages, and others.
RAD Approach
dotConnect for Oracle provides a vast number of GUI tools that increase your productivity. It integrates into Visual Studio Server Explorer and other tools, and provides advanced visual component editors to simplify component tweaking. DataSet tools, such as DataSet Wizard, DataSet Editor, DataSet Manager, provide you an easy way to create and edit typed and untyped DataSets.
ORM Solutions
dotConnect for MySQL offers enhanced ORM support with a bundled visual designer for ORM models - Entity Developer. dotConnect for MySQL supports ADO.NET Entity Framework, NHibernate, and LinqConnect (formerly known as LINQ to MySQL) - our own ORM solution, closely compatible to Microsoft LINQ to SQL, while extending its functionality with its own features.
8.3.135
The ADO.NET implementation of ASP.NET Identity support is improved
The ICloneable interface is implemented in the IdentityUser and IdentityRole classes
The User_Id column in the AspNetUserClaims table is renamed to UserId
The Install_identity_tables script shipped with installation is changed: the length of the AspNetRoles.Name and AspNetUsers.UserName columns is reduced from varchar(256) to varchar(166)
Entity Framework support
The UpdateDatabaseOperation operation in Code-First Migrations for Entity Framework 6.x is supported
The RenameIndexOperation operation in Code-First Migrations for Entity Framework 6.1 is supported
Multiple EntityContainers in the Code-First CreateDatabase()/CreateDatabaseScript()/DeleteDatabase() functionality are supported
The Database.Delete(DbConnection) functionality is supported: all objects in the current schema (database), which is specified in Database or set with Initialization Command connection string parameter, are removed if DatabaseScript.Schema.DeleteDatabaseBehaviour = AllSchemaObjects
The Database.Exists(DbConnection) functionality is supported: the method returns true if DatabaseScript.Schema.DeleteDatabaseBehaviour = AllSchemaObjects and at least one table exists in the current schema (database) which is specified in Database or set with Initialization Command connection string parameter
Determining correct datatypes of data retrieved by EntitySQL queries with UNION ALL and similar constructions is improved
The compatibility with Hibernating Rhinos EntityFramework Profiler is improved
The bug with throwing System.NullReferenceException when enumerating an ObjectResult returned by a stored procedure is fixed
The ADO.NET implementation of ASP.NET Identity support is improved
The ICloneable interface is implemented in the IdentityUser and IdentityRole classes
The User_Id column in the AspNetUserClaims table is renamed to UserId
The Install_identity_tables script shipped with installation is changed: the length of the AspNetRoles.Name and AspNetUsers.UserName columns is reduced from varchar(256) to varchar(166)
Entity Framework support
The UpdateDatabaseOperation operation in Code-First Migrations for Entity Framework 6.x is supported
The RenameIndexOperation operation in Code-First Migrations for Entity Framework 6.1 is supported
Multiple EntityContainers in the Code-First CreateDatabase()/CreateDatabaseScript()/DeleteDatabase() functionality are supported
The Database.Delete(DbConnection) functionality is supported: all objects in the current schema (database), which is specified in Database or set with Initialization Command connection string parameter, are removed if DatabaseScript.Schema.DeleteDatabaseBehaviour = AllSchemaObjects
The Database.Exists(DbConnection) functionality is supported: the method returns true if DatabaseScript.Schema.DeleteDatabaseBehaviour = AllSchemaObjects and at least one table exists in the current schema (database) which is specified in Database or set with Initialization Command connection string parameter
Determining correct datatypes of data retrieved by EntitySQL queries with UNION ALL and similar constructions is improved
The compatibility with Hibernating Rhinos EntityFramework Profiler is improved
The bug with throwing System.NullReferenceException when enumerating an ObjectResult returned by a stored procedure is fixed
Restriction: If you have 6 month or more than six month VIP membership please mail us for password.
Only for V.I.P Warning! You are not allowed to view this text.