After living 100% in LINQ for the past week, this is my conclusion. And that’s just LINQ to SQL. There are just so many ways to skin the database with LINQ. The possibilities seem quite endless at this point.
But I’m having fun and we’ll see if I can keep it to 1.5 – 2 hours tonight at VTdotNET!
Swoon…..
Sign up for my newsletter so you don't miss my conference & Pluralsight course announcements!
I don’t want to make your head explode or anything <g> but you may want to have a look at the ADO.NET Entity Framework and the Enitiy Data Model. After exploring this, I’m wondering if LINQ to SQL is really even necessary. EDM is much more robust, IMHO. bethmassi.blogspot.com/…/edm-and-linq.ht
Yes adding the Entity Framework into the mix is overwhelming. I’ve definitely been working wtih EDM as well (have some talks coming up). With LINQ to SQL, LINQ to Entities and Entity SQL – there’s a lot to choose from. LINQ to SQL might end up being the poor man’s Entity SQL, but it will be great for many who don’t want or need to go in deeper.