Thinking in LINQ: Harnessing the Power of Functional Programming in .NET Applications

Great book for all levels.Appendix A alone, Lean LINQ Tips, makes the book a must have. My favorite part of the book. It's important to understand the performance impact of using LINQ

Innovative use of LINQ. Some tricks I had not seen before. However, as others have mentioned, I thought the author was a beginning programmer when I saw the incorrect and unnecessary (over-)use of .ToList and .ToArray. Such errors make me doubt that the book was edited and / or proof read by "real" programmers. Shame on the publisher?Use the ideas, but please write the code correctly. It'll be smaller and more readable if you know what you're doing.

The book is not for beginners, this I will say first off. The guy does teach what LINQ is and isn't in a different way, but that's ok, I get it. His style might not be for everyone but he does know how to make a point and you learn something from it. Love the book so far, I'm not that far into it yet but so far, the code has worked, I've learned much about what LINQ is, and is not. All I can say so far, is, I'll write more when I get farther into the book.The style of his teaching is not for everyone but that's ok, we all learn differently and each one must find out how they learn. This is a learning about yourself experience.

Kind of fun exercise to trace through the examples - especially with LinqPad - but really bad and misleading algorithms. He calls a "dot product" a pairwise multiplication of vectors when in fact, it's the summation of those multiplications. He then calls an actual dot product a "weighted sum" which, in a way it is but this is the algorithm he should have called "dot product". A favorite construct of his is:Enumerable.Range(1,n).ToList.ForEach(...)which he uses solely to perform the standard code in the ForEach n times, ignoring the value passed in. This would MUCH better be handled byFor(int i = 0; i < n; i++) {...}No creation of a list, no enumeration of a range and since he never actually uses the values passed in to the ForEach, going from 0 to n-1 is fine. He does this without ever mentioning the inefficiency and wrongheadedness of it all.I know it's a book on Linq, but that doesn't mean you should use examples where linq is precisely the wrong tool to use or where it's used ineffectively.A lot of examples to ponder on here which is kind of fun and some of them are actually not bad, but too many horrible examples for me to recommend this book.

I wish I had this book years ago. This will get you over the hump on LINQ concepts. I originally thought LINQ was just some cute language constructs for accessing databases. It's so much more than that and this book will get you to see that. Highly recommended from a guy that has been cutting code for 40+ years.

I was very disappointed. The author poses a mathematical scenario and provides the Linq query in C# to solve. 1) There is no walkthrough of the query to illustrate what each piece is accomplishing. I guess he figures you are already adept at crafting complicated Linq queries and know what each of the statements is doing. If you are already good at Linq, you only need this book if you have some essoteric math problems that you want to see solved with Linq. If you are trying to learn Linq...not so much. Very unhelpful! 2) Sure would be nice if there was a source of a VB version of the examples. I can work my way through the C#, but it's not my native programming language, and, since there are some major syntax differences, a VB version would come in handy. I used a pretty powerful converter, but many of the examples did not translate.

This a great book to highlight the functional programming "thinking" that should be embraced when mastering, the most innovative language feature in the last 10 years, LINQ. Don't log out without one.

It can be a good start to broaden your idea with LINQ. More examples needed though.

Well done what an excellent book, I am well impressed, really happy.Covers a wide range with excellent examplesAnd the samples are available on line directly from Linqpad - What a BONUS

Linq, c'est bien. C'est même très bien.Vouloir appliquer Linq là où l'on n'y penserait pas, pourquoi pas, ça peut toujours donner de bonnes idées.Mais quel dommage que les exemples donnés soient des horreurs en terme d'optimisation. Ils fonctionnent bien parce qu'ils travaillent sur des ensembles très petits, mais dès que l'on veut passer à la taille réelle...Quelques exemples :- l'auteur veut calculer les sommes cumulées d'une série de termes (soit, par exemple, pour {1,4,7,9}, 1, 1+4, 1+4+7 et 1+4+7+9. Sa méthode consiste à chaque rang à recalculer la somme de tous les termes concernés. On ne recycle pas les résultats précédents...- l'auteur implémente un dictionnaire T9. Son dictionnaire est une suite de mots dans un fichier texte, qui est parcouru à chaque fois intégralement. Toute personne qui a un jour travaillé sur ce genre de problème a entendu parler d'arbres de recherche.- l'auteur génère des mots de passe aléatoires de 6 caractères. Comment ? En créant un dictionnaire de tous les caractères utilisables, en associant à chaque caractère un GUID, en triant le tableau par GUID et en prenant les 6 premières occurences...Peut-être y avait-il plus rapide ?Je n'en suis qu'au tiers du livre et je hurle presque à chaque page. Pas certain que je le termine.

Book is full of useful examples, great is the section about LINQ Tips and also the chapter Interacting with the File System.

This is the most excellent book about LINQ that I have ever bought.