Support for EF Core 5.0, .NET 5.0, and More Features in Entity Developer 6.8!

Devart news about betas, releases, awards, and other information
Locked
Devart
Site Admin
Posts: 3570
Joined: Tue 26 Oct 2004 13:51

Support for EF Core 5.0, .NET 5.0, and More Features in Entity Developer 6.8!

Post by Devart » Thu 18 Jun 2020 15:47

Dear users,

Devart is delighted to introduce the release of Entity Developer 6.8. The new version introduces support for preview versions of Entity Framework Core 5.0 and .NET 5.0, adds ability to generate C# 8 nullable reference types and configure collection navigation properties, improves support for stored procedures, for NuGet and third-party providers, and many more.

EF Core 5 and .NET 5 Support

The new version of Entity Developer supports EF Core 5 and .NET 5 as of EF Core 5 Preview 5. When new EF Core 5 versions are available, we will update its support in Entity Developer. Please note, however, that EF Core 5 support for .NET Standard 2.1 and .NET Core 3.x is fully implemented in all Entity Developer versions (Visual Studio 2019 add-in, standalone application, and console application). However, as for target framework .NET 5 for EF Core 5 model, we don’t recommend using Visual Studio-integrated Entity Developer. It’s better to use standalone or console Entity Developer.

C# 8 Nullable Reference Types

C# 8, which can be used for .NET Standard 2.1 and .NET Core 3.0/3.1 projects, has a hugely important feature – Nullable Reference Types. The new version of Entity Developer adds the ability to generate Nullable Reference Types for entity properties, which is controlled by the new "Nullable Reference Types" property of templates for EF Core, EF6 and NHibernate.

Collection Navigation Properties

Entity Developer 6.8 implements an ability to select a collection type for navigation properties, and which non-abstract type to use for property initialization (or don’t perform it at all). This feature is implemented for Entity Framework and Entity Framework Core with the template properties "Collection Property Type" and "Collection Initialization Type".

DEFAULT Column Values

Entity Developer 6.8 allows configuring code generation for default column values for Entity Framework, EF Core, NHibernate and Telerik Data Access ORMs. For this the "Primitive Default Value Generation" property was added to templates for these ORMs. It allows you to specify whether to add default value generation in the constructor for literals, for both literals and expressions, or not to add at all.

The behavior for old models stays the same (add default value generation for both literals and expressions), but the new models will have a different behavior by default. Default value generation will be added only for literals in the new models by default.

Stored Procedure Result Sets and Complex Types

When generating a model from a database, console Entity Developer 6.8 now can import stored procedures and functions to the model.

Optionally, it can even execute stored procedures for obtaining metadata of their result sets and adding corresponding complex types to the model. You can specify, which procedures it is allowed to execute in the --Execute parameter.

We have also improved stored procedure import in Entity Developer as a standalone application and as Visual Studio add-in. In the new version, users will get less dialog boxes when importing them, and they will be able to configure stored procedure execution and adding complex types to the diagram in model settings.


You can also see our blog article to read about these and other improvements in more details.


Devart development team
http://www.devart.com/entitydeveloper/

Locked