Go get the
ADO.NET vNext August CTP (ADO.NET Entity Framework + some goodies).
I have posted previously about the impact that I think the ADO.NET vNext (ADO.NET Entity Framework) is going to have on the business of building data-driven applications,
especially when considering the impact on server/service-oriented data-driven applications, back-end applications and more. I have already pointed out that LINQ is the candy that I have been craving since I was a child, and to be able to use LINQ against a robust, entity-based virtualized object model -
pure digital crack.
If you were looking forward to the ability to visually configure your model and your model map (the XML that relates your model to your underlying relational database schema), you'll be just as dissapointed as I am. When I saw Pablo using a visual designer for the Entity Data Model in the Channel 9 video I was stoked - I thought,
Great, we'll get that in the upcoming CTP bits! Unfortunately we don't get it, so if you want to actually create an entity model that differs from the database schema (the
entire purpose of EF) because the objects you're working with have a different model (as well they
should) than the schema - you're going to have to do it by hand.
I am planning on doing just that with a database that I plan on exposing via the EF. I'll let you know how that goes.Thankfully there is at least some XSD backing support in the XML for the various parts of the Entity Model class library so you get IntelliSense XML from within VS 2005.
Also keep in mind that you must have the May CTP of the LINQ Framework installed on your machine in order to install the ADO.NET vNext August CTP.
tags: adonet adoef entity framework data adovnext netfx3 vista
links: digg this del.icio.us technorati reddit
