Thanks! But now where are the rest of the sample code of the video?
And again, it's been more than a month since Part 1. I may sound to be bad, but why can't I simply have the codes soon?
I think it doesn't matter for me if the code came directly enedited from David, instead of waiting for you to post the code, and it's been taking too long time to wait.
I have downloaded the ADO .NET vNext August 2006 CTP, and it's amazing! But what bothers me is the diagram you've showed in the video. On the documents, it said that there's no EDM diagram and I have to edit it myself. This is okay, but I can't find the real definition of these models, especially when I look at the XML source generated, the msl, csdl, and ssdl files.
My points are, (maybe it's been discussed in the previous post):
Is there any clear definition of these files?
When can I get the diagramming tools of EDM on the video? It seems like showing a kid a candy with a promised chocolate inside and it looks like yummy, and then the real candy given has no chocolate fill at all...
What about real data and object mapping for other database (other than MS SQL Server)? Talking about mapping means also accepting other kinds of database, just like Access or even Oracle. The integration with LINQ? I just see a code sample, but I still
don't understand how deep is the integration with LINQ, alhough I have to install LINQ first before I install ADO .NET vNext CTP.
Then since ADO in .NET 2.0 has a cool features such as Data Provider and the use of Factory pattern, how does this fit in the ADO 3.0? There are some people still want to be able to control at this level of defining Provider and also try to create their
own Adapter but want to be in accordance to ADO factory model. I hope I won't see another architectural shift.
Thanks for the video, anyway! But I'm afraid I won't encourage downloading ADO vNext to my friends, since the diagram isn't available yet, and I would like to get detailed information about this.