>>
>>I have the Richter book and you just inspired me to pick it up again. I was very new to C# when I tried to read it the first time and felt like I was in way over my head with an advanced text. Flipping through it again now, maybe it's just an organization issue. It starts right out with things like deployment, assemblies, the disassembler, and the like (after a brief overview of high level .NET concepts). Only then do you get into more basic concepts. I'm still not sure it's for someone brand new to C# but I am going to start reading it again. Thanks!
>
>I'll be honest - I normally don't like books that get into the nitty gritty details before I have even gotten started. I tend to get lost/bored. I want to get something working, then dig more into the details as I need/want to understand more about what's going on under the covers.
>
>I skipped around a lot in this book. I didn't start at the beginning and read it start to finish. But I'll honestly say it's one of the few .NET books I've got that I've gone back and re-read various chapters a few times (not like some of my other books that tend to only be used as a reference when I'm looking for something specific). I think the only other .NET book I can say that about is Juval Lowy's "Programming .NET Components" (which, BTW, is NOT an entry level book). But what it did do was help clarify some of the fundamental ways .NET works in way that seemed to work for me. Too often I read things like, "A .NET string is immutable, therefore it's not efficient to do string concatenation with it; use a StringBuilder instead." - great, WTF does THAT mean??! His explanations seemed to click with me.

Or the String.Concat method. ;-)