Another milestone in the ADO.NET vNext train -- the Entity Data Model designer prototype has just been pushed to the web. In earlier iterations I have seen, this tool was more stand alone applications, so it's good to see it integrated into Visual Studio directly.
Some early comments:
* I think it will be important for third party providers to understand any additional requirements, beyond the established ADO.NET vNext interfaces in order fully participate with the ADO.NET entity 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...
View all posts from Jonathan Bruce on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.