Entity Developer 3.50 Beta is available!

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

Entity Developer 3.50 Beta is available!

Post by Devart » Thu 21 Apr 2011 12:23

Dear users,

We are glad to announce the Beta version of Entity Developer 3.50!

The new version contains numerous and significant enhancements in template use and management alongside certain other functional improvements.

Now, it is possible to add more than one template to the model, register added templates within the model and store them either in the Entity Developer resources, or in the specified folder, or together with the model itself. The so-called "shared" templates can now be easily shared between different models.

Another new feature in the area of template use and management is the possibility to exclude templates from the process of code generation by setting their "enabled" property to "false". This greatly improves the flexibility of the code generation process.

Template code can be easily edited in the improved built-in T4 editor. Our T4 editor features extensive intellisense functionality, syntax highlighting, navigation to definitions and declarations of objects and members, present in the template file or included files, multilevel template inclusion and some others.

The range of templates available in Entity Developer is further extended with the POCO template with XML mapping for LINQ to SQL and the POCO, Self-Tracking, DbContext, and Fluent mapping template for Entity Framework.

Additionally, the Entity Developer application now features, alongside the FilePerClass option, the EntitiesOutput and ContextOutput functionality that allows redirecting code generation for entities and appropriate contexts to any folder or project.

Presently, Entity Developer makes it possible for developers to exclude classes from being overwritten at each generation; in multi-layered application development, this allows creating sets of sample classes that can later be modified as needed.

The use of extended properties defined directly in template code makes the process of code generation much more flexible. The developer can customize the set of properties of any element in the model by declaring extended properties both in template code and in model properties. For example, you can add the Generate property to every class and then exclude some classes from generated code by setting this property in designer.

Starting with this version of Entity Developer, developers can select attributes from all available assemblies, set values of attribute parameters and assign attributes to classes, properties or contexts of their model. Assigned attributes and the values of their parameters will be present in generated code. For example, the System.ComponentModel.DataAnnotation attributes that are used for validation.

If you need another feature in Entity Developer, visit our forum at UserVoice and vote for suggested features or suggest your own one.

Devart development team