Errata
The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".
The following errata were submitted by our customers and approved as valid errors by the author or editor.
Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted By | Date submitted | Date corrected |
---|---|---|---|---|---|
Printed | Page 19 |
"XMLPad" should be "XAMLPad" On page 19, the third sentence in the second to the last paragraph on the page contains an incorrect name for a Windows SDK tool. Change: "You can actually define a WPF form completely by writing an XAML description if you don’t like using the Design View window of Visual Studio or if you don’t have access to Visual Studio; Microsoft provides an XAML editor called XMLPad that you can download free of charge from the MSDN Web site." To: "You can actually define a WPF form completely by writing an XAML description if you don’t like using the Design View window of Visual Studio or if you don’t have access to Visual Studio; Microsoft provides an XAML editor called XAMLPad that is installed with the Windows SDK." |
Microsoft Press | May 06, 2010 | |
Printed | Page 41 |
Parenthesis in the wrong place |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 43 |
string should be int and vise versa On page 43, the second sentence of the third paragraph is incorrect. Change: "Remember that the Text property is a string and that the result of the calculation is an int, so you must convert the string to an int before assigning it to the Text property." To: "Remember that the Text property is a string and that the result of the calculation is an int, so you must convert the int to a string before assigning it to the Text property." |
Microsoft Press | May 06, 2010 | |
Printed | Page 82 |
> should be < |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 83 Step 12 |
inRange = (lo <= number) && (hi >= number) Note from the Author or Editor: |
Anonymous | Dec 10, 2010 | |
Printed | Page 195 |
10 should be 11 On page 195, lines 10 and 17 of the code sample refer to 10 rather than 11. Change: // iterate remaining 10 elements using a for statementTo: // iterate remaining 11 elements using a for statementChange: // iterate remaining 10 using a foreach statementTo: // iterate remaining 11 using a foreach statement |
Microsoft Press | May 06, 2010 | |
Printed | Page 219 |
"Horse : Whale" should be "Whale : Mammal" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 222 |
myMammal should be new Mammal On page 222, the first line of the second code sample is incorrect. Change: Mammal myMammal = myMammal(“Mammalia”);To: Mammal myMammal = new Mammal(“Mammalia”); |
Microsoft Press | May 06, 2010 | |
Printed | Page 256 |
"public" should be removed |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 259 |
"this." should be removed On page 259, the first code sample contains several instances of "this." that should be removed. Change: class Tally { public Tally() { this.instanceCount++; } ~Tally() { this.instanceCount--; } public static int InstanceCount() { return this.instanceCount; } ... private static int instanceCount = 0; }To: class Tally { public Tally() { instanceCount++; } ~Tally() { instanceCount--; } public static int InstanceCount() { return instanceCount; } ... private static int instanceCount = 0; } |
Microsoft Press | May 06, 2010 | |
Page 299 First code example |
bool peek = bits[6]; // retrieve bool at index 6; should be true (1) Note from the Author or Editor: |
Bob Verhey | Apr 02, 2011 | ||
Printed | Page 321 |
=> missing from code sample |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 453 |
DockControl should be DockPanel On page 453, the sentence before the Note refers to DockControl rather than DockPanel. Change: "In the Properties window, set the Width property of the DockControl to Auto, set the HorizontalAlignment property to Stretch, set the VerticalAlignment property to Top, and set the Margin property to 0." To: "In the Properties window, set the Width property of the DockPanelto Auto, set the HorizontalAlignment property to Stretch, set the VerticalAlignment property to Top, and set the Margin property to 0." The sentence after the Note contains the same error. Change: "The DockControl control should appear at the top of the form, occupying the full width of the form." To: "The DockPanelcontrol should appear at the top of the form, occupying the full width of the form." |
Microsoft Press | May 06, 2010 | |
Printed | Page 459 |
newMember_Click should be exit_Click |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 465 |
clearText should be clearName On page 465, in step 4, clearText is referenced in place of clearName. Change: "Return to the definition of the textBoxMenu style, and to the clearText menu item add a Click event method called clearName_Click. (This is the default name generated by the command.) " To: "Return to the definition of the textBoxMenu style, and to the clearName menu item add a Click event method called clearName_Click. (This is the default name generated by the command.) " |
Microsoft Press | May 06, 2010 | |
Printed | Page 513 |
table should be class |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 517 |
Product should be Products On page 517, the last sentence refers to a Product table rather than a Products table. Change: "Phrasing this relationship slightly differently, a row in the Product table can reference a single row in the Suppliers table through the SupplierID columns in both tables, but a row in the Suppliers table can reference" To: "Phrasing this relationship slightly differently, a row in the Products table can reference a single row in the Suppliers table through the SupplierID columns in both tables, but a row in the Suppliers table can reference" |
Microsoft Press | May 06, 2010 | |
Printed | Page 538 |
WpfApplication1.Window1 should be Suppliers.SupplierInfo |
Microsoft Press | Jul 13, 2010 | |
Printed, PDF | Page 548 3rd & 4th paragraph |
The example on adding a new item to a table via DLINQ is using a pre-Visual Studio 2008 RTM method. The book is using the Add method but it should be InsertOnSubmit. Note from the Author or Editor: |
Steven Wiley | Mar 29, 2011 | |
Printed, PDF | Page 548 7th & 8th paragraph |
The example on removing an item from a table via DLINQ is using a pre-Visual Studio 2008 RTM method. The book is using the Remove method but it should be DeleteOnSubmit. Note from the Author or Editor: |
Steven Wiley | Mar 29, 2011 | |
Printed | Page 555 |
Additional code needed in sample On page 555, in the 13th line of the second code sample, an ArgumentOutOfRangeException must be caught for the application to function as expected. Change: productsInfo.Add(newProd);To: try { productsInfo.Add(newProd); } catch (ArgumentOutOfRangeException e) { } |
Microsoft Press | May 06, 2010 | |
Printed | Page 564 Bottom - step 4 |
Folder in sample code doesn't seem to exist. asking for ..Litware, but only the ..Completed Litware folder is on my CD. Note from the Author or Editor: |
Jonathan M. | May 28, 2011 | |
Printed | Page 633 |
Service should be ProductsService |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 634 |
Service should be ProductsService On page 634, the first line of step 11 is incorrect. Change: "Add the GetProductInfo method shown below in bold type to the Service class:" To: "Add the GetProductInfo method shown below in bold type to the ProductsService class:" Microsoft Press is committed to providing informative and accurate books. All comments and corrections listed above are ready for inclusion in future printings of this book. If you have a later printing of this book, it may already contain most or all of the above corrections. |
Microsoft Press | May 06, 2010 |