Devart Entity Developer v6.2.468 » Developer.Team - Developers Paradise!

Devart Entity Developer v6.2.468

Devart Entity Developer v6.2.468
Devart Entity Developer v6.2.468


Entity Developer is a powerful ORM designer for ADO.NET Entity Framework, NHibernate, LinqConnect, and LINQ to SQL. You can use Model-First and Database-First approaches to design your ORM model and generate C# or Visual Basic .NET code for it. It introduces new approaches for designing ORM models, boosts productivity, and facilitates the development of database applications.

Visual ORM Model Designer with Code Generation
Entity Developer allows you to create and edit NHibernate, Entity Framework, LinqConnect, and LINQ to SQL models visually, without typing a line of XML code. It supports creating all kinds of mapping, such as table splitting, mapping entity to several tables, complex types, inheritance hierarchies, creating entities from SELECT statements and methods from SQL code, etc. Code generation is very flexible due to using T4-like templates, allowing virtually anything you may want for code generation. C# and VB code can be generated for your model out-of-the-box, and you may even create your own templates for other programming languages.

Multiple ORM Support
Entity Developer supports NHibernate, Entity Framework, LinqConnect, and LINQ to SQL models. It offers a separate edition for each of the supported ORMs and the Professional Edition supporting all the three ORMs. Entity Developer for NHibernate and Entity Developer for Entity Framework allow designing NHibernate and Entity Framework models. See the Compatibility page for the list of ADO.NET providers, supported for these ORMs. Entity Developer for LINQ to SQL uses Microsoft SqlClient to connect to database. Entity Developer is also included to the professional edition of dotConnect for PostgreSQL, MySQL, Oracle, SQLite, and Salesforce and to LinqConnect.

Powerful Code Generation
Entity Developer provides powerful T4-like template-based code generation framework. It offers you a number of predefined templates for different use cases. They are templates for generating context, entities, and mapping, with support for fluent, attribute, and XML mapping, both persistence aware and persistence ignorant (POCO) entities, support for validation framework for entity property values validation, etc. Additional templates offer functionality of automatic generating MVC Controller and views, Data Transfer Objects with converter classes for entities, Data Annotations metadata classes and other features. All these templates provide a number of settings for rich configuration capabilities, and if these are not enough, you even can create your own templates.

6.2.468 29-Mar-18

The new Retrieve Cross Database Relations option is implemented in Model Settings for detecting FK relations between tables in different databases (MySQL)
The bug with the Retrieve Data functionality on the base class of TPH inheritance is fixed
The bug with the Find Next functionality of T4 Editor embedded into Visual Studio is fixed
The bug with throwing the "IDE not supported" exception by Entity Developer in Visual Studio 2017 of versions 15.6.* is fixed
Entity Framework support
The new SQL Type, Size, Precision, Scale options are added to the Parameters tab in Method Editor of EF Core Model
The process of synchronizing methods and parameters with database stored procedures in EF Core Model is improved
The bug with adding entry to appsettings.json, when "Use the following connection string from App.Config" and "Rewrite connection string during regeneration" in Model Settings are turned on, is fixed
The bug with throwing the "Multiple constructors accepting all given argument types have been found in type '...'. There should only be one applicable constructor." error by the code generated with the MVC Controller template in ASP.NET Core Web Application is fixed
The bug with missing DataMember attribute on the Many end of an association, when using the EF Core template with "Generate Data Contracts=True", is fixed
The bug with applying the "Include foreign key columns in the model" model setting by Create Model Wizard is fixed (SQL Server)


Only for V.I.P
Warning! You are not allowed to view this text.