Rating:  - This is THE book to learn C#
Very very easy to read. Full of good examples. It grabs you by the hand and teaches you step by step everything about C# in simple, understandable words. Provides examples on every topic, makes comparation between C#, VB.NET, C/C++ and Java. I was eager to learn C# but I did not want to read from a hard, meticulous book. I found this book and it was awesome reading it, and when you less know it you are finished reading these +600 pages book and already programming C#. If you are still deciding which book to purchase, there are good books out there, but THIS ONE is a definitive good decision to acquire and read.
Rating:  - Not well put together
I work through every example in a book to make sure I'm not glossing over important details as I read. What I found in this book was a real mess of code from one example to the next. Many times the code examples appear to be building on each other as you progress through each chapter but if you actually work the examples, you find that variable names are different, naming conventions are all over the board, and you end up spending time trying to figure out what changed instead of focusing on what you're supposed to be learning. It also felt like a lot of the concepts were just being tossed into the text instead of being treated thoroughly. I will say that I just had to stop after chapter 5 so it may get better but I'm really disappointed so I'm giving it a low rating.
Rating:  - This book is not as good as I expected
When I made a decision to purchase this book based on the first couple of reviews @ amazon.com. I bought this book two weeks ago and so far I am reading chapter 14.
The book is not clear and sometimes confused in describing C#. I myself got confused a couple of times. Here are a couple of examples, in page 195, "IComparer and IComparable ..." section, where does "IComparable" comparable come from? I had to look up from MSDN to find out it from System.IComparable. Another example, is "string" a built-in C# type or just a keyword mapping to the .NET class? Third example is why "using System.Text;" is used in code examples 10-2 and 10-3.
Does ADO.Net only provide disconnected classes but not connected classes? That is an idea the book give me. The book does not mention anything about the connected classes. I assume that some of developers would still use the connected classes. I also purchased "ADO.NET in a nutshell" by B. Himilton and M. MacDonald. They are pretty good in giving me better ideas of what are ADO.NET and and some points of how it would be used in the real world.
Rating: - Who Cares about Typos? Great Book!
This book is quick, it is made for the programmer with past experince looking to upgrade their skill set. I love the way that Mr. Liberty divides the book into sections. Allowing you to skip stuff you already know and only read what you wish to learn/remeber.
The way that he includes information about ADO.net and ASP.net is great as it allows me. To see where I could go with this language, and some of the things I can do.
His use of code is the way it should be. Small snipets that refer to exactly what he is talking about. I have caught some mistakes but as I said I am a PROGRAMMER, so I caught them quickly. Besides they are small and would have been caught by the compiler anyways.
The size is exactly what it needs to be. C# is a rather large language so there are quite a few things to be covered. As well as that Mr. Liberty adds small sections to allow for review of important concepts eg OO.
The final section is rather advanced and I personall skipped it. But I have a feeling that I will come to a point when I will have to go back and review it.
Rating:  - 3RD EDITION IS FULL OF TYPOS
I returned this book after 2 days because of the numerous typos and other glaring errors.
The ratio of obvious errors to good tips is about 1:1 for the first three chapters and I assume this holds true for the rest of the book. I don't know if these errors were introduced in the 3rd edition or if they are carry-overs from previous editions, but the number of errors is just unacceptable.
If the errors and typos are corrected, this book would rate at least 4 stars.
|
