Microsoft Data Access strategies

Lately, there is a lot of buzz around two technologies from Microsoft about representing and querying data. The first is the new Entity Data Model exposed as part of the ADO.NET Entity Framework, and the second is a set of extensions to the .NET Framework for integrating queries into the programming language known as LINQ.

What are these technologies, how do they relate to one another, and what role do they play in Microsoft’s Data Access Strategy? How do they compare with the current ADO.NET which is widely used? How does XML data access feature in the new world? What about the community projects like NHibernate and Repository Factory - how do they fit it?

See my PowerPoint presentation DATA ACCESS STRATIEGES - 2008 to get an idea of what to use where and how Microsoft's data access strategies have evolved.

Comments