Rating: 
Summary: good and bad. I recommend another book in addition to this
Review: Not a bad book. Just typing the code, without reading all of the explanations, helped me piece together what was being illustrated, and that's a big plus. I come from vb background and have been programmer for many years. On the minus, there were certain pieces of code which were not clear (for example, using of shared members without introducing what shared members were). Some examples did not work on my computer, although the folks at experts-exchange.com were able to help me. The book does have syntax errors but microsoft has not made public any fixes to the book material. The books starts to use very many complex objects, such as drawing objects, etc. without introducing them. In practical, day to day programming, you will not likely need to use drawing objects. It would have been nice to not use these objects to illustrate the concepts being presented. Some of the objects at the end of the book seemed very complex...there seemed to be lack of clarity about getting a stream and assigning a stream etc. when demonstrating usage of ado.net. Any objects used by the author should have been first introduced, and explained to the reader, in detail. The author did not do this. Still, just typing all the code and going through the exercizes, I did learn "alot" -- well, you know how the computer field is, "alot" is a relative term; there's so much more to learn than this to prepare for the .net world. I recommend Murach's vb.net database programming with ado.net. Haven't read it yet, but it seems to have excellent reviews and covers just about everything that you will need to know as a vb.net/asp web developer...
Rating: 
Summary: Good could be better
Review: Overall a good book. I like the hands-on style of explaining things. The author does not give you wooden definitions but talks in a practical manner. e.g. "A constructor is block of code that executes when you use the new keyword to create an instance of a class." I ve never read such a clear and to the point explanation of a constructor before. The text is full of tips and established practices that I found particularly helpfull. The negative is that lots of things are not explained. The logic and whys behind some of the code are simply missing, which is a shame since the author is a skillful one. This book could easily get a 5 star rating if it were not for this. I d actually give 3,5. I haven't read other books on OOP and .NET but I think this one is worth its money.
Rating:
Summary: Good could be better
Review: Overall a good book. I like the hands-on style of explaining things. The author does not give you wooden definitions but talks in a practical manner. e.g. "A constructor is block of code that executes when you use the new keyword to create an instance of a class." I ve never read such a clear and to the point explanation of a constructor before. The text is full of tips and established practices that I found particularly helpfull. The negative is that lots of things are not explained. The logic and whys behind some of the code are simply missing, which is a shame since the author is a skillful one. This book could easily get a 5 star rating if it were not for this. I d actually give 3,5. I haven't read other books on OOP and .NET but I think this one is worth its money.
Rating:
Summary: Good for entry level programmer
Review: the book is pretty good, if you're new to Object Oriented methodology, otherwise it's a waste of money.
Rating: 
Summary: Do Not Buy This Book - Very Poorly Written
Review: This book has 2 problems first the examples are not very successful choice. Also the author did not spend much time to explain the analysis process of each problem and how he / she approach the problem. Otherwise the book gives you a good introduction to OOP and how you can implement that.
Rating:
Summary: Average book on OOP
Review: This book has 2 problems first the examples are not very successful choice. Also the author did not spend much time to explain the analysis process of each problem and how he / she approach the problem. Otherwise the book gives you a good introduction to OOP and how you can implement that.
Rating: 
Summary: Excellent for VBers moving to DotNet
Review: This book is an excellent tutorial for VBers who are moving to DotNet and who want to break all the bad habits picked up over the years. I have, by the way, just described myself. The book does a very good job bringing object theory down to earth and showing how to implement objects in both VB.Net and C#. If you are new to objects, this book will show you why object programmers swear by the approach--it really does make it easier to write scalable, reusable code. It also helps the developer avoid the "house of cards" syndrome as a program grows beyond its original scope. If you have had plenty of object theory, but struggle to translate objects to code, this book will get you over the hump. Examples show how to implement inheritance, acggregation, and association. I would recommend starting with this book, then reading Rosenberg, "Use Case Driven Object Modeling With UML", which teaches an object-oriented development process. Fowler, "UML Distilled" is another great text. Finally, dig into Gamma et al (the "Gang of Four"), "Design Patterns". These books really will change the way you code. Postscript: Having worked through the examples in the first half of the book, I continue to be impressed. Reynolds-Haertle does a very nice job of illustrating most of the constructs one uses to get day-to-day jobs done. For example, she includes several examples of collections built with the .Net ArrayList construct. Later, she shows an example of a collection built with a Dictionary construct, and discusses benefits and drawbacks of each type. If you are a VBer who (like me) is somewhat bewildered by the collection classes in .Net, this book does a very nice job sorting them out.
Rating:
Summary: GREAT ! though just a little too much C#-code typo's
Review: This book is really great, specially if you are - like me - a little unsure about your OO skills. Of course everybody heared about OO-stuff, and some (me included) have a fairly good idea what it all is about, but how to produce it yourself is something completely different.
This book helped me to get a better understanding of OO, and also learned me a lot of things I now use daily. For Dutch-reading people there is even a Dutch version of this book on the market. This makes it even easier to understand everything better The only thing I didn't like - and that's the reason why I only gave 4 stars - is that the book was FULL of C#-code typo's. Maybe this happened in the Dutch translation procedure... I don't know... but a lot of those small typos (non of them were severe - and because the book explains everything very good they were easily correctable - made it sometimes a little bit unpleasant to read. GREAT BOOK ! A MUST IF YOU DON'T KNOW ENOUGH ABOUT IT.
Rating:
Summary: OOP in a nutshell
Review: this book teaches you two languages c# and vb.net as well as OOP.
A very good book but not as simple as some ppl have put it to be but on the whole very well thought out
Rating:
Summary: Great tutorial on object oriented programming
Review: This book was extremely helpful to me in getting my feet wet in object eriented programming. I have always written in languages that didn't have objects so I knew programming but was not sure how to translate the problem into objects and books that teach object oriented languages didn't seem to discuss the subject much. This book, however, gave me the basics in a clear and understandable way. I am now ready for a more involved look at object oriented programming. Highly recommended!!
| 
