No project of this size can be completely without errors and this is no exception. It's sort of like writing a 300,000 word Visual Basic program without the benefit of a compiler to check your spelling and grammar. This page describes some improvements to the example programs and the mistakes found so far.
If you find other errors, please let me know.
Most of these are typos that are more annoying than confusing.
|23||Henry O'Mara noticed that the code uses MsgBox instead of MessageBox.Show. MsgBox still works and I have nothing against using older Visual Basic Classic statements when they're easier. For example, the Left function is a lot easier to use than Substring for getting the first part of a string.
But I usually use MessageBox.Show and should have here.
|26||Yoel Yaron noticed that the code in bottom shaded block of code should say "Option Infer Off" rather than "Option Explicit Off."|
|64||Yoel Yaron noticed that first sentence after the heading "Adding Controls" should say "WPF Designer" not "Windows Form Designer."|
|66||Similarly Yoel Yaron noticed that first sentence on page 66 should say "WPF Designer" not "Windows Form Designer."|
|198||Paul Moss noticed a typo. In the XAML code's RowDefinition elements, the Width property should be Height. (Rows have heights while columns have widths.)|
|287||Henry O'Mara found a typo. The text should read:
If Option Infer is on, Visual Basic may be able to deduce an explicit data type for a variable declared without a type.
|313||Henry O'Mara pointed out that this sentence in the last paragraphis kind of confusing:
When operators are on the same line, or if an expression contains more than one instance of the same operator, the program evaluates them in left-to-right order.
By "on the same line," this statement means the same line in the table that starts on the following page. For example, * and / are on the same line in that table, indicating that they have the same precedence. If those two operators appear in an expression and there are no parentheses indicating otherwise, Visual Basic evaluates the operators in left-to-right order.
Notice that the order doesn't matter for those operators anyway because. For example, (1 * 2) / 3 = 1 * (2 / 3). Similarly (1 + 2) - 3 = 1 + (2 - 3).
|992||Henry O'Mara found a confusing statement about the NumericUpDown control that basically says the Click event handler fires if the user clicks the arrow button but not if the user clicks the arrow button.
What this should have said was:
The Click event handler ... executes when the user changes the value by clicking an arrow button, but it does not execute if the user types a new value into the field or uses the arrow keys.
That's "keys" not "buttons." Thanks Henry!
If you sign up for one of my VB Helper newsletters, you will be notified when there are updates to this book.