Article ID: 971804 - Last Review: May 27, 2009 - Revision: 1.6

MCTS Self-Paced Training Kit (Exam 70-562): Microsoft® .NET Framework 3.5—ASP.NET Application Development comments and corrections

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

On This Page

Expand all | Collapse all

SUMMARY

This article contains comments, corrections, and information about known errors relating to the Microsoft Press book MCTS Self-Paced Training Kit (Exam 70-562): Microsoft .NET Framework 3.5 ASP.NET Application Development, 978-0-7356-2562-4.

The following topics are covered:

  • Page 48: Description of PreLoad event incorrect
  • Pages 69 & 70: Multiple typos in code example
  • Page 92: "href" should be "src"
  • Page 145: Text should be ErrorMessage
  • Page 147: "EnableClientSideScript" should be "EnableClientScript"
  • Page 152: "ClientFunctionName" should be "ClientValidationFunction"
  • Page 169: "ProcessingPage.aspx" should be "DataCollection.aspx"
  • Page 189: Incorrect information regarding encrypting information
  • Page 196: "Value" needs to be removed from C# code example
  • Page 199: "&lt." should be "<"
  • Page 236: ".Master" should be ".master"
  • Page 255: "Pink" should be "Theme"
  • Page 273: Code example partially incorrect
  • Page 273: Code example partially incorrect
  • Page 302: EnablePartialRending should be EnablePartialRendering
  • Page 306: UpdateProgress should be UpdatePanel
  • Page 317: "include" should be "src"
  • Page 538: Configre should be Configure
  • Page 619: "a" should be "are a"
  • Page 661: after should be before
Back to the top

MORE INFORMATION

Page 48: Description of PreLoad event incorrect

On page 48, the description of the PreLoad event is incorrect and needs to be changed.

Change:
"This event fires before view state has been loaded for the page and its controls and before PostBack processing. This event is useful when you need to write code after the page is initialized but before the view state has been wired back up to the controls."

To:
"Use this event if you need to perform processing on your page or control before the Load event. Before the Page instance raises this event, it loads view state for itself and all controls, and then processes any postback data included with the Request instance."

Back to the top

Pages 69 & 70: Multiple typos in code example

On pages 69 & 70, the C# code example that starts on page 69 and ends on page 70 includes several incorrect characters.
Change: 
//C#
protected void Page_PreInit(object sender, EventArgs e)
{
System.Diagnostics.Debug.WriteLine("Page_PreInit");
}

protected void Page_Init(object sender, EventArgs”e)”
{
System.Diagnostics.De”ug.WriteLine("Page_Init");
}

prote”ted “oid Page_PreRender(object sender, EventArgs e)
{
Sy”tem.Diagnostics.Debug.WriteLin”("Page”PreRender");
}

protected void Page_Unload(object sender, EventArgs e)
{
System.Dia”nostic”.Debug.WriteLine("Page_Unload");
}

To: 
//C#
protected void Page_PreInit(object sender, EventArgs e)
{
System.Diagnostics.Debug.WriteLine("Page_PreInit");
}

protected void Page_Init(object sender, EventArgs e)”
{
System.Diagnostics.Debug.WriteLine("Page_Init");
}

protected void Page_PreRender(object sender, EventArgs e)
{
System.Diagnostics.Debug.WriteLine("Page_PreRender");
}

protected void Page_Unload(object sender, EventArgs e)
{
System.Diagnostics.Debug.WriteLine("Page_Unload");
}

Back to the top

Page 92: "href" should be "src"

On page 92, the second sentence of the first paragraph contains an incorrect attribute name.

Change:
"This property maps directly to the href attribute of the <img> element in HTML."

To:
"This property maps directly to the src attribute of the <img> element in HTML."

Back to the top

Page 145: Text should be ErrorMessage

On page 145, the second sentence of the second paragraph of the "Client-Side Validation" section is incorrect.

Change:
"If validation fails, the validation control’s Text property is displayed to the user."

To:
"If validation fails, the validation control’s ErrorMessage property is displayed to the user."

Back to the top

Page 147: "EnableClientSideScript" should be "EnableClientScript"

On page 147, the third property down in Table 3-1 is incorrect.

Change:
"EnableClientSideScript"

To:
"EnableClientScript"

Back to the top

Page 152: "ClientFunctionName" should be "ClientValidationFunction"

On page 152, the sixth paragraph down from the top contains an incorrect property name.

Change:
"Finally, you attach your client-side function to a CustomValidator by setting the ClientFunctionName property of the CustomValidator control to the name of your validation function."

To:
"Finally, you attach your client-side function to a CustomValidator by setting the ClientValidationFunction property of the CustomValidator control to the name of your validation function."

Back to the top

Page 169: "ProcessingPage.aspx" should be "DataCollection.aspx"

On page 169, the directive located at the top of the page under the first paragraph contains an incorrect page name.

Change: 
<%@ PreviousPageType VirtualPath="~/ProcessingPage.aspx" %>

To: 
<%@ PreviousPageType VirtualPath="~/DataCollection.aspx" %>

Back to the top

Page 189: Incorrect information regarding encrypting information

On page 189, the first sentence of the second paragraph contains incorrect information about encrypting information stored in the view state.

Change:
"If you do have very sensitive information that is stored in the view state between page requests, you can encrypt it using the ViewStateEncryptionMode property of the Page object."

To:
"If you do have very sensitive information that is stored in the view state between page requests, you can encrypt it using the ViewStateEncryptionMode attribute of the Page directive."

Back to the top

Page 196: "Value" needs to be removed from C# code example

On page 196, the last C# code snippet on the page includes an incorrect word in the first three lines.

Change: 
//C#
Response.Cookies["info"]["visit"].Value = DateTime.Now.ToString();
Response.Cookies["info"]["firstName"].Value = "Tony";
Response.Cookies["info"]["border"].Value = "blue";
Response.Cookies["info"].Expires = DateTime.Now.AddDays(1);

To: 
//C#
Response.Cookies["Info"]["visit"] = DateTime.Now.ToString();
Response.Cookies["Info"]["firstName"] = "Tony";
Response.Cookies["Info"]["border"] = "blue";
Response.Cookies["info"].Expires = DateTime.Now.AddDays(1);

Back to the top

Page 199: "&lt." should be "&lt;"

On page 199, the third sentence in the Security Alert box at the bottom of the page includes an incorrect character.

Change:
"For example, Server.HtmlEncode replaces a “<” sign with “&lt.”."

To:
"For example, Server.HtmlEncode replaces a “<” sign with “&lt;”."

Back to the top

Page 236: ".Master" should be ".master"

On page 236, the two code examples on the page include incorrect extensions.

Change: 
<%@ Page Language="VB" MasterPageFile="MySite.Master" %>

To: 
<%@ page Language="VB" MasterPageFile="MySite.master" %>

Change: 
<pages masterPageFile="MySite.Master" />

To: 
<pages masterPageFile="~/MySite.master" />

Back to the top

Page 255: "Pink" should be "Theme"

On page 255, the 7th line down in the VB code example uses an incorrect word.

Change: 
Page.Pink = "PinkTheme"

To: 
Page.Theme = "PinkTheme"

Back to the top

Page 273: Code example partially incorrect

On page 273, the 4th line in the code example at the top of the page is missing content.

Change: 
string GetTextBoxValue()

To: 
public string GetTextBoxValue()

Back to the top

Page 273: Code example partially incorrect

On page 273, the fourth line down in the second C# code example on the page is missing content.

Change: 
void ShowTextBoxValue(string textBoxValue)

To: 
public void ShowTextBoxValue(string textBoxValue)

Back to the top

Page 302: EnablePartialRending should be EnablePartialRendering

On page 302, the first sentence of the third paragraph refers to "EnablePartialRending" rather than "EnablePartialRendering."

Change:
"By default, the ScriptManager control’s EnablePartialRending property is set to True."

To:
"By default, the ScriptManager control’s EnablePartialRendering property is set to True."

Back to the top

Page 306: UpdateProgress should be UpdatePanel

On page 306, the first sentence is incorrect.

Change:
"The UpdateProgress control can also be associated directly with an UpdateProgress control through the AssociatedUpdatePanelId property."

To:
"The UpdateProgress control can also be associated directly with an UpdatePanel control through the AssociatedUpdatePanelId property."

Back to the top

Page 317: "include" should be "src"

On page 317, the first sentence in the second paragraph on the page includes an incorrect attribute name.

Change:
"You can add client script to your page through a script block that includes code or through an include attribute that references a JavaScript (.js) file."

To:
"You can add client script to your page through a script block that includes code or through an src attribute that references a JavaScript (.js) file."

Back to the top

Page 538: Configre should be Configure

On page 538, the second sentence includes a typo.

Change:
"You can then use the Configre Data Source Wizard to connect to your data and generate markup for the data source."

To:
"You can then use the Configure Data Source Wizard to connect to your data and generate markup for the data source."

Back to the top

Page 619: "a" should be "are a"

On page 619, the first sentence of the "ASP.NET Security" section contains a typo.

Change:
"There a number of ways you can use the authentication and authorization methods of ASP.NET to secure your XML Web services."

To:
"There are a number of ways you can use the authentication and authorization methods of ASP.NET to secure your XML Web services."

Back to the top

Page 661: after should be before

On page 661, the third sentence of the "Defi ning User Control Events" section is incorrect.

Change:
"For example, after the page Init event is called, the control’s Init event is called in turn. Processing then returns to the page for the Load event; following this the control’s Load event is called."

To:
"For example, before the page Init event is called, the control’s Init event is called in turn. Processing then returns to the page for the Load event; following this the control’s Load event is called."

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.
Back to the top
APPLIES TO
  • MCTS Self-Paced Training Kit (Exam 70-562): Microsoft .NET Framework 3.5—ASP.NET Application Development, ISBN 978-0-7356-2562-4
Back to the top
Keywords: 
KB971804
Back to the top