Errata

Visual Basic 2005: A Developer's Notebook

Errata for Visual Basic 2005: A Developer's Notebook

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date submitted
Printed Page 5
4th paragraph

When an error is encountered in the sample code the Error Dialog box appears and in
order to get the 'Edit and Continue' feature of VB 2005 to work you are supposed to
click the "Enable Editing" link.

This link is not there on a fresh install of Visual Studio 2005 Pro. The 'Edit and
Continue' feature works anyway if you exit from the error dialog box and add the
correct line to code and drag the yellow pointer to it. There is no need to click an
"Enable Editing" link, that appears to be non-existant anyway.

 Anonymous   
Printed Page 17
How Do I Do That? Paragraph

The menu item View->Property Editing View doesn't exist in VS 2005. Was it dropped
from the IDE?

 Anonymous   
Printed Page 58
Evaluate Conditions Separately with Short-Circuit Logic paragraph

On page 58 the book explains that the AndAlso and OrElse logical operators are newly added in Visual Basic 2005. This is incorrect. Where I work we currently use Visual Basic 2003 / .NET 1.1 verison. In the 2003 / .NET 1.1 version the AndAlso and OrElse logical operators are present and fully functional.

I admit that I did find some MSDN links that make it appear that AndAlso and OrElse were newly added in VB 2005. But here is an MSDN link that confirms presence of AndAlso and OrElse in VB 2003:

http://msdn2.microsoft.com/en-us/library/wz3k228a(vs.71).aspx

 Anonymous   
Printed Page 83
7th line, 2nd paragraph

stop resizing ... IsSplitterFixed property to False
should be
stop resizing ... IsSplitterFixed property to True

 Anonymous   
Printed Page 185
Example source code at the bottom of the page

The "Connection = ..." statement at Public Sub Main() says:

Connection = ConfigurationSettings.AppSettings("Connection")
it should say
Connection = ConfigurationManager.AppSettings("Connection")

 Anonymous   
Printed Page 192
Section: "Edit an XML Document with XPathNavigator

The methods described (AppendChild and SetValue) exist in the 2.0 framework, but if called produce a "Specified method is not supported" exception. Microsoft apparently has not implemented the XPath update capabilities.

 Anonymous