Entity Developer V6.11.1213

Released: Apr 1, 2021

Updates in V6.11.1213

Funktionen

  • Added support for Microsoft Visual Studio 2019 version 16.10 Preview.
  • Added the ability to ignore warnings during code generation.
  • Data Transfer Object template has been improved:
    • New Serialization Library property has been added for specifying the library used for serialization.
    • The extended property "Do Not Serialize" has been added to exclude properties and navigation properties from serialization.
    • The extended property "Serialization Name" has been added to set custom names for properties and navigation in serialization.
    • Behavior change: WCF Data Contract Attributes is now set to False by default.

Entity Framework support

  • The JSON (Newtonsoft.Json, Microsoft.Text.Json) and YAML (YamlDotNet) serializations are now supported in Entity Framework Core (via Entity Framework Core template) and Entity Framework 6 (via DbContext template).
  • Added new template property "Serialization Library" for specifying the library used for serialization.
  • Added new template property "Serialize Original Column Names" for controlling the appearance of original column names in serialization.
  • Added a new template property "Serialize Navigation" for controlling the appearance of navigation properties in serialization.
  • Added a new template property "Serialize Null Value" for managing the behavior of nullable properties.
  • Added a new extended property "Do Not Serialize" to exclude properties and navigation properties from serialization.
  • Added a new extended property "Serialization Name" to set custom names for properties and navigation in serialization.
  • Microsoft .NET 6.0 has been added to the list of available Target Framework versions in Create Model Wizard and Model Settings in Entity Framework Core and Entity Framework 6 models.
  • Entity Framework Core 6.0 is now supported for Microsoft.Data.SqlClient, Microsoft.Data.Sqlite and Npgsql.
  • The new package "MySql.EntityFrameworkCore" is now used for MySQL Connector Microsoft .NET in Entity Framework Core 3 and Entity Framework Core 5.
  • Entity Framework Core 5 is now supported for FirebirdSql.Data.FirebirdClient and Pomelo.EntityFrameworkCore.MySql.
  • Entity Framework Core Spatial Data (NetTopologySuite) is now supported for Pomelo.EntityFrameworkCore.MySql.
  • Added new extended property "Record Type" for classes.
  • Added new extended property "Do Not Generate Default Constructor".
  • Added a new extended property "Do Not Generate Mapping".
  • Newtonsoft.Json.Linq (JObject and JToken as property types) is now supported for Pomelo.EntityFrameworkCore.MySql in Entity Framework Core Model.
  • System.Text.Json (JsonDocument and JsonElement as property types) is now supported for Pomelo.EntityFrameworkCore.MySql and Npgsql in Entity Framework Core Mode.
  • Added new options "Private setter for store generated properties" and "Constructor parameter" to Model Settings.

LINQ to SQL support

  • Added a new option "Read-only computed columns" to Model Settings.

Fehlerkorrekturen

  • Fixed the bug with creating app.config in Visual Studio .NET Core projects.

Entity Framework support

  • The following properties are marked as obsolete:
    • The Generate Data Contracts property of the Entity Framework Core template.
    • The Do Not Generate Data Contract Attribute extended property of navigation properties in Entity Framework 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 has been fixed using the workaround with loading previous ODP.NET version from local NuGet cache.
  • Fixed 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 in Entity Framework 4/Entity Framework 5/Entity Framework 6
  • Fixed the bug with detecting the existing classes with QueryType=True by Update From Database Wizard in Entity Framework Core Model.
  • Fixed the bug with code generation for Npgsql, when the timetz column is mapped to a class property of type other than DateTimeOffset, in Entity Framework Core Model.