If you start 'thinking in LINQ' you'll get more done with less code, and what you write will be simpler than using SQL.

When you want to find all the objects that are missing a corresponding object, then you need the LINQ equivalent of an outer join. Here, step by painful step, is how to build that query.

You don't ever have to write a complicated LINQ/Entity Framework query, but you do need to know when to call the ToList method on your query. Here's a tip on both.

As I mentioned Monday and in my Visual Studio 2008 review, I've been struggling with the finer points of LINQ queries. In a talkback comment to my review, "CSharper" pointed me at one solution to ...

The IQueryable interface pertaining to the System.Linq namespace extends the IEnumerable interface and can be used to query data from data sources that implement IQueryable providers.

You have a method that contains a LINQ query. If you use the right interface, other developers can piggyback on your method with their LINQ queries without losing efficiency.