Kevin

>My two cents: if you're using stored procs in SQL Server, there is not much of a convincing reason to use LINQ to SQL (and in my opinion, LINQ to SQL is, in some instances, a few steps backwards)

As LINQ is still very young, it is no wonder it ist sometimes a step backwards, but

>The power and benefits to LINQ are things like Linq to Objects, Linq to XML, etc.

for me the real power lies in making the exchange of different storage mechanisms (almost) painless is the real power gained by abstracting the differences away. Even if you are using best practice (which sometimes is debated) for SQL server, while keeping the "best of breed" aproach you are kept locked into the CS-approach. I won't argue for data entry, but lookup or report data might benefit from other aproaches more.

my 0.02 EUR (look at the exchange rate ! <g>)

thomas