You may not have heard about Microsoft’s new brainchild, Language Integrated Query (LINQ). If you did hear about it, you may have yawned and put it down as yet another new technology searching for a requirement.
LINQ is different from most new technologies because it really can do everything it says it can. After working with LINQ for nearly a year, I’ve found that LINQ hasn’t disappointed me, as have so many other technologies I’ve tried. LINQ is incredibly easy to use and quite reliable. The fact that I’m not alone in that sentiment is attested to by the large number of third-party add-ons created by other developers who feel the way I do about LINQ.
If you haven’t encountered LINQ before, here’s the straight-up definition. LINQ is a kind of query language, sort of the same as SQL, but the syntax is a little different. The basic idea is that you ask a question (or rather, your application does) and LINQ provides the answer from the data source you specify. That data source may not be a straight-up database. For example, if you ask LINQ which employees are in the accounting department and you supply Active Directory as the data source, the LINQ gets the answer for you from Active Directory.