>Are you saying that Linq2SQL is already old stuff, or did I miss the point? So, did I waste my money when I just ordered Murach's ADO.NET 3.5 with C# 2008 book?

Depending on whose blog or whitepaper or translated from another language site or whatever you read, LINQ may or may not be a technology Microsoft is dead-ending.

I'm way past playing pin the tail on this mornings MUST HAVE brand new technology that may or may not be passe (EEW why are you using THAT?) by lunchtime.

TSQL has been around for a long time, and nothing I see says it will be gone today.

As long as I can make a connection to my SQL server, I can handle data using TSQL.

That's my story and I'm sticking to it.

>
>I do have Visual Studio RC1 installed on both my laptop and my desktop, so that is ready to go. That was a long installation, by the way.
>
>Cecil
>
>>Cecil, the problem is that change has been so fast and furious that many/most books and articles describe technologies that may no longer be concurrent. L2SQL, for example, is highly accessible but already Foxed. In your shoes I'd get hold of a VS2010 beta, get your head set on tiered development that does not revolve around SP, and start messing with POCO. with a fox background you'll find it fairly familiar, in any case you'll be as up with the play as most people out there, and not having NET legacy to worry about should make it easier to engage.