Devart Entity Developer v6.8.1019 Professional
Devart Entity Developer v6.8.1019 Professional
Entity Developer is a powerful ORM designer for ADO.NET Entity Framework, Entity Framework Core, Hibernate, LinqConnect, Telerik Data Access, and LINQ to SQL. It introduces new approaches for designing ORM models, boosts productivity, and facilitates the development of database applications.
Develop Faster
Design your data access layer visually, via drag-n-drop, and then generate code automatically. Or simply generate a model from a database or vice versa in a couple of minutes.
Do Less Mistakes
Automating data access layer generation helps you do less mistakes in your code. Our code generation templates are used for years and utilized by hundreds of users.
Professional Tool
Devart develops solutions for .NET Data access for 15 years, and our ORM designer is 9 years on the market. It is a professional tool, created by experienced developers and designed to make you more productive.
Visual Designer for a Variety of .NET ORMs
Entity Developer can help you design models for various .NET ORMs in one unified interface. You can get support for all ORMs in one tool, or you may purchase a separate edition, working with one of the supported ORMs.
Feature-Rich Designer with Powerful Code Generation
Seamless Visual Studio integration
Support for Model-First and Database-First
Visual creation for nearly all kinds of mapping
Applying model changes to database or vice versa
Powerful model refactoring
Optimized work with large models
Design-time LINQ/ESQL/HQL query execution
Viewing and editing of data in source tables
Background model validation
T4 template-based C# or VB code generation
Lots of predefined templates
File per class, partial class generation
Custom attributes support
Custom template support
Template editor with syntax highlighting
High quality of generated code
Highly customizable generation
Console application for automation
Wide Mapping Support
Edit nearly any kind of mapping for all the supported ORMs visually.
Visual editors for classes, properties, complex types, enums
Support for various kinds of inheritances and associations
Mapping CRUD operations to stored procedures
Create methods from stored routines or command texts
Visual editing of a storage part of Entity Framework v1-v6 models
Table splitting, entity splitting, query views
and many more...
Database-First Approach Support
Easily generate a model from a database and apply database changes to the model. Switch to model-first whenever necessary.
Generate a model from a database in a few clicks
Apply changes of the database schema to the model
Configure generation with lots of various options
Flexibly configure naming of generated classes, members, and methods
Get from database to ready-to-use code in minutes
Model-First Approach Support
Create a model and then generate a database from it automatically. Apply model changes to the database without losing data where possible.
Generate a database from a model in a few clicks
Specify a default set of properties to be added to each new entity
View, select, and apply model changes to the database
Flexibly configure naming of generated tables and columns
Visual Studio Integration
Entity Developer is seamlessly integrated into Visual Studio; however, if you don't have Visual Studio, you still can use Entity Developer as a separate application.
Design model directly in the IDE
Visual Studio 2008 - 2019 support
Refactoring integration
Code is generated when you save the model
Errors in model are displayed in Visual Studio Error List
Model diagrams, template editor behave like usual IDE documents
Documentation is integrated into Visual Studio documentation
Powerful Refactoring
Powerful Model Refactoring wizard allows you to quickly configure mapping aspects that cannot be automatically generated from database. It allows you to create:
inheritance hierarchies,
complex types,
table splitting
in just a couple of clicks.
Optimized Work with Large Models
Entity Developer is optimized to ensure comfortable and efficient work with large models, containing thousands of entities.
Highly optimized metadata retrieving
Split model into several thematic diagrams
Fast code generation
LINQ Query Execution against Models
Execute LINQ, Entity SQL, or HQL queries (depending on the ORM used) without the need to finish your application.
Test your model at design-time
Preview the returned data and browse related entities
View and edit data of the database tables directly
Template-Based Code Generation
Template-based code generation system in Entity Developer can satisfy even the most demanding developers.
Generate C# or Visual Basic code
T4-template based code generation
Editable templates
Wide Choice of Predefined Templates
Entity Developer offers a large set of predefined templates for generating C# or Visual Basic code for various needs.
Templates for POCO or persistence aware classes
Fluent or XML mapping
Templates for DTO classes
Templates for Data Annotation Metadata
Templates for WCF RIA Service
MVC controller and view templates
And more...
Flexible Generation Settings
Entity Developer allows you to configure code generation to a large extent with template properties, custom attribute support, extended properties for model objects, etc.
Generate all classes to one file or file per class
Configure project folders to output files
Generate extensible partial classes with code behind
Configure generation with template properties
Specify attributes to use for model objects
Custom Templates Support
Even if the standard Entity Developer code generation is not enough for you, you can achieve virtually anything by creating your own custom templates, even generate code for other programming languages.
Convenient template editor with syntax highlight
Store templates with model or in ED resources
Add properties for model objects that affect generation
Get unlimited generation capabilities
Console Support
Entity Developer provides a console application that allows automating code generation/database updates and performing common operations via console commands:
Generate model from database
Validate model
Generate code from model
Generate create database from model script
Generate update database from model script
6.8.1019 17-Jun-20
The new Primitive Default Value Generation property is added to EF, EF Core, NHibernate, Telerik Data Access templates to determine whether to generate initialization for a primitive property based on database DEFAULT column value
The new property "Nullable Reference Types" is added to C# templates of EF, EF Core, NHibernate models to specify whether C# 8 nullable reference types and non-nullable reference types must be generated
The code generation of assigning DateTime.Now to the DateTime property mapped to the MySQL datetime column with the default value CURRENT_DATE or CURDATE() in EF, EF Core, NHibernate models is supported when Primitive Default Value Generation=LiteralOrExpression (MySQL Connector/Net)
The ability to search for available System.Data.SQLite (with SQLite.Interop.dll dependency) and FirebirdSql.Data.FirebirdClient providers in local NuGet cache is implemented in a standalone and console Entity Developer for Entity Model and NHibernate Model
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, MySQL, PostgreSQL being quoted by Entity Developer is updated
Retrieving SQL Server metadata of cross-schema foreign keys by Create Model Wizard and Update From Database Wizard is optimized (SQL Server)
The behavior of Create Model Wizard and Update From Database Wizard is changed: timeout used for reading SQL Server metadata is greatly increased
The behavior for the new EF, EF Core, NHibernate, Telerik Data Access 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 and NHibernate 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 compatibility issue with JetBrains ReSharper is fixed
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, NHibernate 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, NHibernate models 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, NHibernate models is fixed ("ODP.NET, Unmanaged Driver"/"ODP.NET, Managed Driver")
The bug with retrieving metadata of string columns' default values in MySQL 8 is fixed (MySQL Connector/Net)
The bug with droping and recreating indexes by Update From Database Wizard, when there are unique indexes with the same name in different tables, is fixed (SQL Server)
The bug with throwing "Index was outside the bounds of the array" by Create Model Wizard and Update From Database Wizard, when getting metadata from result set with datetime2 or/and time columns returned by Table Valued Function, is fixed (SQL Server)
The bug with generating new Guid() with Primitive Default Value Generation=Literal in EF, EF Core, NHibernate, Telerik Data Access models is fixed
Entity Framework support
Entity Framework Core 5.0 is supported for Microsoft.Data.SqlClient, Microsoft.Data.Sqlite, Npgsql
.NET 5.0 is added to the list of available Target Framework versions in Create Model Wizard and Model Settings in EF6 and EF Core 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 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 partial method is added to the OnModelCreating(DbModelBuilder modelBuilder) method generated by DbContext template of EF model
The design time connection via Microsoft.Data.SQLite is supported for creating EF Core Model in standalone and console versions of Entity Developer
The generation of a class inherited from DbConfiguration in EF 6.4 is added to .NET Core/.NET Standard projects (Npgsql/Firebird)
The DbProviderFactories and DbProviderServices registrations are implemented in Create Model Wizard of EF6 models for System.Data.SQLite and FirebirdSql.Data.FirebirdClient providers in .NET Framework and .NET Core/.NET Standard projects
The new property Target Framework is added to Create Model Wizard and Model Settings of EF6 models
The list of providers (packages) loaded by Create Model Wizard in EF6 models is extended
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 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
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 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 Visual Studio validation of EF 6.4 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 adding entities to conceptual part of EF6 model created using Npgsql or System.Data.SQLite 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 new Primitive Default Value Generation property is added to EF, EF Core, NHibernate, Telerik Data Access templates to determine whether to generate initialization for a primitive property based on database DEFAULT column value
The new property "Nullable Reference Types" is added to C# templates of EF, EF Core, NHibernate models to specify whether C# 8 nullable reference types and non-nullable reference types must be generated
The code generation of assigning DateTime.Now to the DateTime property mapped to the MySQL datetime column with the default value CURRENT_DATE or CURDATE() in EF, EF Core, NHibernate models is supported when Primitive Default Value Generation=LiteralOrExpression (MySQL Connector/Net)
The ability to search for available System.Data.SQLite (with SQLite.Interop.dll dependency) and FirebirdSql.Data.FirebirdClient providers in local NuGet cache is implemented in a standalone and console Entity Developer for Entity Model and NHibernate Model
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, MySQL, PostgreSQL being quoted by Entity Developer is updated
Retrieving SQL Server metadata of cross-schema foreign keys by Create Model Wizard and Update From Database Wizard is optimized (SQL Server)
The behavior of Create Model Wizard and Update From Database Wizard is changed: timeout used for reading SQL Server metadata is greatly increased
The behavior for the new EF, EF Core, NHibernate, Telerik Data Access 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 and NHibernate 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 compatibility issue with JetBrains ReSharper is fixed
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, NHibernate 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, NHibernate models 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, NHibernate models is fixed ("ODP.NET, Unmanaged Driver"/"ODP.NET, Managed Driver")
The bug with retrieving metadata of string columns' default values in MySQL 8 is fixed (MySQL Connector/Net)
The bug with droping and recreating indexes by Update From Database Wizard, when there are unique indexes with the same name in different tables, is fixed (SQL Server)
The bug with throwing "Index was outside the bounds of the array" by Create Model Wizard and Update From Database Wizard, when getting metadata from result set with datetime2 or/and time columns returned by Table Valued Function, is fixed (SQL Server)
The bug with generating new Guid() with Primitive Default Value Generation=Literal in EF, EF Core, NHibernate, Telerik Data Access models is fixed
Entity Framework support
Entity Framework Core 5.0 is supported for Microsoft.Data.SqlClient, Microsoft.Data.Sqlite, Npgsql
.NET 5.0 is added to the list of available Target Framework versions in Create Model Wizard and Model Settings in EF6 and EF Core 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 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 partial method is added to the OnModelCreating(DbModelBuilder modelBuilder) method generated by DbContext template of EF model
The design time connection via Microsoft.Data.SQLite is supported for creating EF Core Model in standalone and console versions of Entity Developer
The generation of a class inherited from DbConfiguration in EF 6.4 is added to .NET Core/.NET Standard projects (Npgsql/Firebird)
The DbProviderFactories and DbProviderServices registrations are implemented in Create Model Wizard of EF6 models for System.Data.SQLite and FirebirdSql.Data.FirebirdClient providers in .NET Framework and .NET Core/.NET Standard projects
The new property Target Framework is added to Create Model Wizard and Model Settings of EF6 models
The list of providers (packages) loaded by Create Model Wizard in EF6 models is extended
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 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
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 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 Visual Studio validation of EF 6.4 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 adding entities to conceptual part of EF6 model created using Npgsql or System.Data.SQLite 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
Only for V.I.P Warning! You are not allowed to view this text.