Pablo Castro, ADO.NET Technical Lead at Microsoft, just dealt the development community a huge blow by mentioning in the MSDN Forums that ADO.NET vNext will not be included in .NET 3.0.
"ADO.NET vNext will not be included in .NET 3.0. (that's why we're just calling it "vNext" for now)." - Pablo Castro
Microsoft is being really slow to deliver o/r mapping technology. We could have used the ADO.NET Entity Framework years ago when they were talking about ObjectSpaces.
I think this goes hand in hand with Microsoft always wanting to deliver new versions of software that completely change development. I would rather they deliver smaller, usable solutions incrementally that provide a migration path to future solutions.
Source: David Hayden ( Sarasota Web Development )
Filed: ADO.NET vNext