So in my LINQ code, rather than using an explicit Join to attach the Customer to the Orders table, I can query the Orders collection and retrieve the Customer information through the Orders navigation ...

If you start "thinking in LINQ" you'll get more done with less code, and what you write will be simpler than using SQL. Switching to LINQ and the Entity Framework (EF) means that code you'll write for ...

I am not really even sure how to Google search for this, as I am not really sure how to formulate the question, so I'll try and give an example. I am using LINQ-XML to parse an input file that I want ...