Errata
Errata for MCTS Self-Paced Training Kit (Exam 70-526): Microsoft® .NET Framework 2.0 Windows®-Based Client Development
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 CD-ROM |
"ImageIndex" should be "ImageList" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page CD-ROM |
== should be != |
Microsoft Press | Jul 13, 2010 | |
Printed | Page CD-ROM |
Readiness Review incorrect answer marked as correct |
Microsoft Press | Jul 13, 2010 | |
Printed | Page CD-ROM |
Print should be PrintPage |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 22 and 23 |
Incorrect code in C# answers |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 31 |
TopBottom should be replaced with TopDown |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 38 |
the words False and True should be reversed |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 44 |
The word "on" in missing from answer B to question 3 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 56 |
spacing should be alignment |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 75 |
right should be left |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 96 |
MultiSelect should be MultiExtended |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 98 |
Multiple errors in Table 3-2 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 102 |
ListBox1.IndexOf should be ListBox1.Items.IndexOf |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 111 |
Incorrect description for Parent property in Table 3-7 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 129 |
"IndexKey" should be "ImageKey" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 138 |
Incorrect character used in Size property |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 156 |
Sample BMP files not located on Companion CD |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 164 |
"enabled" should be "displayed" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 168 |
"UnChecked" should be "Unchecked" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 189 |
Incorrect operator used in C# Step 2 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 203 |
"State" property includes incorrect description |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 233 |
Invalid character in Button 3 property names |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 257 |
"DML" used in place of "DDL" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 261 |
"Figure 6-2" should be "Table 6-5" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 263 |
Missing quotation in C# code |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 275 |
SqlParameter used in place of SqlCommand |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 340 |
Sql1 referenced in place of SqlDataAdapter1 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 360 |
Sql1.UpdateCommand should be SqlDataAdapter1.UpdateCommand |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 369 |
SqlDataAdapter should be SqlDataAdapter1 |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 390 |
C# code contains an error |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 457 & 458 |
"myReader" should be "myWriter" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 539 |
"Label2" and "Label 4" should be "Label1" and "Label3" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 545 |
Multiple errors in C# code sample |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 561 |
"TabOrder" referenced in place of "TabIndex" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 571 |
Incorrect value used in AutoPopDelay property formula |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 597 |
"must" is used in place of "most" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 653 |
"overrides" should be "override" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 691 |
"SplitControl" should be "SplitContainer" |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 707 |
ODBC should be Oracle and vice versa |
Microsoft Press | Jul 13, 2010 | |
Printed | Page 729 |
IsMdiContainer referred to as IsMdiParent |
Microsoft Press | Jul 13, 2010 | |
Other Digital Version | CD-ROM |
Missing files needed for Lesson 4 in Chapter 6 |
Microsoft Press | May 06, 2010 | |
Other Digital Version | CD-ROM |
"composite" should be "custom" In the Readiness Review assessment, Question 27 (526P_6.1.7_01) uses an incorrect control. Change: "You are creating a composite control. You want to provide a transparent background color. How can you do this? (Choose all that apply.)" To: "You are creating a custom control. You want to provide a transparent background color. How can you do this? (Choose all that apply.)" |
Microsoft Press | May 06, 2010 | |
Other Digital Version | CD-ROM |
Readiness Review answer incorrectly marked correct One of the questions on the Readiness Review Assessment has an incorrect answer marked as correct. The question reads: "You are creating a Windows Forms application that will be deployed to a kiosk environment. The application will be used by thousands of people, including users who have unique visual requirements such as using High Contrast mode. While developing your application, which of the following guidelines should you follow to ensure that the application will work well in High Contrast mode? (Choose all that apply.)" The following answer should be incorrect: "Convey by visual cues or sound any information that is conveyed through color." |
Microsoft Press | May 06, 2010 | |
Other Digital Version | CD-ROM |
Readiness Review correct answer marked as incorrect On the Readiness Review Assessment, one of the questions has an correct answer marked as incorrect. The question reads: "You want to specify a custom icon for your application's shortcut on the Start menu. Which file types can you choose to specify an icon? (Choose all that apply.)" The following answer should be marked as correct: ".ico" |
Microsoft Press | May 06, 2010 | |
Printed | Page 19 |
Property Grid used in place of Toolbox On page 19, the first sentence of Step 4 reads: "Drag a Button from the Property Grid to the upper left-hand corner of the form." It should read: "Drag a Button from the Toolbox to the upper left-hand corner of the form." |
Microsoft Press | May 06, 2010 | |
Printed | Page 25 |
Select should be Double-click On page 25, the third bullet point is incorrect. Change: "Select a control in the Toolbox and double-click the form." To: "Double-click a control in the Toolbox." |
Microsoft Press | May 06, 2010 | |
Printed | Page 33 |
Column numbering stated to begin at 1 rather than 0 On page 33, the first two sentences of the fourth paragraph read: "Columns in a TableLayoutPanel are numbers starting at 1, while rows start at 0. Thus, the example shown above adds aButton to the cell in column 3 at row 3, which is actually the 3rd column and the 4th row the user sees." It should read: "Columns and rows in a TableLayoutPanel are numbers starting at 0. Thus, the example shown above adds aButton to the cell in column 3 at row 3, which is actually the 4th column and the 4th row the user sees." |
Microsoft Press | May 06, 2010 | |
Printed | Page 43 |
True missing from code sample On page 43, Answer C to question 1 is missing a parameter. Change: ' VB FLPanel1.SetFlowBreak(aButton) // C# FLPanel1.SetFlowBreak(aButton);To: ' VB FLPanel1.SetFlowBreak(aButton, True) // C# FLPanel1.SetFlowBreak(aButton, true); |
Microsoft Press | May 06, 2010 | |
Printed | Page 53 |
TabOrder should be replaced with TabIndex On page 53, the 5th property in Tabel 2-1 reads: "TabOrder" It should read: "TabIndex" |
Microsoft Press | May 06, 2010 | |
Printed | Page 69 |
MouseClickEventArgs should be replaced with MouseEventArgs On page 69, the first sentence of the 2nd paragraph reads: "One of the arguments for the Button.MouseDown event handler is an instance of MourseClickEventArgs." It should read: "One of the arguments for the Button.MouseDown event handler is an instance of MourseEventArgs." The last sentence of the 2nd paragraph reads: "Table 2-3 describes the properties of the MourseClickEventArgs class." It should read: "Table 2-3 describes the properties of the MourseEventArgs class." The first sentence of the 3rd paragraph reads: "Using the values exposed by the MouseClickEventArgs instance, you can determine the button that was clicked and the position of the mouse wheel." It should read: "Using the values exposed by the MouseEventArgs instance, you can determine the button that was clicked and the position of the mouse wheel." |
Microsoft Press | May 06, 2010 | |
Printed | Page 85 |
$12,345.00 should be $12,345.67 On page 85, the ammount indicated in the Displayed Text column of the $99,999.00 row is incorrect. Change: "$12,345.00 – Note that the actual currency symbol, thousands separator, and decimal separator will be determined by the control’s FormatProvider." To: "$12,345.67 – Note that the actual currency symbol, thousands separator, and decimal separator will be determined by the control’s FormatProvider." |
Microsoft Press | May 06, 2010 | |
Printed | Page 97 |
Single should be One On page 97, the second sentence of the description of SelectionMode in Table 3-1 is incorrect. Change:"Can be set to None, Single, MultiSimple, or MultiExtended. MultiSimple allows the selection of multiple objects, and MultiExtend allows the use of the Shift and Ctrl keys when making multiple selections." To: "Can be set to None, One, MultiSimple, or MultiExtended. MultiSimple allows the selection of multiple objects, and MultiExtend allows the use of the Shift and Ctrl keys when making multiple selections." |
Microsoft Press | May 06, 2010 | |
Printed | Page 99 |
MultiSelect should be MultiExtended On page 99, the SelectedIndex and SelectedItem descriptions in Table 3-3 are incorrect. Change: "SelectedIndex Gets the index of the selected item, or, if the SelectionMode property is set to MultiSimple or MultiSelect, it can return any selected index. SelectedItem Returns the selected item, or, if the SelectionMode property is set to MultiSimple or MultiSelect, it can return any selected item." To: "SelectedIndex Gets the index of the selected item, or, if the SelectionMode property is set to MultiSimple or MultiExtended, it can return any selected index. SelectedItem Returns the selected item, or, if the SelectionMode property is set to MultiSimple or MultiExtended, it can return any selected item." |
Microsoft Press | May 06, 2010 | |
Printed | Page 109 |
null should be -1 On page 109, the second sentence of the ImageKey property in Table 3-6 contains an incorrect property. Change: "If the ImageKey property is set, the ImageIndex property is set to null." To: "If the ImageKey property is set, the ImageIndex property is set to -1." |
Microsoft Press | May 06, 2010 | |
Printed | Page 111 |
Incorrect description for PrevNode property in Table 3-7 On page 111, the description for the PrevNode property in Table 3-7 is incorrect. Change: "Returns the previous node." To: "Returns the previous sibling tree node." |
Microsoft Press | May 06, 2010 | |
Printed | Page 132 |
"ImageIndex" should be "ImageList" On page 132, Question 3 Answer D contains an incorrect C# component. Change: D. ' VB Button1.ImageList = ImageList1 Button1.ImageKey = "myImage" // C# button1.ImageIndex = imageList1; button1.ImageKey = "myImage";To: D. ' VB Button1.ImageList = ImageList1 Button1.ImageKey = "myImage" // C# button1.ImageList = imageList1; button1.ImageKey = "myImage"; |
Microsoft Press | May 06, 2010 | |
Printed | Page 154 |
containers should be panels On page 154, the last sentence of the second paragraph contains and incorrect Tool Strip type. Change: "This results in the ToolStripContainer filling the entire form and having tool strip containers available on all sides." To: "This results in the ToolStripContainer filling the entire form and having tool strip panels available on all sides." |
Microsoft Press | May 06, 2010 | |
Printed | Page 162 |
Incorrect capitalization in the word Flow On page 162, in the description for the property LayoutStyle the F in "HorizontalStackWithOverFlow" and "Vertical- StackWithOverFlow" should not be capitalized. Change: "A value of HorizontalStackWithOverFlow indicates that items are stacked horizontally and overflow as needed. Vertical- StackWithOverFlow stacks items vertically and overflows as needed." To: "A value of HorizontalStackWithOverflow indicates that items are stacked horizontally and overflow as needed. Vertical- StackWithOverflow stacks items vertically and overflows as needed." |
Microsoft Press | May 06, 2010 | |
Printed | Page 165 |
"FileToolStripMenuItem" should be "fileToolStripMenuItem" On page 165, in the second sentence at the top of the page the variable FileToolStripMenuItem has an incorrect capitalization. Change: "For example, if you created a File menu item, the default name would be FileToolStripMenuItem." To: "For example, if you created a File menu item, the default name would be fileToolStripMenuItem." |
Microsoft Press | May 06, 2010 | |
Printed | Page 183 |
"event" should be "method" On page 183, the second sentence in Step 4 incorrectly uses the word "event". Change: "Choose the event you created in the Code Editor." To: "Choose the method you created in the Code Editor." |
Microsoft Press | May 06, 2010 | |
Printed | Page 196 |
"MergeItem" should be "MergeAction" On page 196, the first bullet point under Suggested Practices contains an incorrect property. Change: "Create toolbars with similar members and practice merging them together, changing the MergeIndex and MergeItem properties of each tool strip item." To: "Create toolbars with similar members and practice merging them together, changing the MergeIndex and MergeAction properties of each tool strip item." |
Microsoft Press | May 06, 2010 | |
Printed | Page 206 |
Missing characters in C# code sample On page 206, the C# code sample near the top of the page is missing closing characters and is incomplete. Change: // C# private OracleConnection ConnectionToOracle = new OracleConnection ("Data Source=Oracle8i;Integrated Security=yes; To: // C# private OracleConnection ConnectionToOracle = new OracleConnection ("Data Source=Oracle8i;Integrated Security=yes"); |
Microsoft Press | May 06, 2010 | |
Printed | Page 236, Question 1 |
Answer concerning error range 20-29 is incorrect On page 236, answers C and D of Question 1 reads: "C. Errors with a severity level of 20 through 29 D. Errors with a severity level of 30 or greater" They should read: "C. Errors with a severity level of 20 through 25 D. Errors with a severity level of 26 or greater" |
Microsoft Press | May 06, 2010 | |
Printed | Page 260 |
"DDL" used in place of "DML" On page 260, the third paragraph reads: "Each .NET Framework Data Provider Command object exposes three main execution methods that can be used to return data, update data, call stored procedures and functions, and so on, or perform catalog operations such as executing data definition language (DDL) commands against a data source." It should read: "Each .NET Framework Data Provider Command object exposes three main execution methods that can be used to return data, update data, call stored procedures and functions, and so on, or perform catalog operations such as executing data manipulation language (DML) commands against a data source." |
Microsoft Press | May 06, 2010 | |
Printed | Page 262 |
Missing restriction in Table 6-6 On page 262, on Table 6-6 the commands BeginExecuteXMLReader and EndExecuteXMLReader are missing the note (SQLCommand only). Change: BeginExecuteXmlReader To: BeginExecuteXmlReader (SQLCommand only) Change: EndExecuteXMLReader To: EndExecuteXMLReader (SQLCommand only) |
Microsoft Press | May 06, 2010 | |
Printed | Page 263 |
Wrong loop end in C# code On page 263, the 16th line down in the C# code sample contains an incorrect loop end. Change: for (int i = 0; iTo: for (int i = 0; i |
Microsoft Press | May 06, 2010 | |
Printed | Page 285 |
Stored procedures missing in Northwind Database On page 285, in order to complete Exercise 3 you might have to create stored procedures in the Northwind Database for Get Freight Cost and Get Contact Name. To create the GetFreightCost stored procedure use the following code: CREATE PROCEDURE GetFreightCost @ORDERID INT, @Freight MONEY OUTPUT AS SELECT @Freight = Freight FROM Orders WHERE OrderID = @OrderIDTo create the GetContactName stored procedure use the following code: CREATE PROCEDURE GetContactName @Name NVARCHAR(40) OUTPUT AS SELECT @Name = ContactName FROM Customers WHERE CompanyName = @Name 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 | |
Printed | Page 319 |
Definition of "Serializable" is incorrect On page 319, the definition of Serializable reads: "Locks are placed on all data that is used in a query, preventing other users from updating the data. Prevents non-repeatable reads but phantom rows are still possible." It should read: "A range lock is placed on the DataSet, preventing other users from updating or inserting rows into the dataset until the transaction is complete." |
Microsoft Press | May 06, 2010 | |
Printed | Page 352 |
ForeignKey class referenced in place of ForeignKeyConstraint On page 352, the first sentence of the "How to Create a Foreign Key Constraint" section reads: "Create foreign key constraints by creating an instance of the ForeignKey class and assigning the desired column or columns from the parent and child tables to the constraint." It should read: "Create foreign key constraints by creating an instance of the ForeignKeyConstraint class and assigning the desired column or columns from the parent and child tables to the constraint." |
Microsoft Press | May 06, 2010 | |
Printed | Page 366 |
Code causes records to not save On page 366, in Step 23 the last 3 lines of code in the VB and C# code example causes records to not be saved in Step 27. Remove the following lines from the VB example: ' After the row is updated reset the table to reflect the changes NorthwindDataSet1.Customers.Clear() SqlDataAdapter1.Fill(NorthwindDataSet1.Customers)Remove the following lines from the C# example: // After the row is updated reset the table to reflect the changes northwindDataSet1.Customers.Clear(); sqlDataAdapter1.Fill(northwindDataSet1.Customers); |
Microsoft Press | May 06, 2010 | |
Printed | Page 370 |
Additional Provider information needed in VB and C# code On page 370, a NOTE needs to be added to step 7 that reads: "NOTE: If you are using SQL Server 7, SQL Server 2000 or SQL Server 2005 (all editions) you must change the Provider in line 5 of the VB and C# code to SQLNCLI instead of SQLOLEDB." |
Microsoft Press | May 06, 2010 | |
Printed | Page 418 |
Incorrect capitalization in the code sample On page 418, the C# code sample reads: customersBindingSource = New BindingSource(northwindDataSet1, "Customers");It should read: customersBindingSource = new BindingSource(northwindDataSet1, "Customers"); |
Microsoft Press | May 06, 2010 | |
Printed | Page 463 |
InnerXml should be ReadInnerXml and OuterXml should be ReadOuterXml On page 463, answers C & D to Question 2 contain incorrect methods. Change: C. ' VB myReader.MoveToAttribute("length") MsgBox(myReader.InnerXml) // C# myReader.MoveToAttribute("length"); MessageBox.Show(myReader.InnerXml); D. ' VB myReader.MoveToAttribute("length") MsgBox(myReader.OuterXml) // C# myReader.MoveToAttribute("length"); MessageBox.Show(myReader.OuterXml); To: C. ' VB myReader.MoveToAttribute("length") MsgBox(myReader.ReadInnerXml) // C# myReader.MoveToAttribute("length"); MessageBox.Show(myReader.ReadInnerXml); D. ' VB myReader.MoveToAttribute("length") MsgBox(myReader.ReadOuterXml) // C# myReader.MoveToAttribute("length"); MessageBox.Show(myReader.ReadOuterXml); |
Microsoft Press | May 06, 2010 | |
Printed | Page 544 |
Incorrect instruction for setting the MdiParent property On page 544, step 3 reads: "In a method in the parent form, such as a menu item Click event handler, create a new instance of the child form and set its MdiParent property to True, as shown in the following example:" It should read: "In a method in the parent form, such as a menu item Click event handler, create a new instance of the child form and set its MdiParent property, as shown in the following example:" |
Microsoft Press | May 06, 2010 | |
Printed | Page 549 |
IsMdiContainer referred to as IsMdiParent On page 549, answer A to question 1 reads: "Set the IsMdiParent property of the parent form to True." It should read: "Set the IsMdiContainer property of the parent form to True." |
Microsoft Press | May 06, 2010 | |
Printed | Page 567 |
"Minimum" used in place of "Maximum" On page 567, the third sentence of the first paragraph reads: "Likewise, when the Value property is the same value as the Minimum property, the ProgressBar control appears completely filled." It should read: "Likewise, when the Value property is the same value as the Maximum property, the ProgressBar control appears completely filled." |
Microsoft Press | May 06, 2010 | |
Printed | Page 581 |
"DefaultSettings" should be "Default" On page 581, the C# code sample near the top of the page contains an incorrect object. Change: // C# Properties.Settings.DefaultSettings.TitleSetting = "This is the new Title"; Properties.Settings.DefaultSettings.Save();To: // C# Properties.Settings.Default.TitleSetting = “This is the new Title”; Properties.Settings.Default.TitleSetting.Save(); |
Microsoft Press | May 06, 2010 | |
Printed | Page 631-632 |
ToolBoxBitmap should be ToolboxBitmap On pages 631 and 632, each of the code samples references ToolBoxBitmap rather than ToolboxBitmap. Change: ' VB Class myControlTo: ' VB Class myControlChange: // C# [ToolBoxBitmap(@"C:myToolboxBitmap.bmp")]To: // C# [ToolboxBitmap(@"C:myToolboxBitmap.bmp")] |
Microsoft Press | May 06, 2010 | |
Printed | Page 655 |
Call to Refresh missing from C# code On page 655, the C# code at the top of the page is missing a line. Change: // C# protected override void OnClick(EventArgs e) { mClicks++; base.OnClick(e); }To: // C# protected override void OnClick(EventArgs e) { mClicks++; base.OnClick(e); this.Refresh(); } |
Microsoft Press | May 06, 2010 | |
Printed | Page 691 |
"TabContainer" should be "TabControl" On page 691, the first sentence under Case Scenario 2 contains an invalid control. Change: "The TabContainer control can be used to display multiple pages of information and allow the user to switch between pages while keeping the information static." To: "The TabControl control can be used to display multiple pages of information and allow the user to switch between pages while keeping the information static." |
Microsoft Press | May 06, 2010 | |
Printed | Page 723 |
InnerXml should be ReadInnerXml and OuterXml should be ReadOuterXml Page 723, answers C & D to Question 2 contain incorrect methods. Change: "C. Correct. The MoveToAttribute method allows you to specify either an attribute name or index. The attribute value is exposed via the InnerXml property. D. Incorrect. When positioned on an attribute, the OuterXml property returns the name of the attribute as well as the value." To: "C. Correct. The MoveToAttribute method allows you to specify either an attribute name or index. The attribute value is exposed via the ReadInnerXml property. D. Incorrect. When positioned on an attribute, the ReadOuterXml property returns the name of the attribute as well as the value." |
Microsoft Press | May 06, 2010 | |
Printed | Page 742 |
Definition for "delegate" incorrect On page 742, the definition for "delegate" reads: "A type-date function pointer that can be used to call a method synchronously or asynchronously." It should read: "A type-safe function pointer that can be used to call a method synchronously or asynchronously." 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 |