Rating: 
Summary: Excellent
Review: This is a very well written, straight to the point book. I am able to grasp the OOP concepts as I go through the examples in the book. She provides real world examples, such as code analysis, that you can build on and improve. From reading just the first three chapters, I was able to create a cool windows application.
Rating: 
Summary: A necessity
Review: This is also a good book for VB 6.0 developers switching to VB.Net. There are good books explaining how to develop VB.Net applications. Once you're comfortable with VB.Net programming you should seriously consider making use of the OOP capabilities in this rich VB.Net environment. This book explains in clear chapters how to handle the classes you will develop and how to make use of the existing VB.Net classes in your application
The author takes you chapter by chapter through the OOP process. A must have.
Rating: 
Summary: Do Not Buy This Book - Very Poorly Written
Review: This is by far the worst OOP book on the market.
-Code samples are too long requiring too much typing.
-Many grammatical/coding errors.
-Code placement (where the block of code goes in IDE)is not well defined.
-Very choppy. The material darts around and after reading the book many of the readers I've talked to still seem lost on
object orientation. Should have taken a clue when I picked up the book turned to the second page and read "For Bruce You're Still the one."
Come on this is a technical book not "Gone With The Wind" Save yourself alot of time and money buying another book
Rating:
Summary: Certainly NOT the worst OOP book on the market...
Review: This was actually a great book for beginners! - Being an absolute programming newbie, typing all the code actually helped me better understand what I was doing. - While there was some ambiguity preventing some code from executing properly, ALL of the code on the included CDROM worked properly and helped me to troubleshoot (and better understand) the code. I think 'A reader' needs to lighten up. Dedicating a book to a loved one certainly isn't a crime, unless you're a 30+ year-old who lives with his parents. And an inflatable doll.
Rating:
Summary: Very disappointed
Review: Very ambiguous and confusing in places. Heck, page 1, paragraph 1, the author decided to use an example to illustrate what a "class" (as in the blueprint for objects) is. Unfortunately, she chooses to use a college registration illustration, which includes "classes" (as in a college classroom). She then goes on to talk about a "class" a dozen times or more, quite often not being clear if she's talking about the OOP class or the thing the student goes to. Does "class registration" mean when the student goes to sign-up for his class, or when you're initializing the class to create student objects in your code? Again, all this is page 1, paragraph 1. More examples of confusion and ambiguity show up frequently. I am disappointed.
Rating:
Summary: Very disappointed
Review: Very ambiguous and confusing in places. Heck, page 1, paragraph 1, the author decided to use an example to illustrate what a "class" (as in the blueprint for objects) is. Unfortunately, she chooses to use a college registration illustration, which includes "classes" (as in a college classroom). She then goes on to talk about a "class" a dozen times or more, quite often not being clear if she's talking about the OOP class or the thing the student goes to. Does "class registration" mean when the student goes to sign-up for his class, or when you're initializing the class to create student objects in your code? Again, all this is page 1, paragraph 1. More examples of confusion and ambiguity show up frequently. I am disappointed.
Rating:
Summary: Very disappointed
Review: Very ambiguous and confusing in places. Heck, page 1, paragraph 1, the author decided to use an example to illustrate what a "class" (as in the blueprint for objects) is. Unfortunately, she chooses to use a college registration illustration, which includes "classes" (as in a college classroom). She then goes on to talk about a "class" a dozen times or more, quite often not being clear if she's talking about the OOP class or the thing the student goes to. Does "class registration" mean when the student goes to sign-up for his class, or when you're initializing the class to create student objects in your code? Again, all this is page 1, paragraph 1. More examples of confusion and ambiguity show up frequently. I am disappointed.
| 
