F. Rodriguez said

This book is very easy to read and understand, the author uses very good methodology to explain practical examples.

I have the book Visual Basic 2005 programmer reference and practical examples as a complement to this.

Book worm said
I loved the sample and explanations on XML serialization as well as the topic on collections. What I didn't like was the their discussion of objects esp. the example - a CAR. It could have been much helpful if they had stick with the customer and bill classes. Overall, I can recommend this to programmers with experience on other languages, and it would help if you know already the basics of objects, as the discussion on classes will only be on Chapter 10. If you are a novice or VB beginner, I would advise you to buy a second book to support your learning together with this book. A good second book will be an Apress book.If you want a thorough OOP tutorial, buy Daniel Clark's Beginning OOP using Visual Basic 2005.

hpjr007 said
This book is excellent for beginners; it explains all steps in details.
It is definitively a must have!

R. Stringfellow said
I looked this book over pretty well at Borders before buying it from Amazon, but was unpleasantly surprised once I began to read it straight through. Critical information is omitted from some topics. Continuity seems illogical. And the website, though expertly administrated, has a small subscriber base. The book is not very well organized and is carelessly written. For twice the price, the Deitel offering is ten times the tome.

Daniel Appling said
I am a seasoned programmer learning the .NET platform. At first this book seemed okay...the layout was pretty good and I found their presentation methods easy to learn from. Then I started running into some serious coding problems. Their ASP code examples are outdated and riddled with errors. No error errata on the website either to fix anything I saw. I spent more time trying to fix their stuff than I did acutally learning. It would be a good book if it wasn't for all the errors. They desperately need some technical editors... I wouldn't recommend this book at all.