When using MVC and EF together it makes sense to have a data layer and model layer for good separation of concerns, however this can lead to lots of object to object mapping
Say you want to store an array of strings associated with an entity using EF? For example Tags on a Blog Post...
When EF4 generates your db for a referenced object it uses the class name, which makes for confusion when there are more than one reference for the same type
I am aiming to be able to use interfaces to describe common objects in my data layer, so that I can have common/reusable business logic functions which can expect a certain interface
PhoneGap on crap Windows Phone, you BEAUTY!!!!