I had certainly delayed looking at LINQ for too long. After seeing a screencast on some of the new features in ASP.NET I noticed the very handy LINQ to SQL item. Well. Let's just say I'm not using strongly typed datasets anymore. LINQ provides strongly typed access to your database (tables, views, sprocs and function) while also allowing you [...]

... the language. (Those are two powerful incentives to use it, by the way.) But there's nothing really magical about it -- behind the scenes, LINQ to SQL queries are transmogrified into method calls that ... in the middle. In SQL, it was "select stuff from here with this criteria." In LINQ, it's "from here, with this criteria, select stuff." Furthermore, we have to reference the name of each row entity, ...

... become exponentially difficult to write as their complexity grows. LINQ scales much better in this regard. Once you get used to it, it's hard to go back. Database queries ... -time. Parameterization is automatic and type-safe. LINQ queries can directly populate an object hierarchy. ... SQL provides a model for provider independence that might really work. LINQ significantly cuts plumbing code and clutter. ...

... the statement. You can see this if you access the Expression of the statement: System.Linq.Expressions.Expression expression = x.Expression; In ... stuff - but there are a lot of examples out there on how to do it appropriately. I've written about this before but when it comes to using LINQ and its constructs you really can't write enough. The pattern you want to use when you're dealing with a tree ...

... . The technical reasons are not really interesting, but suffice to say that to provide good Linq support we also need to modify NHibernate slightly. Those changes happens on the trunk, which is ... from the community. It is likely to have bugs (in fact, we know it contains bug in the more complex Linq queries, that is why it is still under active development), and the NHibernate team response is most ...

... , to encourage people to make other systems and data stores accessible from the coolness-that-is-LINQ.  Back in February, Charlie Calvert published a  long list of LINQ providers.  In July, Robert Shelton later reblogged it.  Charlie also has a list of LINQ Links.  Nice to see.  By my count there are 33 different LINQ ...