Rating: 
Summary: Yes Presenting C-Sharp, that's what it is!
Review: Everybody I highly recommend that you buy this book IF you would like to have C# *PRESENTED* to you by Chroistopher Wille.Although having said that you could also download the .NET runtime package from Microsoft and get all of this information (and more) for FREE. I couldn't believe, as I read this book, that one man could Copy|Paste an entire book. Buy this book ONLY if you NEED the tax deduction, otherwise buy a real .NET book.
Rating: 
Summary: Short, but good for VB developers
Review: Everyone seems to be bashing this book, but I really liked it. As a VB programmer going to C#, this is my fourth book on the subject. Although it's small, the concepts are explained really well. For example, writing Events in C# is totally different b/c it uses Delegates. The book "C# Essentials" and "A Programmer's Intro to C#" just left me confused. This book explained it very well. This applies to most of the topics in this book. He is an excellent writer and would make a great instructor.
Rating:
Summary: Great book
Review: Great book! This is a short and 'to the point' book that gives you a surprisingly thorough look at C# and many of the features of the CLR. There's no semi-relevant verbage you have to wade through to get to the point as there is with most programming books. You get only what you need to know. I do think some some topics should have been covered more thoroughly than they were, but I guess that wasn't the point of this book. If you have an object oriented programming background (having some knowledge of C++ is helpful) and don't need an introduction to OOP concepts, this book is a worthwile purchase.
Rating:
Summary: Does SAMS even use copy editors?
Review: Horrible! This book reads like a term paper written by an English-failing high school student. I don't understand how any publisher could ship... this. The content is dated and weak as well. Don't buy this book!
Rating:
Summary: Marketing hype only
Review: I realize that there is a value to being first, but the actual information in this book could have conveniently been printed in about 5 pages. While it did touch on the major concepts of the language, there was no depth at all. Considering the book touts itself as "Intermediate to Advanced" I was quite disappointed.
Rating:
Summary: Good Look to the Horizon
Review: I thought the book was a nice heads up to what's coming with the C# language. It covered the major points completely and somewhat thoroughly. Given the early beta nature of the product, I'm sure it is very hard to write for a language that want be formally available for several month. The book is more of a travel guide (a good one) for the language. Anyone who will work in it will probably want a more detailed reference when it eventually comes out. But until then, get the beta copy and start with this book.
Rating: 
Summary: Too light on content
Review: I was expecting a K&R type introduction to C#, but while this book didn't cover the very basics (thankfully), neither did it get into any serious content. Most of the information in this book can be gathered online from Microsoft and other sources. In the example code, the author sometimes uses concepts that have not been previously introduced -- sloppy. Also frustrating is that he devotes very little to C# specific concepts that should be the focus of the book. I get the feeling that previous reviewers seem to be allocating stars to the C# language rather than this book! I recommend waiting for more substantive books on C#.
Rating:
Summary: Another classic debacle from Sams - 0 Stars
Review: It's a wonder Sam's even manages to sell books. Everyone of their's that I have picked up in the past is full of errors and examples that don't work. I strongly suggest that you steer clear of this book and wait for the Wrox or New Riders book on C#. That will be the one to buy. Anything from Sams is simply a grab to be the first on the shelf. Quality, accuracy, usefulness, instructive. What's that ? Sams just wants customers to buy their books. They don't really care whether you find them useful.
Rating:
Summary: Great book
Review: Let me begin that I'm not reviewing the topic (C#) as a language, I'm reviewing the book. I'm a java/C/C++ programmer and I bought it to see what C# was all about. This book does give you an overview of the C# langauge as proposed (at the time the book was written very little was known about it) and the technologies around it, complete with code samples. Unfortunately it reads like a marketing document from microsoft. He uses the word java once in the whole book, and doesn't explain things simply like "This is another name for a Virtual Machine". Well since virtually none of the concepts in C# are unique to the language, why would you not at least give the common name for a concept? In a term "Non disclosure agreement", probably to get the early peek at the technology he had to abide by some exclusionary agreement. What does this mean to the reader, it means you have to read a whole page explaining what something is before you realize "Oh thats just a...just in time compiler" or wherever. By the time you read this review you'll already have several MUCH better alternatives to this book. Look elsewhere. (and all that being said I probably will learn C# and hope it is somewhat ported to other environments, I think it's a good alternative to some uses of C++)
Rating:
Summary: I use this book as a car mat
Review: Let me begin that I'm not reviewing the topic (C#) as a language, I'm reviewing the book. I'm a java/C/C++ programmer and I bought it to see what C# was all about. This book does give you an overview of the C# langauge as proposed (at the time the book was written very little was known about it) and the technologies around it, complete with code samples. Unfortunately it reads like a marketing document from microsoft. He uses the word java once in the whole book, and doesn't explain things simply like "This is another name for a Virtual Machine". Well since virtually none of the concepts in C# are unique to the language, why would you not at least give the common name for a concept? In a term "Non disclosure agreement", probably to get the early peek at the technology he had to abide by some exclusionary agreement. What does this mean to the reader, it means you have to read a whole page explaining what something is before you realize "Oh thats just a...just in time compiler" or wherever. By the time you read this review you'll already have several MUCH better alternatives to this book. Look elsewhere. (and all that being said I probably will learn C# and hope it is somewhat ported to other environments, I think it's a good alternative to some uses of C++)
| 
