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

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.

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 you can see, creating Web parts and query data from the SharePoint 2010 installation is very easy with the new Visual Web Part and LINQ to SharePoint features of VS2010.

So I'm playing around with Visual Studio 2010 while we think about moving our projects to it, and I was trying to make a new Silverlight 4 app, but when I ...