Currently Entity Developer roadmap includes the following features:
Support for the NHibernate open-source ORM framework.
Support for third-party ADO.NET data providers in Entity Framework and NHibernate models. Provider should support Entity Framework for Entity Framework models.
Migrating models between different ORM solutions (from Entity Framework or LINQ to NHibernate, etc.).
Wizard for comparing the database with the model and updating the model from the database. The wizard will try retaining all manual changes to the model.
DDL script generation for creating database for the model (Model First), and wizard for comparing database with the model, and updating the database from the model. Wizard will try affecting the existing database data as little as possible.
Support for command line parameters for automatic code generation from the model and automatic model generation from the database.
Model editing via C# or Visual Basic script.
Editing of the data, returned by LINQ or Entity SQL queries and saving changes to the database.
Execution of native SQL code.
Code completion, syntax highlighting, code formatting, etc.
Design-time adding of custom attributes, which affect code generation, to classes, methods, and properties.
Design-time adding of custom attributes for DataAnnotation validation.
Design-time and template enhancements for creating validation rules for values of the model class properties.
Reusing code of a template in other templates. Linking one template file to another with template import or inheriting template from other one.
Binding template to a model with the relative template path stored in the model. This allows transfering templates with the models without the need to register templates in Entity Developer separately.
Templates for generating RIA domain model classes for Devart LINQ and NHibernate models.
Templates for generating POCO code for Entity Framework 4 models.
Diagram for displaying storage schema.
Automatic mapping of CRUD functions by their names or user-specified rules.