Entity Developer 6.11 is released!

Discussion of open issues, suggestions and bugs regarding Entity Developer - ORM modeling and code generation tool
Locked
Devart
Site Admin
Posts: 3772
Joined: Tue 26 Oct 2004 13:51

Entity Developer 6.11 is released!

Post by Devart » Fri 02 Apr 2021 12:08

Dear users,

Devart is glad to announce the release of Entity Developer 6.11 – a visual ORM designer for a wide variety of ORMs. The new version introduces support for Entity Framework Core 6, greatly improves serialization support adding support for more formats, and offers a number of usability improvements.

Entity Framework Core 6 Support

We have added support for Entity Framework Core 6.0, which is currently available as Preview versions, to Entity Developer, so now you can design EF Core 6 models for this providers with our designer.

Note that you must have .NET 5 or .NET 6 as the target framework for your project if you want to use Entity Framework 6.0.

Serialization Support

The following Entity Developer templates now support not only Data Contract serialization, but also serialization to JSON and YAML formats: Data Transfer Objects (for all ORMs), EF Core (for Entity Framework Core), and DbContext (for Entity Framework v4 - v6). They now support the following serializations and serialization libraries:
  • Data Contract – for serialization with the DataContractSerializer class.
  • JSON serialization via either Newtonsoft.Json or Microsoft.Text.Json libraries.
  • YAML serialization via the YamlDotNet library.
These templates also provide properties for selecting serialization library and determining which navigation properties to serialize. They also provide extended properties for excluding certain entity properties from serialization, and providing a custom name for serialization.

EF Core and DbContext templates also allow users to specify whether to use original column names and not entity property names for serialization and whether to serialize NULL values.

JSON Data Types Support in EF Core Models

We have extended the list of supported data types in Entity Developer and added the following JSON types: JsonDocument and JsonElement from System.Text.Json and JObject and JToken from Newtonsoft.Json.Linq.

This is not all, to know more about new features of Entity Developer please read our blog article.

Here is the complete list of Entity Developer 6.11.1213 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:
    • 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
    • The new extended property Do Not Serialize is added for properties and navigation properties to exclude them from serialization
    • The new extended property Serialization Name is added for properties and navigation properties to set custom names in serialization
    • The behavior is changed: WCF Data Contract Attributes is set to False by default now
  • The bug with creating app.config in Visual Studio .NET Core projects is fixed
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)
    • The new template property Serialization Library is added for specifying the library used for serialization
    • The new template property Serialize Original Column Names is added for controlling the appearance of original column names in serialization
    • The new template property Serialize Navigation Properties is added for controlling the appearance of navigation properties in serialization
    • The new template property Serialize Null Value is added for managing the behavior of nullable properties
    • The new extended property Do Not Serialize is added for properties and navigation properties to exclude them from serialization
    • 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:
    • the Generate Data Contracts property of the EF Core template
    • the Do Not Generate Data Contract Attribute extended property of navigation properties in EF Core Model
    • the WCF Data Contract Attributes property of the DbContext and Data Transfer Object templates
    • the WCF DataMember Attribute on Navigation Properties property of the DbContext and Data Transfer Object templates
  • The bug with loading Oracle.ManagedDataAccess.Core v3.21.1 (.NET Standard 2.1) by the Entity Developer version integrated into Visual Studio is fixed using the workaround with loading previous ODP.NET version from local NuGet cache
  • The bug with incorrect detecting DatabaseGeneratedOption.Identity for the properties with DEFAULT NULL in a database, when "Detect function-based column default value" is selected in Create Model Wizard, is fixed in EF4/EF5/EF6
  • The bug with detecting the existing classes with QueryType=True by Update From Database Wizard in EF Core Model is fixed
  • The bug with code generation for Npgsql, when the timetz column is mapped to a class property of type other than DateTimeOffset, in EF Core Model is fixed
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 development team
http://www.devart.com/entitydeveloper/

Locked