Rating: 
Summary: Great Reference on Visual C#
Review: As is stated on the front cover of this book, this is a "Reference," and not a tutorial, however, this book is an invaluable reference. For learning C#/.Net itself, I recommend either the Wrox Professional C# 2nd Edition, or the OOP with Microsoft Visual Basic .NET and Microsoft Visual C# .NET Step by Step.Mickey covers all aspects of C# programming, including:
* The C# language and the .Net framework itself
* An extremely comprehensive presentation of Windows Forms
* Introductory material on GDI
* Good beginning material on ADO.Net and XML
* Introductory material on ASP.Net and Web services This book is very heay on thorough explanations of various classes, techniques, and the .Net framework itself, and very light on example programs, making it an excellent reference. The only issue I have with this book is that it does not cover basic architectual issues in building an entire program. By this I mean it does not show how a programmer might write a distributed application, with code in components. If you want to know how best to architect an entire solution, this book is of little help. Also, Micky makes a number of well-meaning comparisons to C++, which are either wrong or are misleading, however, the comparisons are of no consequence to his excellent presentation on C# and .Net itself.
Rating:
Summary: Great Reference on Visual C#
Review: As is stated on the front cover of this book, this is a "Reference," and not a tutorial, however, this book is an invaluable reference. For learning C#/.Net itself, I recommend either the Wrox Professional C# 2nd Edition, or the OOP with Microsoft Visual Basic .NET and Microsoft Visual C# .NET Step by Step. Mickey covers all aspects of C# programming, including:
* The C# language and the .Net framework itself
* An extremely comprehensive presentation of Windows Forms
* Introductory material on GDI
* Good beginning material on ADO.Net and XML
* Introductory material on ASP.Net and Web services This book is very heay on thorough explanations of various classes, techniques, and the .Net framework itself, and very light on example programs, making it an excellent reference. The only issue I have with this book is that it does not cover basic architectual issues in building an entire program. By this I mean it does not show how a programmer might write a distributed application, with code in components. If you want to know how best to architect an entire solution, this book is of little help. Also, Micky makes a number of well-meaning comparisons to C++, which are either wrong or are misleading, however, the comparisons are of no consequence to his excellent presentation on C# and .Net itself.
Rating: 
Summary: Sorry
Review: Examples are piss poor and there is little information that you couldn't easily find on help. Help actually provides more info than this waste of time. This is supposed to be a core reference but all references are quite incomplete. For example if you look at this book, examine the DataGrid control sub-chapter and see if it provides enough information to actually write, or use a data grid control. This book is useless.
Rating:
Summary: Enumerator example has a lapsed listener problem
Review: I have read in the reviews of this book that it's geared towards the intermediate/advanced developer. I disagree! This book is orientated towards the beginner. If you're a seasoned professional in a language such as VC++, then I recommend that you bypass this poorly written book as you'll be done with it in a few weeks!
Rating: 
Summary: Poor reference
Review: I have read in the reviews of this book that it's geared towards the intermediate/advanced developer. I disagree! This book is orientated towards the beginner. If you're a seasoned professional in a language such as VC++, then I recommend that you bypass this poorly written book as you'll be done with it in a few weeks!
Rating: 
Summary: Need to get another copy
Review: I originally bought this book for my team as a reference, but I'm finding that I use this book all the time now. The integration with Visual Studio is really cool, and keeps the book at my fingertips at all times. It also has the most concise explanation of the C# language I've seen so far. Also, the book has coverage of controls and other topics that weren't covered even in the Petzold book. For one book to cover overloading of the true and false operators, as well as Windows Forms and XML, is simply amazing. Another thing - if there are any errors, my team hasn't found any yet, and we've been through the book front to back. Great work. This is easily the team's favorite Visual C#-specific .NET book, and I'm going to need another copy just so I can keep the it in my office. The only drawback is that I would have like to have a bit more detail on ASP.NET and Web Services, but all in all, this is a great book.
Rating:
Summary: A solid foundation to C#
Review: I read this book a couple of years ago when I was making the switch from VB to C#. It is well written and covers the OO fundamental well. I've referred to it regularly since making the switch to C#. It's become one of the staples in my reference library.
Rating:
Summary: Very Good for the Studio Parts
Review: I've been reading this book becuase I needed a book that also talked about how use the parts of visualstudio like the windows forms controls and making web services. There's about 1/3 of the book on windows forms after the part anout using the language. i also have another book about just the c# language, but this one is good too. The way it automatically adds new infos to the online help is good too.
Rating:
Summary: Poorly done - Basically C# for Dummies
Review: I've been using C# for 3 years, but purchased this book hoping to glean some new stuff on C# and .NET. Boy, was I disappointed. I own many MS Press titles from Richter, Petzold, Prosise, etc. and have been ecstatic about them all. However, this author definitely is not included in that list and shouldn't be writing professional books. I know that he used to write the "dummies" level books and it definitely shows in this attempt. The information is nothing short of a rehashing of MSDN material with absolutely nothing added. Very disappointing.
Rating:
Summary: Enumerator example has a lapsed listener problem
Review: Overall I think this book makes a good reference. In chapter 7, I like the point about being careful to invalidate the enumerator if the underlying data gets changed. However, be aware the example has a "lapsed listener" problem. When the enumerator object is no longer needed, how is it supposed to be unsubscribed from the Changed event? If it never gets unsubscribed, then the garbage collector will not be able to remove it from the heap, thus you end up with a memory leak. Using System.WeakReference is one way to solve this problem.
| 
