It would be great if the user was allowed to input parameters when Entity Developer is executing the function to create the return type model.

Currently if you need to input parameter values for the function to execute correctly, it will fail and no model will be generated since all values are sent as NULL.

I would like to be able to convert my database objects, which are in underscore notation into PascalCase when I do database-first work. Likewise, I would like to convert my PascalCase .NET objects into underscore notation in the database when doing model-first. So
MY_GREAT_TABLE becomes MyGreatTable and, MyGreatClass would become MY_GREAT_CLASS.

First of all, thanks for your great work ! Your Castle Active Record template is excellent.

It would solve a very common problem if you could add another template which generates classes that do not inherit from ActiveRecordBase (see http://www.castleproject.org/activerecord/documentation/trunk/advanced/mediator.html).

That should create <ClassName>.cs with attribute-decorated properties and optionally another, <ClassName>Repository.cs

Since we can connect to Oracle without using a TNSNAMES.ORA by fully specifing de DSN entry I think the connection interface should manage this by itself.
An example of a DSN-less connectionstring:

Data Source=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=MyHost)(PORT=MyPort)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=MyOracleSID)));User Id=myUsername;Password=myPassword;

please support a dark theme as in VS2012 in the standalone version of entity developer

Support for the EF4 CTP about the code first development. See http://blogs.msdn.com/b/efdesign/archive/2010/06/21/productivity-improvements-for-the-entity-framework.aspx

it would be nice if we can update only ONE entity from database.
a right-click menu option "update this entity from database" on entity would be perfect solution.

currently, is is pretty painful to do so, since we have to start from all objects and un-check everything except the entity that we are interested in.

thank you

Support view pregeneration in the DbContext template when generating fluent mapping.

After creating a Entity Model based on SQL Server 2008, I have to change the connection string so that queries run correctly.

I have to add...
MultipleActiveResultSets=True;

If would be nice if the Entity Developer would have this set by default just like the VS 2010 EDM designer.

Also, It would be nice to be able to modify the connection properties using the "Edit Model Setting" screen instead of having to edit the string manually in the .edps code file.

This should then create a unique constraint for the corresponding column in SQL.
Often there are fields that are not primary key, but still need to be unique "natural part numbers" are a common example.

Having the posibility to Enter "normal" SQL Code and out of this, generate the right LinQ Code.

My company uses a standard naming convention for private variables in classes which is different to the format produced by your product. It appears one cannot change this format from the layout eg '_MyPrivateVariable' to 'myPrivateVariable'. We use camel case for private variable declarations. I notice that there isn't an option for camel case at all. My recourse at the moment is to hand edit all the class files or develop a script to do this.

When adding a column, to be able to auto-add a property (via tick box) that maps to it and uses a default but alterable type mapping table.
E.g. Char becomes String, etc.
If nullable then IS nullable.

Ability to choose whether to generate fluent mapping for all entities in the OnModelCreating method or to implement fluent mapping generation in the separate configuration classes - a class per entity.

Implement the generation of the context methods for stored procedures added to the conceptual model in the designer when using the fluent mapping.

Generate interfaces for purposes of testing.

Automatic mapping of CRUD functions by their names or user-specified rules