Entity Developer 6.3 is released !

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

Entity Developer 6.3 is released !

Post by Devart » Fri 22 Jun 2018 10:47

Dear users,

Devart is delighted to introduce the release of Entity Developer 6.3 . Entity Developer now features support for Entity Framework Core 2.1.

Entity Developer allows you to design models for Entity Framework Core 2.1.1 and supports all the new features. You may define classes as query types, add parameters for class properties to a parameterized constructor, configure lazy loading for entire model or for separate navigation properties visually.

You are welcome to download and evaluate the new version.

If you wish to provide feedback on the new version, you can do it in our forums or with contact form. There is also a feedback form, and we are always glad to hear your comments and take into account your development needs.

If you want to share your ideas about new Entity Developer features, you may do it on the UserVoice.


Here is the complete list of Entity Developer 6.3.525 features:
  • The bug with generating ParameterDirection.InputOutput for SQL Server OUTPUT parameters is fixed
Entity Framework support
  • Entity Framework Core 2.1 is supported
    • 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
    • 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
    • Properties now have the Constructor Parameter property, for configuring a parameterized constructor of the class
  • 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
Devart development team
http://www.devart.com/entitydeveloper/

Locked