Recommend me a C# book

[Speedo]

Preferably something aimed towards a more experienced programmer (have about 8 years now of C++ experience, and various other languages). I've tinkered with C# from time to time and it isn't that difficult for me to pick up with its similarities to C++, but I'd like to start using it more seriously and would prefer not to learn things the wrong way.

[BioPhysEngr]

Interesting learning project + Google + Willingness to play around = Victory

You sound like an experienced programmer so it should be easy to pick up the language without needing to buy a book. Besides, there are plenty of great tutorials on the web. Just pick a project and go for it.

Have fun!

[HanneSThEGreaT]

TBH, I think if you were a total newb, yes, start with a book. But you have 8 years experience, so it should really not be difficult at all. I have years of experience in VB 6, then I moved to VB.NET, then C#. The only book I studied along these lines, were VB 6.

If you are looking for specific topics, ask here, and we can help, or try google for what you're looking for. It should really be sufficient

[TheGreatCthulhu]

On the other hand, if you find it easier to use a book as a reference, then either get something that is a reference in the true sense of the word, something that covers a broad range of .NET topics in decent amount of detail (that would be a thick book), or something designed for experienced programers, meant for the reader to just fly-through and quickly pick all the stuff up (that would be a thin book). Unfortunately, I can't recommend anything specific.
But, as others have said, there are plenty of resources on the web, and you'll still be calling MSDN your "home away from home".
If you aren't coming from a .NET background (or a managed environment like Java), then it is very important to understand what .NET is all about, what the Garbage Collector (GC) is (and to learn to trust it), what managed means, and what is the difference in the way reference and value types are passed around (that's what's important, not whether they are created on the heap or on the stack).

And remember, managed or not, all the not-really-language-specific good programming practices still apply.