Devart Entity Developer 7.2 new features
| • | Visual Studio 2022 version 17.9 Preview is supported |
| • | The new option "Show System Schemas" (by default, False) is added to Servers' Options -> SQL Server. If the "Show System Schemas" check box is selected, database objects from system schemas will be retrieved (SQL Server) |
| • | The new option "Retrieve Cross Schema Relations" (by default, True) is added to Servers' Options -> SQL Server. If the "Retrieve Cross Schema Relations" check box is selected, foreign keys from different schemas will be retrieved. This can take much time (SQL Server) |
Entity Framework support
| • | Entity Framework Core 8 is supported |
| • | .NET 8 is added to the list of available Target Framework versions in Create Model Wizard and Model Settings in EF and EF Core models |
| • | The new extended property Do Not Generate OnConfiguring Method is added for the model in EF Core Model |
|
Devart Entity Developer 7.1 new features
| • | Visual Studio 2022 version 17.5 Preview is supported |
| • | Visual Studio 2022 version 17.6 Preview is supported |
| • | Visual Studio 2022 version 17.7 Preview is supported |
| • | Entity Framework Core 7.0 is supported |
| • | The behavior is changed: the primitive properties by default have Inheritance Modifier = None |
| • | The Temporal configuration section is added to class properties in EF Core 6 and higher models (SQL Server) |
| • | The Triggers configuration option is added to class properties in EF Core 7 models (SQL Server) |
| • | Retrieving metadata of table triggers by Create Model Wizard and Update From Database Wizard is supported in EF Core 7 models (SQL Server) |
Entity Framework support
| • | The new extended properties Do Not Generate Serializable Attribute and Do Not Serialize are added for complex types in EF Core Model |
|
Devart Entity Developer 7.0 new features
| • | Windows 11 is supported. |
| • | Visual Studio 2022 version 17.2 is supported. |
| • | Visual Studio 2022 version 17.3 Preview is supported. |
| • | The behavior is changed: Entity Developer default installation path has changed from C:\Program Files (x86)\Devart\Entity Developer to C:\Program Files\Devart\Entity Developer. |
| • | 64-bit version of standalone Entity Developer application is added. |
| • | 64-bit version of console Entity Developer application is added. |
|
Devart Entity Developer 6.12 new features
| • | The new property Validation Framework is implemented in the Data Transfer Object template for generating DataAnnotations attributes |
Entity Framework support
| • | 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 Uri data type is supported in EF Core Model |
| • | The DateOnly and TimeOnly data types are supported in EF Core 6 models (SQL Server, SQLite) |
| • | 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 behavior is changed: if Target Framework is set to .NET 5 in Model Settings of EF Core Model in Visual Studio, EF Core 6 is no longer available as an option of EF Core version |
| • | 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 |
| • | 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 |
|
Devart Entity Developer 6.11 new features
| • | Visual Studio 2019 version 16.10 Preview is supported |
| • | 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 Data Transfer Object template is improved: |
| o | 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 |
| o | The new extended property Do Not Serialize is added for properties and navigation properties to exclude them from serialization |
| o | The new extended property Serialization Name is added for properties and navigation properties to set custom names in serialization |
| o | The behavior is changed: WCF Data Contract Attributes is set to False by default now |
| • | The new hotkey Alt+E is implemented in Property Editor for opening Column Editor in EF Core Model, NHibernate Model, Telerik Data Access Model |
| • | Schemas of type E (External Login from Azure Active Directory) are supported in Create Model Wizard / Update From Database / Update To Database (SQL Server) |
| • | Detection of GENERATED ALWAYS AS ROW START and GENERATED ALWAYS AS ROW END columns in SQL Server 2016 and higher by Create Model Wizard / Update From Database Wizard is implemented |
| • | The behavior of the Regenerate Storage and Mapping functionality in EF Core, NHibernate, and Telerik Data Access models 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 |
Entity Framework support
| • | 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) |
| o | The new template property Serialization Library is added for specifying the library used for serialization |
| o | The new template property Serialize Original Column Names is added for controlling the appearance of original column names in serialization |
| o | The new template property Serialize Navigation Properties is added for controlling the appearance of navigation properties in serialization |
| o | The new template property Serialize Null Value is added for managing the behavior of nullable properties |
| o | The new extended property Do Not Serialize is added for properties and navigation properties to exclude them from serialization |
| o | The new extended property Serialization Name is added for properties and navigation properties to set custom names in serialization |
| • | .NET 6.0 is added to the list of available Target Framework versions in Create Model Wizard and Model Settings in EF Core and EF6 models |
| • | Entity Framework Core 6.0 is supported for Microsoft.Data.SqlClient, Microsoft.Data.Sqlite, Npgsql |
| • | The new package MySql.EntityFrameworkCore is used now for MySQL Connector .NET in EF Core 3 and EF Core 5 |
| • | EF Core 5 is supported for FirebirdSql.Data.FirebirdClient and Pomelo.EntityFrameworkCore.MySql |
| • | EF Core Spatial Data (NetTopologySuite) is supported for Pomelo.EntityFrameworkCore.MySql |
| • | 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 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 |
| • | Newtonsoft.Json.Linq (JObject and JToken as property types) is supported for Pomelo.EntityFrameworkCore.MySql in EF Core Model |
| • | System.Text.Json (JsonDocument and JsonElement as property types) is supported for Pomelo.EntityFrameworkCore.MySql and Npgsql in EF Core Mode |
| • | 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 following properties are marked as obsolete: |
| o | the Generate Data Contracts property of the EF Core template |
| o | the Do Not Generate Data Contract Attribute extended property of navigation properties in EF Core Model |
| o | the WCF Data Contract Attributes property of the DbContext and Data Transfer Object templates |
| o | the WCF DataMember Attribute on Navigation Properties property of the DbContext and Data Transfer Object templates |
| • | 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 |
| • | EF Core 6 is added to the list of available values of the Entity Framework version property in Model Settings of EF Core Model for Pomelo.EntityFrameworkCore.MySql |
LINQ to SQL support
| • | The new option "Read-only computed columns" is added to Model Settings for controlling value of the Read Only attribute of class properties created for computed columns (SQL Server) |
|
Devart Entity Developer 6.10 new features
| • | 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 |
Entity Framework support
| • | Entity Framework Core 5.0 is supported |
| • | The new features are supported in Entity Framework 5.0: |
| o | Many-to-many associations |
| o | The new types of properties IPAddress and PhysicalAddress |
| • | The Model Refactoring functionality is supported for classes in EF Core Model |
| • | The HierarchyId data type is supported via EntityFrameworkCore.SqlServer.HierarchyId nuget package for EF Core 3 and EF Core 5 (SQL Server) |
| • | The IPAddress and PhysicalAddress data types are supported in EF Core Model (Npgsql) |
| • | 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 |
| • | 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 %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 |
| • | 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 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 |
|
Devart Entity Developer 6.9 new features
| • | Visual Studio 2019 version 16.8 Preview is supported |
| • | PostgreSQL 13 is supported |
| • | Schemas of type A (Application role) are supported in Create Model Wizard / Update From Database / Update To Database (SQL Server) |
| • | 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 |
Entity Framework support
| • | EF Core spatial data types support is improved: in addition to Geometry and Geography, specific .NET NetTopologySuite types like GeographyPoint, GeographyLine are now available property types (MySQL, Oracle, PostgreSQL, SQLite) |
| • | The default mapping for spatial data types in Server's Options is updated (MySQL, SQLite) |
| • | Pomelo.EntityFrameworkCore.MySql is supported in EF Core Model for connecting to MySQL and MariaDB |
| • | "Async MySQL ADO.NET Connector" is added to the list of available providers in EF Core Model ("MySqlConnector" NuGet package) |
| • | FirebirdSql.EntityFrameworkCore.Firebird is supported in EF Core Model for connecting to Firebird |
| • | "FirebirdClient" is added to the list of available providers in EF Core Model ("FirebirdSql.Data.FirebirdClient" NuGet package) |
| • | Support for "Microsoft SQL Server Compact Data Provider 3.5" and "Microsoft SQL Server Compact Data Provider 4.0" is improved |
|
Devart Entity Developer 6.8 new features
| • | 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: |
| o | Import of stored procedures and functions via Create-Model command is supported |
| o | 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 |
| o | The new option --Execute is added to Create-Model command for executing procedures/functions to get metadata from result set |
| o | The asterisk symbol (*) is supported in --Tables and --Views parameters of Create-Model to include all objects |
| • | 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 |
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 |
| o | C# DbContext template of Devart Entity Model when ImplementINotifyPropertyChanging=False and ImplementINotifyPropertyChanged=False and PropertyChangePartialMethods=False |
| o | 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 |
|
Devart Entity Developer 6.7 new features
| • | Command-line interface is implemented in a standalone Entity Developer |
| • | 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 |
| • | The compatibility with dotConnect providers is improved: provider's package loaded via NuGet is registered in Entity Model, EF Core Model, and NHibernate Model with no need to run the dotConnect installation |
| • | The ability to search for available providers in local NuGet cache is implemented in a standalone Entity Developer for Entity Model, EF Core Model and NHibernate 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 |
Entity Framework support
| • | "ODP.NET, Managed Driver" is added to the list of available providers in EF Core Model |
| • | 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 |
NHibernate support
| • | Devart NHibernate Model is supported in .NET Standard / .NET Core projects |
|
Devart Entity Developer 6.6 new features
| • | PostgreSQL 12 is supported |
| • | The "Optimize rendering for screens with different pixel densities" feature of Visual Studio 2019 is supported |
| • | The 12cR2 option is added to the list of available Oracle versions in Model Synchronization Settings |
| • | Graph tables in SQL Server 2019 are supported (SQL Server) |
| • | The behavior is changed: columns with IsHidden=1 in SQL Server 2019 are ignored by Create Model Wizard (SQL Server) |
Entity Framework support
| • | Entity Framework Core 3.0 is supported |
| • | Entity Framework Core 3.1 is supported for projects with target framework .NET Core 2.x/3.x, or .NET Standard 2.x, or .NET Framework 4.6.1 and higher |
| • | Entity Framework 6.3 is supported |
| • | Entity Framework 6.4 is supported |
| • | The DbContext template is improved for using Entity Framework 6.3: |
| o | The "Configuration Type Name" property, which specifies the descendant of DbConfiguration class that should be used for code-based configuration, is added |
| o | The "Use DbConfigurationType Attribute" property, which determines whether to register the configuration type specified in the ConfigurationTypeName property of the DbConfigurationType attribute, is added |
| o | With UseDbConfigurationTypeAttribute=false, the static constructor for registering factory and the new partial method OnStaticConfigured are generated |
| • | The DbContext template is improved: precision and scale for database types are generated now in EF4/EF5/EF6 models when Fluent Mapping=True and Mapping Generation Strategy=UseAttributes |
| • | 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 |
| • | Support for spatial types in EF Core is added (SQL Server) |
| • | 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 |
|
Devart Entity Developer 6.5 new features
| • | The integration with Visual Studio 2019 is improved: now the installation detects both 2019 Release and 2019 Preview versions |
| • | The behaviour is changed: a plural form of names ending with "s" now has a longer version (for example, status -> statuses) |
Entity Framework support
| • | Entity Framework 6.3 Preview 9 is supported for projects with target framework .NET Core 3 or .NET Standard 2.1 |
|
Devart Entity Developer 6.4 new features
| • | Visual Studio 2019 is supported |
| • | Deprecated Synchronous API calls are no longer used with Visual Studio 2019 |
| • | The ability to disable generation of the byte order mark (BOM) in the beginning of code files in a standalone Entity Developer is implemented |
| • | The time to wait while trying to retrieve metadata before terminating the attempt and generating an error by Create Model Wizard / Update From Database Wizard / Update To Database Wizard is increased to 180 seconds for SQL Server |
|
Devart Entity Developer 6.3 new features
| • | Visual Studio 2019 Release Candidate 4 is supported |
| • | Using an extended property of type OutputInfo is supported |
| • | Code generated for nullable properties is simplified: now T? is generated instead of System.Nullable<T> |
| • | PostgreSQL 11 is supported |
Entity Framework support
| • | Entity Framework Core 2.1 is supported |
| o | Query type support is added: classes now have the Query Type property, and if it is set to true, this class is generated as a query type |
| o | Lazy loading for Entity Framework Core 2.1 is supported: |
| ▪ | Model now has the Use Lazy-Loading Proxies property, which enables lazy loading on the model level |
| ▪ | Navigation properties now have the Lazy property, which enables lazy loading for a specific navigation property |
| o | Properties now have the Constructor Parameter property, for configuring a parametrized constructor of the class |
| o | An additional constructor that accepts DbContextOptions as an argument is added to the DbContext class descendant in the VB.NET version of the DbContext template for EF Core. |
| • | The "Include Environment Variables" property, determining whether context configuration will be extended with environment variables when a connection string from the appsettings.json file is used, is added to the EF Core template |
| • | The "Json File Base Path" property, specifying the base path for file-based providers when a connection string from the appsettings.json file is used, is added to the EF Core template |
| • | The new Generate GeneratedCode Attributes option (by default, False) is added to the DbContext template in EF4/EF5/EF6 and the EF Core template |
| • | The new Generate Dummy Comments option (by default, False) is added to the DbContext template in EF4/EF5/EF6 |
| • | The code formatting is fixed in the DbContext template in EF4/EF5/EF6 and the EF Core template |
| • | The code generation of a default value for the String property mapped to the column with a default value, that contains a unicode literal with N-prefix, is supported in EF and EF Core |
| • | The code generation of DateTime.Now for the DateTime property mapped to the column with the default value SYSDATETIME() is supported in EF and EF Core |
| • | The code generation of DateTime.UtcNow for the DateTime property mapped to the column with the default value GETUTCDATE() or SYSUTCDATETIME() is supported in EF and EF Core |
| • | The code generation of DateTimeOffset.Now for the DateTimeOffset property mapped to the column with the default value SYSDATETIMEOFFSET() or GETDATE() is supported in EF and EF Core |
| • | The code generation of DateTimeOffset.UtcNow for the DateTimeOffset property mapped to the column with the default value GETUTCDATE() or SYSUTCDATETIME() is supported in EF and EF Core |
| • | The code generation of a default value for the Guid property mapped to the column with the default value NEWID() or NEWSEQUENTIALID() is supported in EF1/EF4/EF5/EF6 |
| • | The code generation of a default value for the Boolean property mapped to the column with the numeric default value is supported in EF1/EF4/EF5/EF6 |
| • | The multiple select functionality in EF Core Model is improved: now it allows setting PrimaryKey, ValueGenerated, Concurrency for several properties simultaneously |
NHibernate support
| • | The possibility to set parameters for Generator=native is implemented |
|
Devart Entity Developer 6.2 new features
| • | The .NET Standard 2.0 projects in Visual Studio 2017 are supported |
| • | The .NET Core 2.0 projects in Visual Studio 2017 are supported |
| • | The macaddr8 data type introduced in PostgreSQL 10 is supported |
| • | The usage of long identifiers (up to 140 symbols) for naming model objects is supported |
| • | The ModelNameAsFilesPrefix property is implemented in the RepositoryAndUnitOfWork template |
| • | Identity columns in PostgreSQL 10 are supported |
| • | The new Retrieve Cross Database Relations option is implemented in Model Settings for detecting FK relations between tables in different databases (MySQL) |
Entity Framework support
| • | Entity Framework Core 2.0 is supported |
| • | The Retrieve Data functionality via Model Explorer for EF Core 2 is implemented |
| • | The new "Detect function-based column default value" option is implemented in Model Settings of EF Core model |
| • | The code generation for async method calls is added to the EF Core template |
| • | The code generation for async method calls in the EF Core template is improved |
| • | Support for ASP.NET Core MVC is added to the MVC Controller template |
| • | Support for ASP.NET Core MVC is added to the Data Annotations Metadata template |
| • | The new SQL Type, Size, Precision, Scale options are added to the Parameters tab in Method Editor of EF Core Model |
| • | The new Controller Area extended class property is added to EF Core Model |
| • | The check of conditions for setting optionsBuilder.Use... in the generated OnConfiguring method by the EF Core template is improved |
| • | The process of synchronizing methods and parameters with database stored procedures in EF Core Model is improved |
NHibernate Support
| • | The new Unimplemented class property is added for using the Dynamic Models functionality |
| • | Support for formulas in navigation properties is added |
|
Devart Entity Developer 6.1 new features
| • | Visual Studio 2017 is supported |
| • | The .NET Core projects in Visual Studio 2017 are supported |
| • | The Snake case in both Model and Database naming rules is supported via the new "Add underscore" option |
Entity Framework support
| • | The new Raw SQL Query class property and SQL method property with the corresponding editors are implemented in Entity Framework Core |
| • | The behaviour is changed: IsRequired(false / true) for navigation properties is always generated in EF Core fluent mapping now |
|
Devart Entity Developer 6.0 new features
| • | Visual Studio 2017 Release Candidate 4 is supported |
| • | The DbProviderFactory provider registration in application's *.config is supported by the Entity Developer version integrated into Visual Studio |
| • | The possibility to set values of stored procedure parameters for getting metadata to generate automatically the corresponding complex type is implemented |
| • | The possibility to choose whether to add new entities to a diagram or not in Update From Database Wizard is implemented |
| • | The default behaviour is changed: bit(2..8), bit(9..16), bit(17..32) are mapped to Byte, Int16, Int32 correspondingly by Create Model Wizard and Update Model From Database Wizard (MySQL) |
Telerik Data Access support
| • | Telerik Data Access support is added |
NHibernate support
| • | NHibernate Loquacious API for mapping by code is supported |
| • | The IsExternal functionality is supported for the complex types |
| • | The behaviour is changed: the type definitions (typedef) are generated now in XML mapping files of each class, which uses the typedefs, if the Xml Mapping File Per Class template property is set to True |
| • | The behaviour is changed: CustomSqlType in fluent mapping now includes a detailed information (length, precision, scale) |
Entity Framework support
| • | Entity Framework Core 1.0 RTM is supported |
| • | The generation of static methods by the EntityObject template is supported via the new property Direct Call of EntityMethod |
| • | The MySQL Connector/Net support is added for Entity Framework Core models |
| • | The behaviour is changed: the ObservableCollection navigation properties are initialized now in a default class constructor |
| • | The behaviour is changed: now the DbContext template generates an additional partial class for the context class when "File Per Class" and "Generate Partial Class" are set to True |
|
Devart Entity Developer 5.8 new features
| • | Visual Studio 2015 is supported |
| • | The support for materialized views is implemented (Oracle) |
NHibernate support
| • | The behaviour is changed: now the database comments are generated via the Update Database From Model and Generate Database Script From Model wizards (PostgreSQL) |
Entity Framework support
| • | The Use ObservableCollection property of the DbContext template is implemented |
LINQ to SQL support
| • | The behaviour is changed: now 1:1 and 1:0..1 associations are displayed differently on the diagram |
|
Devart Entity Developer 5.7 new features
| • | Visual Studio 2015 Release Candidate is supported |
| • | Visual Studio 2013 is supported |
| • | SQL Server 2014 is supported |
| • | The possibility to use relative paths to assemblies in code generation templates is implemented |
| • | The Remove Invalid Characters option (by default, True) is added to the Model Naming rules; if it is set to False, all invalid characters will be replaced with underscores |
| • | The behaviour is changed: installation with the /VERYSILENT install parameter will uninstall the other version of the product without any dialog box if it is installed |
| • | The behaviour is changed: the values of "Target Server" and "Server Version" can be reset via the Model Settings > Synchronization > Mapping dialog despite the fact whether connection is specified in Database Explorer or not |
| • | The behaviour is changed: now replication stored procedures are not shown on the "Select database objects" step of the Create/Update Model From Database wizard (SQL Server) |
| • | The behaviour is changed: now paths to assemblies with attributes (Model Settings -> Model -> Attributes) are saved and used as relative paths |
| • | The behaviour is changed: now by default VARCHAR(8000) / NVARCHAR(4000) columns, instead of VARCHAR(MAX) / NVARCHAR(MAX), correspond to the string properties in the model |
| • | The behaviour is changed: Generate Database Script From Model saves the output in ASCII format if there are no unicode symbols in the script; UTF-8 is used otherwise |
NHibernate support
| • | NHibernate 4 is supported |
| • | The NHibernateV3Compatible option in the NHibernate templates is implemented |
| • | The Generate Serializable Attribute property of classes and complex types is implemented |
| • | The support of mapping a string representation of enum to the string fields in database is implemented |
| • | Oracle Managed Data Provider for .NET is supported |
| • | The Generate Partial Class option in the Fluent NHibernate template is implemented |
| • | The Generate Serializable Attribute property is added to the NHibernate template |
| • | The Do Not Generate Cloneable Attribute extended property of classes and complex types is implemented (by default, false) |
| • | The Natural Id property of HibernateProperty in fluent mapping is supported |
| • | The possibility of setting default values for enum properties is implemented |
| • | The behaviour is changed: the Generate Serializable Attribute extended property of classes and complex types is renamed to Do Not Generate Serializable Attribute (by default, false) with changing its logic correspondingly |
| • | The behaviour is changed: the "Regenerate Storage and Mapping" option clears existing mapping settings to make NHibernate runtime to use default storage values |
| • | Code generation for model classes is improved: the initialization of the properties, having default values, when creating classes is added |
Entity Framework support
| • | Entity Framework 6 is supported |
| • | Oracle Managed Data Provider for .NET is supported |
| • | The new "Provider Manifest Token" model property is implemented to identify the target server |
| • | The "WCF DataMember Attribute on Navigation Properties" property is added to the Data Transfer Object template for pointing the end (-s) where the attribute should be generated |
| • | The Implement Equals property is added to the DbContext, ObjectContext, and POCO Entity templates |
| • | The override modifier for DbSet class properties generated by DbContext templates is added |
| • | The View Generation option of the model with Entity Framework version = Entity Framework 6 is supported for the DbContext (only with XML mapping), EntityObject, POCO, and Self-Tracking Entities templates |
| • | The Enable WinForms Data Binding property of the DbContext template is implemented |
| • | The Property Change Partial Methods property of the DbContext template is implemented for generating partial methods On%PropertyName%Changing and On%PropertyName%Changed for each primitive property of entity classes |
| • | More information messages, when validating EF6 models basing on the EntityFramework.dll functionality, are added |
| • | The behaviour is changed: now partial configuration classes are generated when DbContext template is used with Fluent Mapping=True and Mapping Generation Strategy=UseConfigurationClasses options |
| • | The behaviour is changed: the validation of EF6 models depends on the EntityFramework.dll functionality only (.NET Framework 4.5 is not required any more) |
| • | The behaviour is changed: now a property in the generated code is initialized basing on the default value in CSDL only (instead of default values in any of SSDL and CSDL) |
| • | The behaviour is changed: now the default values are not set for string properties, that correspond to fields with the default values like expressions |
| • | The information message about availability of NuGet Package Manager on the workstation is added in the Entity Developer version integrated into Visual Studio |
LINQ to SQL support
| • | The possibility of setting default values for enum properties is implemented |
|
Devart Entity Developer 5.6 new features
NHibernate support
| • | The behaviour is changed: "Generate Database Script"/"Update Database From Model" wizards generate columns with the identity clause 'GENERATED AS IDENTITY' for auto-generated primary key properties (only for Oracle 12c) |
Entity Framework support
| • | The behaviour is changed: "Generate Database Script"/"Update Database From Model" wizards generate columns with the identity clause 'GENERATED AS IDENTITY' for properties with 'Store Generated Pattern=Identity' (only for Oracle 12c) |
|
Devart Entity Developer 5.5 new features
| • | Visual Studio 2013 Release Candidate is supported |
| • | A new MVC Controller template, generating a ASP.NET MVC controller with data access code, is added |
| • | A new MVC View Advanced template, generating an ASP.NET MVC view based in Twitter Bootstrap, is added |
| • | A new Data Transfer Object template for DTO classes generation is implemented |
| • | A new Data Annotation Metadata template, generating Data Annotation metadata classes and decorating classes and properties with data annotation attributes for validation, presentation and defining metadata, is added |
| • | The "Regenerate Storage and Mapping" option for regenerating model parts, specific to the database server, is added to the diagram shortcut menu |
| • | Add Template dialog box is improved |
| • | The "WCF DataMember Attribute on Navigation Properties" property is added to the DbContext and POCO templates for pointing the end (-s) where the attribute should be generated |
| • | The Save and Refresh buttons for persisting and reloading changes to / from a database are added to the Retrieve Data grid |
| • | The Refresh option in the Attributes tab of the Model Settings window is implemented; it updates the list of available attributes types in the referenced assemblies |
| • | The capability to modify custom attributes for several selected entities or properties at the same time is implemented |
| • | The capability to cancel metadata reading in wizards and Database Explorer is added |
| • | The "Recreate Database Tables" check box, which allows to drop and recreate database tables, is added to the "Update To Database" wizard |
| • | The "Include Drop" check box for including DROP commands for database objects to the generated script is added to Generate Database Script Wizard |
| • | A new shortcut menu command "Include Related", which allows making a copy of the related objects in the specified diagram, is added |
| • | A new shortcut menu command "Add To Model with Related", which allows adding tables, related to the selected one, to the model, is added to the shortcut menu of tables in Database Explorer |
| • | A new shortcut menu command "Add On Diagram With Related", which allows creating an object and all the objects related to it on a diagram, is added to the shortcut menu of classes, complex types, and enums in Model Explorer |
| • | New "Simple" diagram skin is added for displaying a diagram in metro style |
| • | The "Default Width" diagram property for specifying the default width for newly created diagram shapes (entities, complex types and enums) is added |
| • | The user interface of Express Edition concerning availability of custom templates is improved |
| • | The "Model Name As Files Prefix" property is implemented for the templates which generate classes for model entities |
| • | The possibility of adding custom attributes to enum members is implemented |
| • | The "Close the window when the generation completes successfully" option in the Generation Process window is implemented in the standalone Entity Developer |
| • | The behaviour is changed: the possibility to exclude the generation of keys (primary, foreign) in "Update Database From Model" and "Generate Database Script From Model " wizards is added |
| • | The behaviour is changed: now by default MVC Controller template generates files in the model folder, MVC View Advanced template creates files in the Views model subfolder |
| • | The behaviour is changed: a table storage engine is not set explicitly in the generated DDL (MySQL) |
| • | The behaviour is changed: the PostgreSQL limitation in 63 character for identifier names is taken into account when the SQL script is generated by Update Database From Model / Generate Database Script wizards |
| • | The behaviour is changed: a string default value for the property can be set without quotes in the Properties window |
| • | The behaviour is changed: now, when creating a new TPH discriminator column in Inheritance Editor, it has the string type by default |
| • | The behaviour is changed: the error is generated if the Abstract inheritance modifier is set for the class which is involved in the Table Per Type inheritance |
| • | The behaviour is changed: empty value is used in property editors instead of -1 for marking facets of class property without assigned value |
NHibernate support
| • | The support for enums declared in external assemblies is implemented |
| • | The capability for setting special rules for generating default names of newly-created database columns, which correspond to complex type's properties, when using the Model First approach is implemented |
| • | The capability to customize properties that are automatically added when creating a new entity is added (a new Initialization page is added to the Model->General section of the Model Settings dialog box) |
| • | Class Editor is improved: the capability to edit extended property settings, such as validation and presentation, is added |
| • | Type Editor is improved: the capability to edit extended property settings, such as validation and presentation, is added |
| • | The Column Editor is improved: now default settings for database columns, such as Not Null, Unicode, Precision and Scale, are displayed in the dialog box |
| • | The Inheritance Modifier property of HibernateProperty and HibernateRelationProperty is implemented |
| • | The GenerateDummyComments template property for suppressing generation of dummy comments for each class and its members is implemented |
| • | The behaviour is changed: System.DateTime .NET structure is mapped to TIMESTAMP database type when using Model First approach (PostgreSQL) |
Entity Framework support
| • | A new WCF RIA Domain Service template, generating a WCF RIA Services domain service class for a Devart Entity Framework model is added |
| • | The Namespace property of class, complex type, enum is implemented |
| • | The Entity Container Namespace properties of the model is implemented |
| • | The design time support for model-defined functions is added |
| • | The support for enums declared in external assemblies is implemented |
| • | The "Rewrite connection string during regeneration" option (default value is True) of model settings is added to provide the possibility to turn off modifying connection string in *.config after model is saved first time |
| • | The capability for setting special rules for generating default names of database objects when using the Model First approach is implemented (a new Advanced page is added to the Synchronization->Database Naming section of the Model Settings dialog box) |
| • | The capability to customize properties that are automatically added when creating a new entity, and options that are automatically set when creating a new property is added (a new Initialization page is added to the Model->General section of the Model Settings dialog box) |
| • | New setting "Detect Table Per Type inheritances", which enables automatic detection of TPT inheritances, is added for Create Model Wizard and model |
| • | Adding information to application's *.config file about cursors used in the model is implemented (Oracle Data Provider for .NET) |
| • | DbContext template is improved: a "WCF Data Contract Attributes" setting for generation of DataContract, KnownType, and DataMember attributes for classes and properties is added |
| • | DbContext template is improved: "Implement INotifyPropertyChanging" and "Implement INotifyPropertyChanged" template settings are added |
| • | DbContext template is improved: a new "Mapping Generation Strategy" property that determines the method of mapping generation is implemented |
| • | POCO template is improved: a new "WCF Data Contract Attributes" setting for generating DataContract, KnownType, and DataMember attributes for classes and properties is added |
| • | POCO template is improved: "Proxy Creation Enabled" setting is implemented |
| • | POCO template is improved: new template settings, "Implement INotifyPropertyChanging" and "Implement INotifyPropertyChanged", are added |
| • | Create Model Wizard is improved: it is now able to download and install the required 'EnityFramework' Nuget package for Entity Framework 6 models, and for models for Entity Framework 4 and 5 in case they use the DbContext template |
| • | The Storage Column Editor dialog box is improved: the possibility to specify different settings that were previously available only in the Properties docking window are implemented |
| • | Class Editor is improved: the capability to edit extended property settings, such as validation, presentation, and facets, is added |
| • | Type Editor is improved: the capability to edit extended property settings, such as validation, presentation, and facets, is added |
| • | Storage Entity Editor is improved: the capability to edit extended columns settings, such as facets, is added |
| • | The behaviour is changed: the validation error is not generated when an abstract class is used in Table Per Type inheritance |
| • | The behaviour is changed: auto-implemented properties are generated when DbContext template is used with ImplementINotifyPropertyChanged=False and ImplementINotifyPropertyChanging=False |
| • | The behaviour is changed: DatabaseGeneratedOption is always generated for EntityKey properties when using fluent mapping |
| • | The behaviour is changed: a default value for the "Detect Table Per Type inheritances" option in Model settings is set to False |
| • | The behavior is changed: now connection string is configured with the name of the assembly, where the model is located, in case when the context class is located in another assembly |
LINQ to SQL support
| • | A new WCF RIA Domain Service template, generating a WCF RIA Services domain service class for a Devart LINQ to SQL model is added |
| • | The Namespace property of a class and an enum is implemented |
| • | The capability for setting special rules for generating default names of database objects when using the Model First approach is implemented (a new Advanced page is added to the Synchronization->Database Naming section of the Model Settings dialog box) |
| • | The capability to customize properties that are automatically added when creating a new entity, and options that are automatically set when creating a new property is added (a new Initialization page is added to the Model->General section of the Model Settings dialog box) |
| • | The support for enums declared in external assemblies is implemented |
| • | Class Editor is improved: the capability to edit extended property settings, such as validation, presentation, and facets, is added |
| • | Type Editor is improved: the capability to edit extended property settings, such as validation, presentation, and facets, is added |
| • | The "Rewrite connection string during regeneration" check box of Model Settings is implemented to determine whether to overwrite the connection string in the project config file with the one, currently set in Entity Developer for the model, each time when regenerating code for the model |
| • | System.Data.Linq.Binary type is added to the "Type Mapping Rule Editor" |
| • | The behaviour is changed: "Save connection string in App.Config as" check box in Model Settings dialog box is renamed to "Use connection string from App.Config as" |
| • | The behaviour is changed: the possibility to add one-to-one associations with nullable foreign key properties is added |
|
Devart Entity Developer 5.0 new features
| • | The functionality of ignoring columns in the database in the "Update To/From Database" wizards if they were omitted once before is implemented |
| • | Warnings about objects that are not mapped are added |
| • | A SHIFT+DELETE keyboard shortcut for deleting entity, complex type, or enum from diagram only is added |
| • | An INSERT keyboard shortcut for creating a new entity, adding property to the selected entity/complex type or new member to enum is added |
| • | The possibility to view notes, added through the "Documentation" property, for all the diagram objects via hints is implemented |
| • | Hints for diagram objects are improved |
NHibernate support
| • | The Lazy property of the "one" end of an association is implemented |
| • | The "Include foreign key columns in the model" property of the model is implemented |
| • | The generation of XML documentation for the code, which is created by Entity Developer, is improved |
| • | DB2 database is supported |
| • | Model Refactoring feature is implemented; it speeds up creating complex types and Table Per Type and Table Per Concrete Type inheritances from several model entities |
| • | The behaviour is changed: .NET auto-properties are generated in code if both Property ChangeNotifiers and Property Change Partial Methods properties of a template are set to False |
Entity Framework support
| • | Entity Framework 6 Alpha 2 is supported |
| • | Third-party providers for Entity Framework models are supported |
| • | DB2 database is supported |
| • | Model Refactoring feature is implemented; it speeds up creating complex types and Table Per Type and Table Per Concrete Type inheritances from several model entities |
| • | Create Storage and Mapping command, that allows automatically creating of the corresponding storage part object and defining mapping, is added to the shortcut menu of classes, properties, and associations |
| • | Select Storage Object command, that allows quick navigation to the corresponding storage part object, is added to the shortcut menu of classes, properties, associations, and methods |
| • | The possibility to delete the corresponding storage part objects automatically when deleting conceptual model objects is added |
| • | The naming algorithm for the newly-created columns, which correspond to complex type's properties, when using the Model First approach is improved |
| • | The Property Editor dialog is improved: fast access to the editor of the corresponding storage object and the possibility to specify different settings that were previously available only in the Properties docking window are implemented |
| • | The Inheritance Editor dialog is improved: specifying Discriminator column for Table Per Hierarchy inheritance in the editor is implemented |
| • | The Class Editor dialog is improved: fast access to the editor of the corresponding storage object is implemented |
| • | The Method Editor dialog is improved: fast access to the editor of the corresponding storage object is implemented |
| • | The behaviour is changed: Configure Behaviour dialog is renamed to Stored Procedure Mapping; options for hiding inappropriate and mapped stored procedures are added |
| • | The behaviour is changed: Table Editor dialog is renamed to Storage Entity Editor |
| • | The behaviour is changed: Stored Procedure Editor dialog is renamed to Storage Procedure Editor |
| • | The behaviour is changed: Generate Database Script/Update Database From Model wizards generate column with the default value NEWSEQUENTIALID() for Guid property with 'Store Generated Pattern=Identity' |
| • | The behaviour is changed: warnings about tables/views without primary keys are written to Error List window when generating a model |
| • | The behaviour is changed: the EntityKey attribute is not assigned to each property of the class if there is no primary key in the corresponding table/view |
| • | The behaviour is changed: empty value is used in property editors instead of -1 for marking facets of Storage Column without assigned value |
LINQ to SQL support
| • | The behaviour is changed: Configure Behaviour dialog is renamed to Stored Procedure Mapping |
| • | The behavior is changed: now the 'Read Only' property is not set to true for autoincrement fields by default when creating/updating models |
|
Devart Entity Developer 4.7 new features
| • | Predefined template for generating Repositories and Unit of Work classes is added |
| • | Integration with Visual Studio refactoring for renaming model objects is implemented |
| • | The "Use Database Comments" option of Model Settings is implemented to determine whether comments for database objects, if supported by DBMS, will be used for model objects Documentation initialization and taken into account when executing model or database update operations |
| • | The "Implement IClonable" option for the generated classes based on the model entities is added to all templates |
| • | The support of SQL Server Compact 4.0 is added |
NHibernate support
| • | Firebird database support is implemented |
| • | The possibility to work with the subselect query is implemented |
| • | The behaviour is changed: the possibility to set Collection Type and Collection Generic for all existing associations simultaneously when changing Default Collection Type and Default Collection Generic via Model Settings is implemented |
LINQ to SQL support
| • | The behaviour is changed: the "Save connection string in App.Config as" option is available in the standalone Entity Developer (the entry in App.Config must be added manually afterwards) |
| • | The possibility of editing a custom return type of a stored procedure via the Edit shortcut menu in Value Types Editor within Method Editor is added |
|
Devart Entity Developer 4.6 new features
| • | Visual Studio 2012 support is implemented |
NHibernate support
| • | The Retrieve Data feature for the NHibernate Fluent template is implemented |
| • | The behaviour is changed: when separating a set of fields into a complex type, the custom mapping is now created for these fields |
Entity Framework support
| • | The functionality of importing the scale and precision parameters of the decimal column into the EntityProperty is implemented |
|
Devart Entity Developer 4.5 new features
NHibernate support
| • | The support of Named SQL queries is implemented |
| • | The possibility to work with stored procedures is implemented |
| • | The support for the "Where" parameter of the hilo generator is added |
LINQ to SQL support
| • | The behaviour is changed: the warning, related to the missing property setter, is disabled |
| • | The behaviour is changed: for the association, in which the many-side entity hasn't the primary key, the code and the mapping are not generated |
| • | The behaviour is changed: the properties, that correspond autoincrement fields, are generated with a ReadOnly keyword in VB.Net |
|
Devart Entity Developer 4.4 new features
| • | The "Pluralize collection navigation properties" option for the possibility to turn off the pluralization of the many-end names of associations is implemented |
| • | Visual Studio 2012 Release Candidate is supported |
| • | The sticker notes for adding comments to diagrams are implemented |
| • | The possibility to add a stamp, specifying diagram author, company, version, copyrights, project name, and date, to a diagram is implemented |
| • | New Collapse All and Expand All menu commands for collapsing and expanding diagram shapes are added |
| • | The behaviour is changed: shortcut menu commands for working with diagram are grouped to the Diagram submenu of the shortcut menu |
| • | The behaviour is changed: the possibility to change diagram shape color via the corresponding Shape -> Color shortcut menu command is added |
| • | The behaviour is changed: when pasting a copied entity to a new diagram, a new entity is not created, the existing entity is added to this diagram |
| • | The behaviour is changed: when cutting an entity from the diagram, the entity is not cut from the model, only from the diagram |
NHibernate support
| • | The "Default Collection Generic" model option for setting the default value of the generic property of the collection navigation properties is implemented |
| • | The support of component navigation properties is implemented |
| • | The Parent property for component mappings is implemented |
| • | The possibility to specify default facets for the columns is implemented |
| • | The possibility to set path to NHibernate assemblies is implemented |
| • | The "none" option for the Access property is implemented |
| • | The behaviour is changed: only particular (not all) property characteristics are regenerated when using Update Model From Database wizard after the metadata of the corresponding column have been changed |
Entity Framework support
| • | The behaviour is changed: "Update Model From Database" wizard places newly added properties to the base abstract class now instead of putting them into child classes (where the mapping is) |
| • | The behaviour is changed: the CSDL property is left unchanged when the corresponding SSDL property is regenerated |
| • | The behaviour is changed: the association names are generated basing on the database FK names when using Database First approach |
LINQ to SQL support
| • | Support for Windows Phone 7 is added |
|
Devart Entity Developer 4.3 new features
| • | Visual Studio 11 Beta is supported |
| • | The copy/cut/paste functionality is added for objects of the conceptual part of a model |
| • | The possibility to drag&drop properties between classes in Model Explorer is implemented |
| • | The "HeaderTimestampVersionControlTag" generation template option is added for improving integration with version-control systems |
| • | The multiline popup editor for the Documentation.Summary property is implemented |
| • | The behaviour is changed: the Migrate option is added to the shortcut menu of property in Model Explorer |
| • | The behaviour is changed: entities and enums on the designer surface are more resizable now |
NHibernate support
| • | The merging of crossing foreign key columns in Table Per Hierarchy (TPH) when generating schema is added |
| • | The merging of crossing columns in Table Per Hierarchy (TPH) when generating schema is added |
| • | The warnings if merging of crossing columns in Table Per Hierarchy (TPH) when generating schema cannot be done correctly is added |
| • | The new "Unimplemented" extended property, which allows disabling code generation, is added for navigation properties |
| • | The "Generate" extended property, which allows disabling code generation for entity properties and complex type properties, is renamed to "Unimplemented" now |
| • | The default behaviour is changed: Discriminator Value is set to Not Null for base abstract classes by default now |
| • | The output order of the "Class" drop-down list elements for the "End 2" in the Association Editor is changed: classes and complex types are grouped to the corresponding groups |
|
Devart Entity Developer 4.2 new features
| • | Materialized view support is added |
| • | The shortcut menu options for deselecting changed/added/dropped tables are implemented for the root nodes in the "Update To/From Database" wizards |
| • | Capability for customizing the default Type Mapping Rules is implemented |
| • | Capability for setting diagram options either globally for all diagram documents or separately for a particular one is implemented: the Diagram Appearance and Printing options can now be set through the Options dialog box |
| • | Capability for setting such options as Environment, Diagram and Servers' to adjust the Entity Developer behavior, Model diagram behavior and Type Mapping Rules to your needs is implemented |
| • | Capability for setting and defining the class property validation rules based on different engines (Data Annotation, Enterprise Library, NHibernate Validator) is added |
| • | The documentation generation for navigation properties is implemented |
| • | The documentation generation for Enum members is implemented |
| • | The "Recreate Model" option, allowing to rebuild the model from a scratch, is added to the "Update Model From Database" wizard |
| • | The algorithm for forming the Navigation Properties names, when there are several FOREIGN KEY constraints between the same tables, is changed |
| • | The diagram design is changed: an arrow (instead of a triangle) is used on the tip of an association now |
| • | The behaviour is changed: database column comments are transfered to the Summary attribute of the Documentation property now |
| • | The behaviour is changed: the Navigation Property will not be displayed on the diagram and in Model Explorer if "Generate" is set to false for the appropriate association end |
| • | The behaviour is changed: the Validate Required attribute is synchronized with the Nullable attribute of Property by default now |
| • | The behaviour is changed: when selecting a property in the Model Explorer, the corresponding entity on the diagram does not expand if it is collapsed |
| • | The behaviour is changed: the DATETIME2 data type is now used for columns, corresponding to System.DateTime properties, for Microsoft SQL Server 2008 and later |
NHibernate support
| • | The support for collections of dependent objects is added |
| • | The new "Generate" extended property, which allows disabling code generation, is added for entity properties and complex type properties |
| • | The possibility to disable "hibernate-configuration" section generation in an application configuration file when saving a model is implemented |
| • | Synchronization with cascading updates and deletes basing on the foreign key constraints is supported |
| • | The ability to pre-define filter criteria and attach those filters at both a class level and a collection level is implemented |
| • | The new "ConstructorModifier" extended property, which allows controlling access for the class constructor, is added for entities and complex types |
| • | The possibility to generate extensibility partial On<property name>Changing and partial On<property name>Changed methods separately with the "PropertyChangePartialMethods" template property is added |
| • | The new messages for an inheritance validation are added |
| • | The behaviour is changed: the Inverse option on the many-side of a one-to-many relationship is set to True by default now |
| • | The behaviour is changed: "Getter Modifier" and "Setter Modifier" code generation properties are added for entity navigation properties instead of the "Modifier" property |
| • | The behaviour is changed: an implicit NOT NULL column attribute in SQL script is determined by the Nullable attribute of Property now |
| • | The behaviour is changed: the Validate Max Length attribute is synchronized with the Length attribute of Column by default now |
| • | The behaviour is changed: "Getter Modifier" and "Setter Modifier" code generation properties are added for entity properties instead of the "Modifier" property |
| • | The behaviour is changed: the field initialization code will create an object of the type, similar to the internal NHibernate type for this field |
| • | The behaviour is changed: the type of the Column.NotNull property is changed to System.Nullable<System.Boolean> and the property can accept three values: true, false and null |
Entity Framework support
| • | The HasStream attribute of entity types, which is used to retrieve binary data as a stream via Open Data Protocol, is supported |
| • | The "Detect function-based column default value" option for automatic setting StoreGeneratedPattern to Identity for corresponding columns is implemented (by default, false) |
| • | The GeneratePartialClass template property to generate a partial class, which will not be overwritten by the designer, for each class in the model is added |
| • | The possibility to rename the storage part of the model in Model Explorer is implemented |
| • | The behaviour is changed: the Validate Max Length attribute is synchronized with the Max Length attribute of Property by default now |
LINQ to SQL support
| • | The validation of method parameters is added |
| • | The behaviour is changed: the Validate Max Length attribute is synchronized with the Max Length attribute of Property by default now |
|
Devart Entity Developer 4.1 new features
| • | The possibility of specifying the name of the connection string to be saved in the application configuration file is implemented |
| • | New skins to improve the application appearance are implemented |
| • | Selection-driven highlighting is implemented |
| • | Capability for changing the shape color for entities, complex types and enums is implemented |
| • | Capability for selecting the diagram skin type is implemented |
| • | Changed behavior: when the FirstLetterUpperCase / FirstLetterLowerCase option is enabled in Naming rules, each letter after underscore will be capital/lower |
NHibernate support
| • | The capability for setting special rules for generating default names of database objects is implemented |
| • | Support for enumerated types ("enums") is implemented |
Entity Framework support
| • | Support for enumerated types ("enums") in Entity Framework June 2011 CTP models is implemented |
| • | Support for spatial data-types for Geography and Geometry in Entity Framework June 2011 CTP models is added |
| • | Import for selected stored procedures into the context model is implemented |
| • | Table-Valued Functions support is improved |
LINQ to SQL support
| • | Support for enumerated types ("enums") is implemented |
|
Devart Entity Developer 4.0 new features
| • | The possibility to export the diagram into an image file is added |
| • | The pluralization algorithm is improved when Naming rules are defined |
| • | The possibility to export the diagram into an image file is added |
NHibernate support
| • | NHibernate support is added |
| • | The possibility of configuring the second-level cache is added |
Entity Framework support
| • | The changes in the Entity name are now preserved by Update From Database Wizard |
| • | The possibility to restrict adding the connection string information to the application configuration file is added |
| • | The Entity Key handling for Views in Update From Database Wizard is improved |
LINQ to SQL support
| • | The possibility to restrict adding the connection string information to the application configuration file is added |
|
Devart Entity Developer 3.50 new features
| • | New Templates are added: |
| • | LINQ to SQL: POCO template with XML mapping generation |
| • | Entity Framework: POCO template, Self-Tracking template, DbContext template with fluent mapping generation |
| • | LinqConnect: POCO template with XML mapping generation |
| • | Templates usability is improved |
| • | Template Editor is significantly improved |
| • | Ability to declare additional properties for model objects is added |
| • | Ability to specify .NET attributes for model objects is added |
| • | The "Preserve schema name in storage" option is added |
|
Devart Entity Developer 3.20 new features
| • | Supported Visual Studio 2010 Service Pack 1 |
| • | Added possibility to split model into several diagrams for better handling of large models |
| • | Implemented possibility to disable automatic recognition of many-to-many associations |
| • | Added ConstraintSet property for Constraints in the Store part of the Entity Framework model |
| • | Added mapping for Function Import result types (Entity Framework v4 only) |
| • | Changed behavior: when adding two related entities with the corresponding properties having different types, an invalid association is created now |
|
Devart Entity Developer 3.00 new features
| • | Supported Visual Studio 2010 Service Pack 1 Beta |
| • | Added Update Model From Database functionality |
| • | Update To Database with Storage Synchronization functionality added |
| • | Added multiselect support for properties |
| • | Improved large models handling |
|
Devart Entity Developer 2.80 new features
| • | Added default bindings to entity fields in Insert(Update/Delete) MethodMappings |
| • | Added possibility of renaming associations in the model |
| • | Support for ADO.NET Entity Framework 4 added |
| • | Support for multi-result set methods added |
| • | Improved dialogs for editing model objects |
| • | Full integration with Visual Studio implemented |
| • | Added full support for ModificationFunctionMapping |
| • | Improved Find in Model functionality |
| • | Improved One-To-One associations handling |
|
Devart Entity Developer 2.50 new features
| • | New t4 like template engine with powerful editor added |
| • | Ability to generate separate files for classes |
| • | Entity Framework Pregenerated Views support added |
| • | Improved null handling code generation |
| • | Ability to execute LINQ and Entity SQL queries with data and native sql preview added |
| • | Ability to preview and edit data in Database Explorer added |
| • | Table splitting added (emulation of deferred loading for "large" datatypes in EF) |
| • | OnDelete support for associations added |
|
Devart Entity Developer 2.20 new features
| • | Advanced mapping with Entity Framework QueryView supported |
| • | Displaying of Navigation properties on diagram and Model Explorer implemented |
| • | Ability to change properties order added |
| • | Ability to edit Referential constraints added |
| • | Ability to set OnDelete action added |
| • | Ability to set Rows Affected parameter added |
| • | Added advanced search on the model |
| • | Added support for SQL Server CE |
| • | Added dialogs for suitable storage model editing |
| • | Added support for storing connections in the configuration files |
| • | Added Entity Set Pluralization Naming Rule |
|
Devart Entity Developer 2.00 new features
| • | Supported ADO.NET Entity Framework |
| • | Supported stored procedures and functions for LINQ to SQL |
| • | Entity Framework Complex Type supported |
| • | Entity Framework Storage Model editing supported |
| • | Many-to-Many associations retrieving added |
| • | Added naming rules for database objects |
| • | Added Visual Studio integration |
| • | Validation schema improved |
| • | Improved Database Explorer |
| • | Stability and performance improvements |
|
Send feedback on this topic
© 2008 - 2024 Devart. All rights reserved.