ADO.NET vNext: Entity Data Model Designer Prototype Available
The ADO.NET team has released a demo of their Entity Data Model Designer. This tool demonstrates some of the Object-Relational Mapping (ORM) features planned for ADO.NET vNext.
The Entity Data Model Designer allows developers to separate the logical schema from the actual database schema. Benefits include a reduced need for joins in code and the ability to isolate code from database schema changes. Other concepts such as inheritance are allowed
Some early comments:
* I think it will be important for third party providers to understand any additional requirements, beyond the establoshed ADO.NET vNext interfaces in order fully participate with the ADO.NET enity model. Does this tool rely or indeed leverage the DDEX Visual Studio integration mechanism?
* The tool is currently only geared to function with the SqlClient ADO.NET provider, and in my early experiments I've been unable to integrate any other ADO.NET vNext enabled providers. I would be interested to hear if anyone has had success with this.
* The ADO.NET team's policy of a steady drip feed of tools and CTP updates is to be commended! I would also like to see some of the broader feedback too...