Rating: 
Summary: Incomplete and written in haste
Review: After reading VB.Net by Fransesco Balena, this one was its poor cousin. If anyone were to get into the ADO.Net chapter, that persons database access knowledge is bound to get scarred for life. Majority of the samples dont work. take a rain check.
Rating: 
Summary: Great Book for All , Novices and Experienced Developers
Review: Awesome [...] book for all , The quality content and the mater coverage is excellent and good book , 5 stars for this book
Rating:
Summary: Great BOOK n GREAT PRICE
Review: COMPLETE COVERAGE OF VB.NET, FROM BASICS TO ADVANCED. GOOD MUST HAVE FOR YOUR .NET COLLECTION, IT WOULD BE BETTER IF YOU STUDY THIS BOOK WITH WROX VB.NET BOOKS. THIS BOOKS IS A MASTERPIECE.
Rating:
Summary: VB .NET power
Review: I got this book several days ago. At the first look book is very good. There is a big difference between VB6 and VB .NET and this book will show you more than you will find in any other book written for VB .NET so far. 1240 pages, 50 chapters, source code at companion web site. I have seen MOC 2373 Object Oriented Programming using Visual Basic .NET and some other books. This book will help me (probably you too) to learn new product and hopefully pass future MCSD certification exams.
Rating:
Summary: Misses the Mark
Review: I guess that I am the exception here, since everyone else seems to love this book. I thought that the book was not very well put together. Let me give you some concrete examples:First, I think that it has already been said that this book does not have enough OOP. That is probably true. I have been doing OOP for so long that I didn't miss the omission, but it might be a little frustrating for a novice. There are also a lot of little things that I noticed. Much of the book seems to be a reprinting of the .NET SDK documentation. Another thing that bothered me quite a bit is that in their tables that list the methods of classes, they didn't list the return values of the methods. This may seem like a little thing, but it meant that I had to go look everything up in the SDK anyway, so after a while I ditched the book and just used the SDK. Another thing that I noticed was some incorrect terminology. As an example, Mr. Beres refers to the System.IO.Directory class as a "static" class. I knew what he meant, because I am also a Java programmer, but that terminology is not used in VB.NET. That could be very confusing because there is no such thing as a static class in VB.NET. VB used to support static methods, but static in this sense meant something completely different than what Mr. Beres is trying to express. I believe that he meant that the class consists only of Shared methods, not that it is a static class. Again, I don't mean to nitpick here, because there were some good things, too. I have also written books for a competing publisher, so I know how hard it is to get everything just right (trust me folks, its not as easy as it looks!), and the authors have done an admirable job. It's just that better attention to detail as well as more consideration of the audience could have made this book so much better.
Rating:
Summary: Misses the Mark
Review: I guess that I am the exception here, since everyone else seems to love this book. I thought that the book was not very well put together. Let me give you some concrete examples: First, I think that it has already been said that this book does not have enough OOP. That is probably true. I have been doing OOP for so long that I didn't miss the omission, but it might be a little frustrating for a novice. There are also a lot of little things that I noticed. Much of the book seems to be a reprinting of the .NET SDK documentation. Another thing that bothered me quite a bit is that in their tables that list the methods of classes, they didn't list the return values of the methods. This may seem like a little thing, but it meant that I had to go look everything up in the SDK anyway, so after a while I ditched the book and just used the SDK. Another thing that I noticed was some incorrect terminology. As an example, Mr. Beres refers to the System.IO.Directory class as a "static" class. I knew what he meant, because I am also a Java programmer, but that terminology is not used in VB.NET. That could be very confusing because there is no such thing as a static class in VB.NET. VB used to support static methods, but static in this sense meant something completely different than what Mr. Beres is trying to express. I believe that he meant that the class consists only of Shared methods, not that it is a static class. Again, I don't mean to nitpick here, because there were some good things, too. I have also written books for a competing publisher, so I know how hard it is to get everything just right (trust me folks, its not as easy as it looks!), and the authors have done an admirable job. It's just that better attention to detail as well as more consideration of the audience could have made this book so much better.
Rating:
Summary: Great Balance of Reference and Tutorial
Review: I like how this book has attained a good balance of being a tutorial and reference book. It has many great examples and does a great job of explaining how to better understand how to develop in .NET!!!
Rating:
Summary: Great Balance of Reference and Tutorial
Review: I like how this book has attained a good balance of being a tutorial and reference book. It has many great examples and does a great job of explaining how to better understand how to develop in .NET!!!
Rating:
Summary: ignore the stars
Review: I only read two chapters of this book for ADO.Net and Multithreading. I would have to say that the ADO.Net section was good. On the otherhand, the Multithreading section was very skimpy, but it does show the reader where to start.
Rating:
Summary: Totally Complete!
Review: I thought the book was well written and very informative. Yes, I agree that it lacks a complete OO discussion, but if you want that get an OOP book. Besides that I think they cover both the language and the IDE very well, with good examples and good discussion. Additionaly the book makes a great reference to the language and IDE after your done reading it completely.
| 
