BT

Your opinion matters! Please fill in the InfoQ Survey!

ADO.NET vNext: Entity Data Model Designer Prototype Available

| by Jonathan Allen Follow 254 Followers on Sep 27, 2006. Estimated reading time: less than one minute |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

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

This demo requires the May LINQ CTP and the August ADO.NET vNext CTP.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

ADO.NET vNext by Jonathan Bruce

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 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...

jonathanbruceconnects.com/jonathan_bruce/2006/1...

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

1 Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT