This was the question that was burning on my mind when I first heard about Linq. I was skeptical and didn’t think it was something that we needed. But after having started to use this new language, I have quickly become a believer.
Linq stands for language-integrated query and that is exactly what it is, it allows for rich metadata, compile-time syntax checking, static typing and IntelliSense on things that used to be imperative code. This is not only a huge win from the error perspective, but also from the ease of use one.
For example, here is a sample query which includes populating an array to store the data:
You can see where we query the data, you just simply do something like “from s in names where s.Length == 5 orderby s select s.ToUpper();” This clearly is close enough to SQL that anyone with experience with SQL programming will understand it and get used to doing this, but this means that if there is a typo, or any other problem in the query, you will find it at compile time.
Linq to SQL
For SQL, there are some specific things built into Linq. You can read all about it here. The main thing to know is that there is a DataContext object which does most of the interaction for you. If you are in Visual Studio and create a Linq to SQL object in there, you can point it to any/all of your tables and then access them in a very Object Oriented manner. And when you are done changing/inserting things into the database, simply call DataContextInstance.SubmitChanges() and it will take care of updating things.
This is a very powerful and intuitive language and I am just starting to wrap my head around it. Hope that this makes you want to try it out also and see what you think.