I typically try to avoid making link blog posts, but wanted to call your attention to a couple good posts recently regarding LINQ. The Microsoft XML team just put up a good collection of links. I agree completely with the initial statement that the community seems to be focused on DLINQ to the exclusion of the other pieces of the puzzle, namely LINQ and XLINQ. There could be any of a number of reasons for this. My top ideas are:
- DLINQ is wanted because ADO is too cumbersome and people want a better model that doesn't require writing as much plumbing code. This is evident from the growing popularity of O/R Mappers.
- There are many features people want DLINQ to support that it currently isn't able to do, or doesn't do as well as the native database engines. This is understandable since LINQ is relatively new and SQL has been around a long time at this point. DLINQ is in many ways the baby of the LINQ family and has a fair amount of maturing yet to go.
- XLINQ is so simple that it doesn't need much discussion. (The same can't be said for the XML Dom which is another reason why I think XLINQ rocks).
Regardless of the reason, LINQ is much more than just querying databases. As an example, check out Anders' talk with John Udell on some of the new features of the May CTP. It is a great talk with plenty of demos, including a demo joining northwind with an XML document showing the power that is possible with an integrated querying model that LINQ provides above just XLINQ and DLINQ.
In addition to the links the XML team gave, check out Sahil Malik's recent series of posts on LINQ and DLINQ. Don't forget to keep my LINQ category marked if you are interested in what I have to say on it.