Dear users,
Devart is delighted to introduce the release of Entity Developer 6.12. This version features support for more data types in Entity Framework Core models, better model connection string storing, code generation template improvements and changes for Entity Framework Core 6 support.
Support for New Types
The new 6.12 version adds Uri to the list of supported types for EF Core 3, EF Core 5, and EF Core 6 models. EF Core providers that support this type, usually map it to a string data type in a database (varchar, text, etc.). For EF Core 6 models, DateOnly and TimeOnly types are supported.
Additionally, the default size of the Type UI list in the Property Editor has been increased to make selecting a type more convenient.
Storing Model Connection
Now you can select where to store model connection strings - in the model files as before, in Entity Developer storage, or in the user environment variables. When selecting Entity Developer storage, connection strings will be stored in the Entity Developer settings directory for the current user:
%APPDATA%\Devart\Entity Developer\Storage\
Connection strings will be stored in the following files:
%APPDATA%\Devart\Entity Developer\Storage\<model_guid>.xml
Code Generation Template Improvements
The Repository and Unit Of Work template has got the new “Generate UnitOfWork Repository Properties” property for EF Core models. This property allows generating properties for access to all repositories in the IUnitOfWork interface.
The Data Transfer Object (DTO) template now has the new “Validation Framework” and “Validation Error Messages” properties for all ORMs that allow generating DataAnnotation attributes for properties of DTO classes.
Finally, the EF Core template now allows configuration of generated enums output.
You can find more information in our blog article.
Devart development team
http://www.devart.com/entitydeveloper/