Rating: 
Summary: Great Book
Review: I'm only on page 188 of this book, but it has already cut to the chase and given me so much good theory. The author doesn't jump into overly-complex topics too soon, nor does he keep you in "Hello World" mode for 188 pages. If the rest of the book is as good as the beginning, I got my money's worth. Actually, I think I already did. ...
Rating:
Summary: Key practical resource for the hard-core VB developer
Review: If you are tired of worthless first-peek .NET books, this is the one to buy. I found the content to be excellent and the format good for picking and choosing what I needed. I particularly like Mr. Troelsen's approach of doing code by hand first before going through the VS.NET wizards. Some of the single-chapter intros to .NET technologies were better than entire books I've read on the subject (quite a feat!). This is a great practical companion to Dan Appleman's "Moving to VB.NET" which does a great job providing the theory behind .NET in general and VB.NET specifically. Let's hope Mr. Troelson writes some follow-up books on the subjects he dealt with in one chapter in this book (may I suggest GDI+).
Rating:
Summary: Good Stuff
Review: Not bad. Covers a lot of stuff. Worth of money.
Rating:
Summary: BE PROF, IN VB.NET ALSO THE .NET PLATFORM
Review: oh my god this books 100% make anyone a prof in vb.net,i cann't imagine how MR Andrew gather all of this informations and concepts in one book without keeping it in a database:)great book for anybody just if you need to be a prof in VB.NET study this book don't read it because it's has a lot of information and you need it in your career,i want to say something for the great author MR Andrew,you are the best author in vb.net and we are waiting for further books from you
Rating: 
Summary: Great at Firts
Review: Overall this is a pretty good book but unfortunately it falls apart at the end. The first 2/3 of this book are very detailed and complete with most things shown from both the command line as well as from the IDE, but, I can only guess that the author got tired (the book is over 1,000 pages) and got a little sloppy for the last 1/3. Unfortunately, the last 1/3 has important topics like ADO.NET and ASP.NET. These are not covered nearly as well as the earlier topics. In addition, the author puts things like parameters in the code that he never bothers to explain. Perhaps he figures that by this point you should be knowledgeable enough to figure things out by yourself but I think he just got tired. Also, unfortunately, the number of errors goes up considerably in the last 1/3 of the book. Most frustrating is the fact that I took time to send the problems and corrections to the author and despite the fact that the publisher claims he will get errors corrected on the web site within 48 hours, none of my corrections ever appeared. Some were very blatant like a C# listing that should have been in VB.NET. Of course, it was pretty obvious that this was the VB version of his original C# text given this and many other smaller but similar errors. Still, overall, its a pretty good book but authors should keep their errata up to date and the editor should have caught many of these mistakes if they put any effort into the proof reading. I also think many of these early authors and publishers spent so much time figuring out how to do things prior to the release of the VS IDE that they feel compelled to tell you about things that took them a long time to figure out from the command line even though the IDE makes it so much simpler now. This exercise is insightful for teaching you more about how .NET really works but it gets tedious after a while. I would rather they spent the time making sure the book was correct and complete. Again, it is a pretty good book but if the author could have persevered until the end and if he would keep his errata up to date it would have been really excellent.
Rating:
Summary: Great at Firts
Review: Overall this is a pretty good book but unfortunately it falls apart at the end. The first 2/3 of this book are very detailed and complete with most things shown from both the command line as well as from the IDE, but, I can only guess that the author got tired (the book is over 1,000 pages) and got a little sloppy for the last 1/3. Unfortunately, the last 1/3 has important topics like ADO.NET and ASP.NET. These are not covered nearly as well as the earlier topics. In addition, the author puts things like parameters in the code that he never bothers to explain. Perhaps he figures that by this point you should be knowledgeable enough to figure things out by yourself but I think he just got tired. Also, unfortunately, the number of errors goes up considerably in the last 1/3 of the book. Most frustrating is the fact that I took time to send the problems and corrections to the author and despite the fact that the publisher claims he will get errors corrected on the web site within 48 hours, none of my corrections ever appeared. Some were very blatant like a C# listing that should have been in VB.NET. Of course, it was pretty obvious that this was the VB version of his original C# text given this and many other smaller but similar errors. Still, overall, its a pretty good book but authors should keep their errata up to date and the editor should have caught many of these mistakes if they put any effort into the proof reading. I also think many of these early authors and publishers spent so much time figuring out how to do things prior to the release of the VS IDE that they feel compelled to tell you about things that took them a long time to figure out from the command line even though the IDE makes it so much simpler now. This exercise is insightful for teaching you more about how .NET really works but it gets tedious after a while. I would rather they spent the time making sure the book was correct and complete. Again, it is a pretty good book but if the author could have persevered until the end and if he would keep his errata up to date it would have been really excellent.
Rating:
Summary: Great OO coverage but is missing some critical topics
Review: Overall, I think the book does a very good job helping those who come from the non-OO background (especially VB 6) into understanding the OO facets of VB.NET. I think that is where this book is the most solid. The first seven chapters or so you'll think it's a 4-5 star book, however it falls off after that. My reasoning for this is that coverage on debugging and deploying .NET applications is basically non-existent. Although the coverage on tracing was a little better, it could have been stronger and far from made up for the missing coverage of former items. Also, the ADO.NET coverage was waaaaaaaaaay too brief. For such a critical part of what MOST developers are will be using for the systems they develop (unless of course you're a game developer), I thought it was pretty bad to only have a pretty short chapter on a technology that is so critical and has been totally revamped. One could say that you should consult other books for that coverage, but I disagree because these items are critical to any VB.NET application. If that was the case, they could have just cut out almost half of this book. If you've taken any of the good practice tests, you how important MSFT thinks the stuff this book is missing is. A better overall book is the core reference, but I still give this one three stars because the coverage for the first 7-8 chapters if very good.
Rating:
Summary: Great OO coverage but is missing some critical topics
Review: Overall, I think the book does a very good job helping those who come from the non-OO background (especially VB 6) into understanding the OO facets of VB.NET. I think that is where this book is the most solid. The first seven chapters or so you'll think it's a 4-5 star book, however it falls off after that. My reasoning for this is that coverage on debugging and deploying .NET applications is basically non-existent. Although the coverage on tracing was a little better, it could have been stronger and far from made up for the missing coverage of former items. Also, the ADO.NET coverage was waaaaaaaaaay too brief. For such a critical part of what MOST developers are will be using for the systems they develop (unless of course you're a game developer), I thought it was pretty bad to only have a pretty short chapter on a technology that is so critical and has been totally revamped. One could say that you should consult other books for that coverage, but I disagree because these items are critical to any VB.NET application. If that was the case, they could have just cut out almost half of this book. If you've taken any of the good practice tests, you how important MSFT thinks the stuff this book is missing is. A better overall book is the core reference, but I still give this one three stars because the coverage for the first 7-8 chapters if very good.
Rating:
Summary: Best VB.NET book I've seen
Review: So far(I'm still only in chapter 5) this VB.NET Book has been hands down better than any others I have seen. I am hoping that the rest of the book follows suit. I think that this book will be invaluable as I learn the new material and a great reference once I finished reading it.
Rating:
Summary: This book is not clear enough.
Review: the quality of the graphic (snapshot) of the 157 first page are fuzzy. This book have good information but need clear technical summary subject by subject. The reader may be lost. This book is not clear enough
| 
