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.
Here is the complete list of Entity Developer 6.12.1338 features:
- The new property Validation Framework is implemented in the Data Transfer Object template for generating DataAnnotations attributes
- The new option "Save connection to" is implemented in Model Settings of EF Core Model to provide the ability to store the connection string in "Model file", "Entity Developer storage", "Environment variable"
- The new option "Enum Output" is added to the EF Core template to specify output for the generated enums
- The new property Generate UnitOfWork Repository Properties (by default, True) is implemented in the Repository and Unit Of Work template of EF Core Model for accessing the collections of entities
- The Uri data type is supported in EF Core Model
- The DateOnly and TimeOnly data types are supported in EF Core 6 models (SQL Server, SQLite)
- The representation of one-to-one association with non-nullable properties on both ends is changed from 1 -> 1 to 0..1 -> 1 on a diagram in EF Core Model
- The behavior is changed: if Target Framework is set to .NET 5 in Model Settings of EF Core Model in Visual Studio, EF Core 6 is no longer available as an option of EF Core version
- The bug throwing "Unknown property 'DoNotSerialize'.", when complex types and VB.NET template are used in EF Core Model, is fixed
- The bug with code generation for the Constrained option of Association Editor in the case of 0..1 -> 1 association in EF Core Model is fixed
- The bug with mapping NUMBER columns to .NET types in EF Core via Oracle.EntityFrameworkCore is fixed ("ODP.NET, Unmanaged Driver"/"ODP.NET, Managed Driver")
http://www.devart.com/entitydeveloper/