There should be an AssociationChanging in System.Data.Objects.DataClasses.RelatedEnd class, so I can validate before items get attached to a relation.

It would be great if you could add feature for designer to convert uppercase table names to pascal case

I have a LINQ query that involves a nullable integer. When I try to run the query, I get the following error:

"LINQ to Entities does not recognize the method 'Int32 GetValueOrDefault(Int32)' method, and this method cannot be translated into a store expression."

I am not a L2E or EF guru in the least, but it seems like that should translate to the SQL ISNULL function shouldn't it?

Regardless, can you please make this functionality work?

Adopt the WAQS framework into EF source code

WAQS framework is a layer of abstraction over the Entity Framework

WAQS is addressing many of the painful scenarios under EF, with a great design and productivity.

http://www.dailymotion.com/video/xuc1jb_waqs-application-scaffolding_tech

You cannot use optimistic concurrency in model-first mode. This is because the entity designer does not support a timestamp type. Even if you add a timestamp column and update your model, it turns into binary(8) in the generated SQL. Manual changes to set the type to "timestamp" in the EDMX file are overwritten and the property reverts to Binary(8).

As far as I can tell, this makes it impossible to use this feature in model-first mode.

ADO.Net supports bulk insert for big amount of data. With the help of this library
http://archive.msdn.microsoft.com/LinqEntityDataReader
It is possible to do Bulk inserts with entities. But it would be nice if there would be a integrated approach.

Entity framework designer should support the attributes from the System.ComponentModel.DataAnnotations namespace. For instance, if I specified a range for a numeric type, EDMX designer would put a RangeAttribute on the generated property. I'm not sure whether or not EF should interpret this information, but at least my own controls could take advantage of it.

Add Filter and Sort support to Windows Forms BindingSource when bound to EF as in example below.

Dim context As New MyEntities
context.Employees.Load()
EmployeeBindingSource.DataSource = context.Employees.Local.ToBindingList()

'Would like the following to then work
EmployeeBindingSource.Filter = "FirstName = 'SANTA'"
EmployeeBindingSource.Sort = "FirstName"

I use data-driven filters stored outside of the application, so new filters and sorts may be added without new code.

See also
https://connect.microsoft.com/data/feedback/details/704105/entity-framework-winforms-datagridview-support-for-bindingsource-filter-sort-and-column-heading-sort#details

Some customers want to write queries that include such expressions as "date1 - date2" or "datetime3 + timespan1 > datetime4". LINQ to Entities currently support some of date/time operations through the EntityFunctions.AddX and DiffX functions, but it doesn't support built-in operators with data/time types.

RecreateDatabaseIfModelChanges shouldn't drop database (we often dont have permissions on server), but should drop tables and recreate them.

There are many database tables that have tables with a primary key of type int and are not autoincremented
it should be nice to have Ef generate code to allow updating the primary key.

Ability to save contents of a loaded entity set into an xml file to persist into hard disk then load again like is possible in data tables

Have some empathy guys! This guy is a good bloke and tries hard, and you're not making it any easier. He's just moved into a new place and is looking at buying himself a new projector for Christmas, but it might just not happen as this rate.

In my models, there are hierarchies that are persisted using TPT while others are persisted using TPH. It would be great if we could choose the strategy and then have Generate Database From Model create the tables depending on our choice.

Sometimes we wish to expose a collection as read only, normally using IEnumerable<T> instead of ICollection<T>. This is not recognized in the current version, but it should.