Full of typos. Most are obvious (e.g. variable names not matching declarations) and show lack of proof-reading. It is merely annoying that many code samples don't match the hard-to-read screen shots (why show me a screen shot if it is hard to read and not a match?).They throw in many code items not yet explained. I understand some are inevitable but many are avoidable. The exercises in a good book should reinforce on what is already taught, not confuse the reader with advanced garbage. For example, the "pop-up ad blocker" exercise is chock full of Windows API calls way ahead of the coding explanation. A more appropriate alternate exercise could be imagined. The authors want to impress us with what VB .NET is capable of instead of just grinding through the basics. I can read the VB help files if I want to be dazzled and confused.
They do not give enough guidelines on acceptable coding practice and alternate methods. For example, in an "If...Then" section they use a code snippet that sets a Boolean variable in the block code. Why not also show the If argument can be directly assigned to a Boolean? And then they could make a point of saying this is doable but frowned upon for reasons of clarity?
Also, in general, not enough exercises. I need the drill-instructor approach. Otherwise I just read the text and don't absorb it enough.
The typesetting is acceptable but I am not enthusiastic about their choices.
I am disappointed. There is no way to detect most of these flaws by skimming on the bookstand, only by working through the book.