ADO.NET vNext Future Directions 4
Also see the first, second and third part of this series of posts on the next generation data access for the .NET platform.
Currently there is no support in ADO.NET vNext for an entity base class. At least not a type that doesn't require to have a key as part of its definition [discussion]. A silly hack is to store the entity type in the Conceptual EDM and let all entities inherit from it [discussion].
Currently there is no support in ADO.NET vNext to re-generate the Mapping and Store Schema after you make a change to the database (also see ADO.NET Entity Framework Metadata). The team is thinking about the best way to make this possible in future releases [discussion].
Currently there is no support in ADO.NET vNext for Locking hints like NOLOCK [discussion]. According to Pablo Castro it's hard to come up with a general purpose mechanism to support locking hints without loosing the database independence. No specific plans.