Errata

The Label Control should be named LabelBrand not Brand in other to justify both codes written below on this page. Or you should replace the LabelBrand with Brand in the sample codes. Thank you

Note from the Author or Editor:
On page 51, please change "updating a Label control named Brand in the master page" to "updating a Label control named LabelBrand in the master page".

p309 C6L1 MCTS 70-515 "method" instead of "event"

Point 13...

CHANGE "Call the base InitializeCulture event"
TO "Call the base InitializeCulture method"

Note from the Author or Editor:
CHANGE "Call the base InitializeCulture event"
TO "Call the base InitializeCulture method"

In step 4 of the Exercise 2, the second sentence says 'Click the Color Scheme list and then click Professional.

Then in the last line it says ' The newly loaded page has a yellow header because the page is now using the Colorful.master master page.

The second sentence should change to 'click Colorful....'

Note from the Author or Editor:
Valid. Please make the change as described, changing "Professional" in step 4 to "Colorful".

The printed version shows correct wording answer for Question 4 - is (D) WebAuthenticationFailureAuditEvent.
But the Lesson Review Answer on Page 903 shows incorrect explanation for (D) selection.

Also the Lesson Review Test on the CD shows the wrong answer - WebAuthenticationSuccessAuditEvent

You want to configure ASP.NET health monitoring to log information every time a user fails to log on to the server.

Which web event class should you use?
WebAuthenticationSuccessAuditEvent
WebApplicationLifetimeEvent
WebRequestEvent
WebAuditEvent

The explanation given for the Lesson Review Test is incorrect:
This class sends an event when a user successfully authenticates with the website.
The question is checking when user fails to log on.
Correct Explanation:
The WebAuthenticationFailureAuditEvent is used to provide information when a failed attempt at user authentication occurs on the site.

Note from the Author or Editor:
Valid. On page 418, please change answer 4D to WebAuthenticationFailureAuditEvent. On page 903, please change explanation 4D to "This class sends an event when a user attempts to authenticate to the website but provides invalid credentials."

The PTQ on the CD will also need to be corrected similarly.

One can't do what is said in following: "By defining an absolute expiration in addition to a sliding expiration, you
can be sure an object is eventually removed.".

Note from the Author or Editor:
Valid--please remove that sentence.

You can't apply a theme at a control level.

Note from the Author or Editor:
Please change the third bullet on page 73 to "You can apply a theme at the page level or at the site level using the Web.config file."

"Quick check" section:

Question: What launch condition does a Web Setup Project include by default?

Answer: By default, a Web Setup Project checks for an IIS version later than 4.0.

When i create web setup project, it contains lunch condition "IIS condition" ((IISMAJORVERSION >= "#5" AND IISMINORVERSION >= "#1") OR IISMAJORVERSION >= "#6") by default. I think, correct is iis version 5.1 and above

Note from the Author or Editor:
Please change quick check answer #1 on page 443 to "1. By default, a Web Setup Project verifies the IIS version."

For the PreLoad event, the book states: "This event fires before view state has been loaded for the page and its controls", however MSDN states that this event is "raised after the page loads view state for itself and all controls." See: http://msdn.microsoft.com/en-us/library/ms178472.aspx

Note from the Author or Editor:
Valid. Please change the description for the InitComplete row to read, "Raised once all initializations of the page and its controls have been completed. 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."

Please change the description for the PreLoad row to read, "This event fires after view state has been loaded and the page has processed postback data."

Chapter 5, Lesson 2 (Working with Site Navigation) exercise step 1?


Open Visual Studio and create new ASP.NET Empty Web Site project

? should be changed to read ?

Open Visual Studio and create new ASP.NET Web Application


? because steps in the exercise expect certain dependencies that are not available when using the ASP.NET Empty Web Site method. For example, step 4 suggests to open the Site.master file, but this file does not exist if using a ASP.NET Empty Web Site project. It does exist if using a ASP.NET Web Application.

Note from the Author or Editor:
Valid. Please change as described.

The bullet reads as below:

■ Practice 1 Create a custom control and implement control state management.

The request seems simply enough, but given the progression of the chapters, this objective is not achievable with the content covered by the end of Chapter 3. The preceding chapter does not even discuss how to implement State Management or how to create and custom control.

Readers familiar with either of these tasks would not have an issue, but less experienced .NET developers would find this out of place.They may find themselves thinking they missed something when in reality it was not covered by this point in the book. It seems more on Control State in the chapter is needed, with some examples including custom control creation, or a move of this practice objective to Chapter 8 where it would be covered.

Note from the Author or Editor:
Valid. Please change the first Practice 1 on page 158 to just read, "Create a custom control."

ASP web forms separate the HTML layout from the .NET Framework code.

Should be:
ASP.NET web forms separate the HTML layout from the .NET Framework code.

Note from the Author or Editor:
Valid, please change as described.

pg. 82

Further comment on:

Duration - "This is a required parameter."


- Parameter is not required if using CacheProfile (as in example on p88)

Note from the Author or Editor:
Valid. Please change, "This is the only required parameter." to "This parameter is required if you are not using CacheProfile."

when describing the location of global themes, the example that you give for .NET 4_0_30319 omits the themes folder from the end of the path:

Example:
C:\inetpub\wwwroot\aspnet_client\system_web\4_0_30319\

Correct example:
C:\inetpub\wwwroot\aspnet_client\system_web\4_0_30319\themes

Note from the Author or Editor:
Valid. Please change as described in the body text of the first bullet point.

You are modifying the page cache to expire based on a control, however the in the code example directly beloq you are using VaryByParam not VaryByControl as expected.

Note from the Author or Editor:
On page 90, step 10, please change "VaryByParam" to "VaryByControl"

"this.onKeyupHandler" should be passed to $addHandlers call instead of "this.onKeyup", like this:

$addHandlers(this.get_element(), { 'keyup': this._onKeyupHandler }, this);

Note from the Author or Editor:
change the $addHandlers line near the bottom of the page to read:

$addHandlers(this.get_element(), { 'keyup': this._onKeyupHandler }, this);

"path" should be replaced with "name" for VS to give intellisense for for MS AJAX Library.

Note from the Author or Editor:
bottom of page 495, the single line of markup should read,

/// <reference name="MicrosoftAjax.js"/>

The second option that says:

"Define an XSL file to transform the XML, and set the Transform attribute to the name of the XSL file"

should read:

"Define an XSL file to transform the XML, and set the TransformFile attribute to the name of the XSL file"

Note from the Author or Editor:
Valid, please change as described.

The sample C# code for the Page_Init method is missing it's parameters. Should read:

protected void Page_Init(object sender, EventArgs e) {
...
}

VB sample code is fine.

Note from the Author or Editor:
change the first link of the C# sample code at the bottom of the page to read,

protected void Page_Init(object sender, EventArgs e)

in the HttpPost part of de controllers code

[HttpPost]
public ActionResult Edit(Employee emp)
{

try
{
NorthwindEntities2 nw = new NorthwindEntities2();
Employee origEmp = GetEmployee(emp.EmployeeID);
nw.Employees.Attach(emp);
nw.ApplyOriginalValues("Employees", origEmp);
nw.SaveChanges();

return RedirectToAction("Index");
}
catch
{
return View();
}


should look like the code below, there is no validation control in the employee controller now, this state control is also missing for ActionResult Create,and in the VB code on page872

[HttpPost]
public ActionResult Edit(Employee emp)
{

if (ModelState.IsValid == true)
{
try
{

NorthwindEntities2 nw = new NorthwindEntities2();
Employee origEmp = GetEmployee(emp.EmployeeID);
nw.Employees.Attach(emp);
nw.ApplyOriginalValues("Employees", origEmp);
nw.SaveChanges();

return RedirectToAction("Index");
}
catch
{
return View("Edit",emp);
}
}
else
{
return View("Edit", emp);
}

Note from the Author or Editor:
p. 873, the HttpPost version of the Create function should read

[HttpPost]
public ActionResult Create(Employee emp)
{
if (ModelState.IsValid)
{
try
{
northwndEntities nw = new northwndEntities();
nw.AddToEmployees(emp);
nw.SaveChanges();
return RedirectToAction("Index");
}
catch
{
return View();
}
}
else
{
return View("Create");
}
}

p. 874, the HttpPost version of the Edit function should read:

[HttpPost]
public ActionResult Edit(Employee emp)
{
if (ModelState.IsValid)
{
try
{
northwndEntities nw = new northwndEntities();
Employee origEmp = GetEmployee(emp.EmployeeID);
nw.Employees.Attach(emp);
nw.ApplyOriginalValues("Employees", origEmp);
nw.SaveChanges();
return RedirectToAction("Index");
}
catch
{
return View();
}
}
else
{
return View("Edit", emp.EmployeeID);
}
}

Printed: in the step 2 says "add PreInit event to the page" and the samples codes are coded into the Page_Load (which is correct)

PDF: as in the printed edition in the step two says add "PreInit" but here both sample codes are coded in PreInit which is incorrect

Note from the Author or Editor:
This problem only occurs when using master pages. However, since Page_Load is more universal, we should use that event handler instead, as the reader suggests.

Please change every instance of the phrase "PreInit" to "Load" on pages 188 and 189, including those in the code sample.

use response.redirect("Home.aspx", false); instead
or alternative the Server.Execute method instead.

See the following KB article 312629 :
http://support.microsoft.com/default.aspx?scid=kb;en-us;312629

and also the following P&P guideline:
"Write Code That Avoids Exceptions"
http://msdn.microsoft.com/en-us/library/ff647787.aspx#scalenetchapt06_topic22

Note from the Author or Editor:
In the Visual Basic code, change:

Reponse.Redirect("Home.aspx")

to:

Reponse.Redirect("Home.aspx", False)

In the C# code, change:

Reponse.Redirect("Home.aspx");

to:

Reponse.Redirect("Home.aspx", false);

The question for number 1 is how to register a class to be used as an extension to a DOM element, not how to create an AJAX UI control. According to page 502, 2nd to last paragraph states this to be Sys.UI.Behavior as opposed to Sys.UI.Control. The answer should be D, not A.

Note from the Author or Editor:
On page 906, the answers to Lesson 2, Question 1 should change as follows:

1. Correct Answer: D

A. Incorrect: You derive from the Sys.UI.Control class to create an AJAX UI Control (not a DOM extension).

B. Incorrect: This call simply indicates that you intend to implement the IDisposable interface. It does not indicate proper inheritance for extending a DOM element.

C. Incorrect: This call creates your class without inheritance. To extend a DOM element, you should inherit from Sys.UI.Behavior.

D. Correct: This call creates a control that extends a DOM element.

text talks about changing the theme of a control by setting the skinid, a theme does not directly apply to a control, you can change the skin by changing the skinid but assigning it the name of a theme wont work.

http://msdn.microsoft.com/en-us/library/tx35bd89%28v=VS.85%29.aspx

Note from the Author or Editor:
Valid point. On page 68, please change "...you can apply a theme to specific controls" to "...you can apply a skin to specific controls". In the code sample on the bottom of the page, change the two occurrences of "BlueTheme" to "BlueSkin"

Part of the paragraph says:

"For example if a user types an address into a TextBox and view state is enabled, the address will remain in the TextBox between requests".

This is not wrong, but it's misleading as the address will remain in the TextBox between requests even if view state is not enabled. Post data is not stored in Viewstate.

Note from the Author or Editor:
Valid point. Please change the specified sentence to:

"For example, if view state is enabled and you set the value of a Label control, ASP.NET will retain the custom value between requests."

The Shared Attribute is listed under @ OutputCache for single page. The Shared attribute can only be used in a user control.

http://msdn.microsoft.com/en-us/library/hdxfb6cy.aspx

Note from the Author or Editor:
Valid errata. Please remove the "Shared" row from the table.

Replace "NoAction" with "NonAction"

Note from the Author or Editor:
The last sentence on page 853 should read, "To do so, you mark it with the NonAction attribute to indicate that it is not an action method."

Replace "DataTime" with "DateTime"

Note from the Author or Editor:
On page 772, the section titled "Customizing an existing field template". The first sentence in the second paragraph has the referece to "DataTime_Edit.ascx". This should be "DateTime_Edit.ascx".

Replace "code edit pages" with "code edit controls"

Note from the Author or Editor:
In the section title, "Customizing an existing field template", the first sentence includes the text "core edit pages". This should read "core edit controls".

Replace "DetailView" with "DetailsView"

Note from the Author or Editor:
On page 751, in Step 17 change "DetailView" to read "DetailsView"

Replace "FormsViews" with "FormView"

Note from the Author or Editor:
Section "Introducing Data-Bound Controls, first paragraph, second sentence: change FormsView to FormView.

Replace "$.jquery()" with "$.ajax()"

Note from the Author or Editor:
Near the bottom, second to last paragraph reads, "The $.jquery() call ... ". Replace with, "The $.ajax() call ...".

It reads "By default, Page.EnableViewState is Enabled...". However, Page.EnableViewState can only be set to true or false. Should be "By default, Page.ViewStateMode is Enabled...".

Note from the Author or Editor:
Please change "By default, Page.EnableViewState is Enabled...". to "By default, Page.EnableViewState is True...".

In the HttpPost part of de controllers code

[HttpPost]
public ActionResult Edit(Employee emp)
{

try
{
NorthwindEntities2 nw = new NorthwindEntities2();
Employee origEmp = GetEmployee(emp.EmployeeID);
nw.Employees.Attach(emp);
nw.ApplyOriginalValues("Employees", origEmp);
nw.SaveChanges();

return RedirectToAction("Index");
}
catch
{
return View();
}


should look like the code below, there is no validation controle in the employeecontroller now, this state control is also missing for ActionResult Create,and in the VB code on page872

[HttpPost]
public ActionResult Edit(Employee emp)
{

if (ModelState.IsValid == true)
{
try
{

NorthwindEntities2 nw = new NorthwindEntities2();
Employee origEmp = GetEmployee(emp.EmployeeID);
nw.Employees.Attach(emp);
nw.ApplyOriginalValues("Employees", origEmp);
nw.SaveChanges();

return RedirectToAction("Index");
}
catch
{
return View("Edit",emp);
}
}
else
{
return View("Edit", emp);
}

Note from the Author or Editor:
p 872, VB sample code for the HttpPost version of the Create function should read as:

<HttpPost()> _
Function Create(ByVal emp As Employee) As ActionResult
If ModelState.IsValid Then
Try
Dim nw As New northwndEntities()
nw.AddToEmployees(emp)
nw.SaveChanges()
Return RedirectToAction("Index")
Catch
Return View()
End Try
Else
Return View("Create")
End If
End Function

p. 872, the HttpPost version of the Edit function should read:
<HttpPost()> _
Function Edit(ByVal emp As Employee) As ActionResult
If ModelState.IsValid Then
Try
Dim nw As New northwndEntities()
Dim origEmp As Employee = GetEmployee(emp.EmployeeID)
nw.Employees.Attach(emp)
nw.ApplyOriginalValues("Employees", origEmp)
nw.SaveChanges()
Return RedirectToAction("Index")
Catch
Return View()
End Try
Else
Return View("Edit", emp.EmployeeID)
End If
End Function

Add using (Imports in Visual Basic) statements to the class file for System.Data,
System.Data.SqlClient,
and System.Configuration.



Should also add
System.Text
as the following code uses a StringBuilder class

Note from the Author or Editor:
Change the end of step 8 to read, "...System.Data.SqlClient, System.Configuration, and System.Text".

The paragraph is misleading. It seems to imply that REST services only use the HTTP GET method. In fact they can use POST, PUT, and DELETE as well. Also the example on p. 605 uses POST because of the [WebInvoke] attribute.

I would suggest rewording the paragraph on p. 603 so that it doesn't imply REST is for GET requests only.

Note from the Author or Editor:
The paragraph before the NOTE should read as follows:

A REST service is a web service you create that responds to basic HTTP requests such as GET, POST, PUT, and DELETE. Clients can therefore call a REST service the same way they would call a web page. This includes a simple GET using a URL and a query string and a POST request. The server then responds with text, as it would for any HTTP request. This way, a REST service does not require knowledge of the XML schema used to call the service. Instead, it simply sends the request and processes the text-based response (usually JSON formatted data).

Regarding the OnClick / OnClientClick events, text reads "Note that returning false from onClick negates the postback".

I believe this should be "Note that returning false from onClientClick negates the postback"

Note from the Author or Editor:
p. 475, end of the paragraph at the top of the page, change the text in the parenthetical that says "onClick" to "onClientClick".

"public Address Address {get; set;}" does not create a new Instance of Address; not equivalent with VB code (first lines of page 343) => C# example won't work (null object reference)

Note from the Author or Editor:
change code at the button of p. 343 that reads, "public Address Address { get; set; } to:

private Address _address = new Address();

public Address Address
{
get { return _address }
set { _address = value; }
}

Suggested textual correction is wrong. Change only this:
<%@ PreviousPageType VirtualPath="~/DataCollection.aspx" %>

Note from the Author or Editor:
Please change <%@ PreviousPageType VirtualPath="~/ProcessingPage.aspx" %> to <%@ PreviousPageType VirtualPath="~/DataCollection.aspx" %>

If you remove the runat="server" attribute the generated value of id can change (example: use a master page). Not removing the ID attribute is not enough; you have to change it.

Note from the Author or Editor:
Replace the sentence, "If the HTML element is referenced by client-side script, you should not remove its ID attribute." with "If the HTML element is referenced by client-side script, verify that ASP.NET has not changed its ID attribute in the rendered HTML."

In question 515P_5.5_06 one of the answers is:
Remove the default DynamicDataRoute from the Global.aspx file.

This should be:
Remove the default DynamicDataRoute from the Global.asax file.

Because a dynamic data project contains a global.asax by default and doesn't contain a global.aspx.

I believe the following is missing from within <system.web>:
<identity impersonate="true"/>

If the above is not required, then some text explaining why it is not required would be helpful.

Note from the Author or Editor:
Right. Please add: <identity impersonate="true"/>

below <system.web> in the final code sample on page 921. Indent it to the same level as the <authentication mode="Windows" />

The text reads "Press Ctrl+[ to return to the Telnet prompt."
The actual command is Ctrl+]

Note from the Author or Editor:
Please change [ to ] as described

public string PostalCode
{
get { return TextBoxPostal.Text; }
set { TextBoxPostal.Text = value; }
}

TextBoxPostal should be TextBoxPostalCode (= ID of the control)

Note from the Author or Editor:
On page 350, in the C# sample code at the top, the last property should read:

public string PostalCode
{
get { return TextBoxPostalCode.Text; }
set { TextBoxPostalCode.Text = value; }
}

Question 1, Answer B (the correct one) states that you should return Redirect("Shipment/Status"). This works, but it requires the controller to have knowledge about how the route segments are arranged, and it would stop working if I configured the route differently, for instance: {action}/{controller}.
It would be advisable to call the specific redirection method:
RedirectToAction("Status", "Shipment")


Question 2, I believe this is a typo: "This default route should point to Default.aspx inside the view folder named Main. You create a controller named DefaultController."

According to the naming convention, a view for a controller named DefaultController should be placed inside in a subfolder named "Default", not "Main".

Note from the Author or Editor:
This is correct. However, the nature of the question is testing if the reader understands the default routing conventions. That said, we will make the following changes to the question:

Page 876, Question 1. The question should end with the text, (Choose all that apply.)

Page 922, Answer B should read:
B. Correct: This naming convention would be the most logical for the controller and action method. A better choice (not shown as an answer) would be to use the RedirectToAction method which does not rely on routing conventions that can change. For example, RedirectToAction("Status", "Shipment").

Page 922, Answer C should read:
C. Correct: This naming convention would be the most logical for the view folder and view. A better choice (not shown as an answer) would be to use the RedirectToAction method which does not rely on routing conventions that can change. For example, RedirectToAction("Status", "Shipment").

--------------------------
Regarding your point about question 2: By default, this page would be in the Views\Home folder and would be Index.aspx. However, the question does not talk about the defaults.

There is another issue, however. Page 876, question 2, should include the text, (Choose all that apply.) at the end of the question.

There is no XmlDataSource in the example, and there is no XPath expression either, even though both are mentioned in the text.

I'm guessing the XML file with menu items has been changed to simplify the example, but the text has stayed the same.

Note from the Author or Editor:
Last paragraph on page 746 the first sentence should be deleted. The paragraph should start with, "The following code ... ".

The question is a bit ambiguous and the marked correct answer is B, even though this is technically not correct.

I see two possible solutions, one would be to use answers C and D, to produce something like this:
<asp:EntityDataSource ID="NorthwindEntityDataSource" runat="server"
ConnectionString="name=NorthwindEntities"
DefaultContainerName="NorthwindEntities" EnableFlattening="False"
EntitySetName="Customers"
Where="it.CustomerID=@CustomerID">
<WhereParameters>
<asp:QueryStringParameter QueryStringField="custId" Name="CustomerID" DbType="String"/>
</WhereParameters>
</asp:EntityDataSource>

If the question is to specify a query that uses a custom Entity SQL expression, then a CommandText must be used, but B is still not the complete answer. Alongside with B the user would also have to define CommandParameters and specify the parameter, something like this:

<asp:EntityDataSource ID="NorthwindEntityDataSource" runat="server"
CommandText="SELECT c.CustomerID, c.CompanyName, c.Phone FROM Customers AS c WHERE c.CustomerID=@CustomerID"
ConnectionString="name=NorthwindEntities"
DefaultContainerName="NorthwindEntities">
<CommandParameters>
<asp:QueryStringParameter QueryStringField="CustomerID" Name="CustomerID" DbType="String"/>
</CommandParameters>
</asp:EntityDataSource>

Or am I wrong in assuming that an EntityDataSource with CommandText using parameters, and no parameters supplied with <CommandParameters> will not work?

Note from the Author or Editor:
You are correct that the question assumes you are using <CommandParameters>. However, we will make changes to make the question more clear.

First, p. 720, question 4, change answer D to read:
D. Add a CommandParameters section to the EntityDataSource control markup.

p. 915, change question 4 to Correct Answer B and D.
Change D to read:
D. Correct: You use a CommandParameters section to define a parameter to used inside the CommandText query. You reference the parameter in the query using the construct, @ParamName.

Question 3:
What types of data can you store in the Cache collection?

Answer:
You can store any type of data in the Cache collection. However, when you retrieve the data, you must cast it to the correct type.

Answer is incomplete. Correct answer should be: You can store any type of data that is serializable in the Cache collection.

Note from the Author or Editor:
Valid point. Please change: "You can store any type of data in the Cache collection." to "You can store any serializable type of data in the Cache collection."

"2. The LoginName, ChangePassword, and LoginView controls are useful only to authenticated users."

I agree on the first two, but the LoginView is also useful to Anonymous users. In fact, it has an AnonymousTemplate whose contents are only visibile to unathenticated users. I would use that template to show them an asp:Login control.

Note from the Author or Editor:
Valid point. Please change the answer for #2 to:

"2. The LoginName and ChangePassword controls are useful only to authenticated users. LoginView is also useful to unauthenticated users when you set the LoginView.AnonymousTemplate property."

In Chapter 1, Lesson 2, on page no 16, It is mentioned that 'You cannot mix Visual Basic and CS' in a web application.

Where as the answer of Question 2 in page 32, is privided as 'A' that is one can add .VB files in a CSharp project.

Is this correct?

Note from the Author or Editor:
This isn't a mistake, but we could clarify the answer explanation. Change the first sentence of answer A to: "Unlike ASP.NET Web applications, ASP.NET websites can contain pages that use different languages."

This is from the author:

Page 107:

Dim FeedbackLabel As Label = DirectCast(FindControl("FeedbackLabel"), Label);
Dim InputTextBox As TextBox = DirectCast(FindControl("InputTextBox"), TextBox);

has to be replaced by:

Dim FeedbackLabel As Label = DirectCast(Panel1.FindControl("FeedbackLabel"), Label);
Dim InputTextBox As TextBox = DirectCast(Panel1.FindControl("InputTextBox"), TextBox);

Page 108:

Label FeedbackLabel = (Label)FindControl("FeedbackLabel");
TextBox InputTextBox = (TextBox)FindControl("InputTextBox");

has to be replaced by:

Label FeedbackLabel = (Label)panel1.Findcontrol("FeedbackLabel");
TextBox InputTextBox = (TextBox)Panel1.FindControl("InputTextBox");

Note from the Author or Editor:
Yes, please make these changes.

Simply change "Return _postalCode;" to "return _postalCode;"

Exercise is to use the Fabrikam Theme, which states in item 8, to set the font-family to Script.

Figure 2-6 shows the text as non Script.

Note from the Author or Editor:
Browser used to capture screenshot didn't render the script font. You can download an updated screenshot here:

http://www.northrup.org/dl/tk70-515/f02xx06-new.bmp

There is no ASP.NET NavigationMenu control, only a Menu control (which happens to have an ID of NavigationMenu in the default Site.master page). Consider rewording as "4. Open the Site.master page. Remove the default Menu control." (to remove any confusion as to the correct class).

Note from the Author or Editor:
Please change as described

NavigationMenu is listed as one of the common ASP.NET navigation controls - this should just be Menu (not NavigationMenu).

Note from the Author or Editor:
Correct; please change "NavigationMenu" to "Menu"

book states: add standard web forms to your site but select the select master page check box when creating the page.

VS2010 has the option of selecting Web Form Using Master Page which should be used instead of a standard page. The checkbox option is no longer available in VS2010 Ultimate.

note to Author: if you are going to rip from prior versions of the book, the least you can do is proof read and update changes where necassary between versions.

Note from the Author or Editor:
Yes, the UI varies for Web Sites and Web Applications (grr). Please update that bullet point to read, "To add a content page to a Web Site project, add a Web Form and select the Select Master Page check box. To add a content page to a Web Application project, add a Web Form Using Master Page class. You then add content to the page inside the content area defined by the master page."

Additionally, on page 47, please change the first paragraph to read:

"To add a content page to a Web Site project, select the Select Master Page check box in the Add New Item dialog box. To add a content page to a Web Application project, select Web Form Using Master Page from the Add New Item dialog box. Both methods allow you to select a master page for your ASPX page. Alternatively, you can associate an ASPX page to a master page by using the MasterPageFile attribute in the @ Page directive."

Question: 1. Which event would you handle to set the value of a Label control?

Answer: 1. Usually, you would handle the Page.Load event. Because other parts of a form probably do not rely on the value of a Label, you could also handle the Page.PreInit, Page.Init, or Page.Render event.

Corrections:
1) Page.Render is not an event, it is a method. Perhaps the intention was Page.PreRender? I doubt you would override Page.Render in order to change a Label.Text property.

2) Page.PreInit will not work because the control object is not created yet and you will get a System.NullReferenceException at runtime.

3) I believe the best event is actually the Page.PreLoad event because changing the value of a property of a label control in a Page.Load handler will cause its viewstate to become dirty and unnecessarily bloat the size of the viewstate string in the response and subsequent postbacks. Maybe this is beyond the scope of the book but in that case the question probably uses a bad example.

Note from the Author or Editor:
Very valid points. Answer 1 should read:

"Typically, you would handle the Page.Load event. Because other parts of a form probably do not rely on the value of a Label, you could also handle the Page.Init, Page.PreLoad, or Page.PreRender events. If the form did not have a master page, you update the label by handling the Page.PreInit event."

a dot is missing after {1}",OfficeSelectedLabel


SummaryLabel.Text = string.Format("Summary info:<br />Room: {0}<br />Delivery Date: {1}",OfficeSelectedLabelText,ServiceDateCalendar.SelectedDate.ToShortDateString());

should be:

SummaryLabel.Text = string.Format("Summary info:<br />Room: {0}<br />Delivery Date: {1}",OfficeSelectedLabel.Text,ServiceDateCalendar.SelectedDate.ToShortDateString());

Note from the Author or Editor:
Thanks for catching that. We should make this change as described.

the image url does not map to the href item of the img tag. This does not exsist. that is a <a href. The image tag uses <img src="" to locate the image

Note from the Author or Editor:
Sorry about that. Please change "href attribute" to "src attribute".

Error is in the physical book


error or typemismatch on page 108

(Label)Findcontrol("Feedbacklabel");
has to be replaced by:
(Label)panel1.Findcontrol("Feedbacklabel");

and

TextBox InputTextbox = (TextBox)FindControl("InputTextbox");
has to be replaced by:
TextBox InputTextbox = (TextBox)Panel1.FindControl("InputTextbox");

Note from the Author or Editor:
I'm sorry, I couldn't reproduce this error. The code sample worked for me with content pages and standard web forms in both web sites and web applications. Perhaps you could send me a non-working project to tony@northrup.org?

However, on pages 107 and 108, I would like to change "Page_PreInit" to "Page_Load".

There is a list of the panel control's properties. The property DefaultButton is listed twice (but description in the second case is something different). In fact I don't know what the correct property name would be for it's description.

Note from the Author or Editor:
Please remove the last bullet point. (Just a copy/paste error, probably)

Are you sure a CompositeControl needs to implement INamingContainer ?

There's none in the C# example and it works perfectly well.

Isn't it just the Templated Control that needs to provide a naming container? Specifically for the purpose that it has no UI, unlike the CompositeControl?

Note from the Author or Editor:
The last sentence on p 372 (carries to 373) should read:

You start by defining a class the inherits from CompositeControl. The following code shows the implementation of this control.

The code in the Sample of Visual Basic Code on p 373, top, should have the line "Implements INamingContainer" removed (line 4).

On page 135 in the sample code for both Visual Basic and C# the 1st parameter of the string.Format suggests that 3 additional parameters will follow ("User: {0}, Lang: {1}, Page: {2}"), however only 2 are supplied. I.e. something like 'Server.HtmlEncode(Request.QueryString["page"])' is missing.

Note from the Author or Editor:
Please change the sample code to:

Sample of Visual Basic Code
Label1.Text = String.Format("User: {0}, Lang: {1}, Page: {2}", _
Server.HtmlEncode(Request.QueryString("user")), _
Server.HtmlEncode(Request.QueryString("lang")), _
Server.HtmlEncode(Request.QueryString("page")))

Sample of C# Code
Label1.Text = string.Format("User: {0}, Lang: {1}, Page: {2}",
Server.HtmlEncode(Request.QueryString["user"]),
Server.HtmlEncode(Request.QueryString["lang"]),
Server.HtmlEncode(Request.QueryString["page"]));

//C#
Label1.Text = "User: " + Server.HtmlEncode(Request.QueryString["user"]) +
", Lang: " + Server.HtmlEncode(Request.QueryString["lang"]) +
", Page: " + Server.HtmlEncode(Request.QueryString["page"]);

In the chapter "Defining User Control Events" you wrote: "after the page Init event is called, the control's Init event is called".
I think that's not true. I tested it and also compared it with this page: http://msdn.microsoft.com/en-us/library/ms178472.aspx
where you can read the following text: "The Init event of individual controls occurs _before_ the Init event of the page".

Note from the Author or Editor:
You are right about the Init event. The text is correct for the Load event.

p. 333, the section, Defining User Control Events, first paragraph should now read as follows:

User controls can have their own encapsulated events. These include life cycle events such as Init and Load. These events are called in sync with the events on the page. For example, before the page?s Init event is called, the Init event for each control on the page is called. Processing then returns to the page for the Load event. First, the page?s OnLoad event is called. Next, the OnLoad event is called for each control on the page. Finally, the page?s Load event is called; then, each control on the page gets its Load event fired. This model allows you to develop user controls in a manner similar to developing a webpage.

NOTE NEUTRAL VS. SPECIFIC CULTURES
The first sentence and a note is incorrect. Instead it should read something like "This code sample uses CultureTypes.NeutralCultures cultures to get a list of cultures that provide only language information (for example just en instead of en-us)."

Note from the Author or Editor:
Please change the note text to read as follows (only changed the first sentence):

This code sample uses CultureTypes.NeutralCultures to get a list of cultures that are associated with a language but not specific to a country or region (for example en instead of en-us). You can use CultureTypes.SpecificCultures instead if you want the user to pick both language and culture. You can use neutral cultures to define the UICulture object, but you can only use specific cultures to define the Culture object.

It says to set the TextBox control CssClass to "textBox" and the Button control CssClass to "button" - neither of which exist in the Styles.css sheet. I suspect the example was different earlier and included these styles in the Styles.css file but now there is just the body tag. Please review and update the example.

Note from the Author or Editor:
Please change step 7 on page 70 to:

7. Add a style sheet to your Contoso theme and name it Style.css. Within the style sheet, define styles to set the default font family, size, and style for the HTML body and the CSS classes textBox and button. Your style sheet should resemble this:

body
{
font-family : Tahoma;
font-size : 10pt;
}

.textBox
{
font-style: italic;
}

.button
{
font-style: oblique;
font-size: 30pt;
}

On page 482 in the C# code example on line 10 where the code is as follows:

string callbackScript = String.Format("function MyServerCall(args) {{0};}, ", callbackRef);

I received a FormatException when running this code (errorMessage: "Input string was not in a correct format") on .Net 4.0 VS2010. The curly brackets were not escaped properly and causing String.Format method to throw an exception. I replaced the code with the following to allow for a successful build:

string callbackScript = String.Format("function MyServerCall(args) {{{0};}}", callbackRef);

Note from the Author or Editor:
There are 2 changes required for this fix (one for c# and one for vb).

In both cases, on page 482, after the comment "define a function used by the client to call the server" change the line (2 lines) to the following:

Dim callbackScript As String = String.Format( _
"function MyServerCall (args) {{{0};}}", callbackRef)


CHANGE the same line in the C# code example to the following:

string callbackScript = String.Format(
"function MyServerCall(args) {{{0};}}", callbackRef);

Quoting from page 475:
"The ASP.NET controls also have the ClientId property for changing the client ID from that of the server".

Are you sure? The ClientID property has no setter, it is read-only in fact. Its primary purpose is to use it in javascript code, such as:

document.getElementById("<%=Panel1.ClientID %>").style.display="none";

You should mention the ClientIDMode property instead, since it's a novelty of Asp.NET 4.0 and it's never mentioned elsewhere in the book. Page 475 seems like a good spot to talk about it.

Setting ClientIDMode="Static" will be helpful to those who want to know for sure what the client id will be.

Note from the Author or Editor:
Near the top of page 475, replace the entire paragraph that starts with "It is also important to note that you can" with the following:

It is also important to note that you can reference ASP.NET controls inside your client-side script. You reference them based on their rendering as HTML. The ASP.NET controls have the ClientId property for referencing the control inside client script or CSS rules. This property's value is generated based on how you set the ClientIDMode attribute. For example, to guarantee the ClientID value is always set to the value of the ID property, you can set ClientIDMode to Static. By default, the ClientIDMode is set to Predictable which means the ClientID value is generated by concatenating the ClientID of the parent container with the ID value of the control.

The first time the user clicks the button the page ViewState["mode"] will be empty, and nothing will happen. They will need to click the button twice in order for the functionality to kick-in.

To make this work you could do it the other way around and check if the mode is already set to "edit", otherwise enter the Catalog display mode. For example:

protected void ButtonEdit_Click(object sender, EventArgs e)
{
string mode = (string)ViewState["mode"];
if (mode == "edit")
{
ViewState["mode"] = "browse";
ButtonEdit.Text = "Edit";
WebPartManager1.DisplayMode = WebPartManager1.SupportedDisplayModes["Browse"];
}
else
{
ViewState["mode"] = "edit";
ButtonEdit.Text = "Done";
WebPartManager1.DisplayMode = WebPartManager1.SupportedDisplayModes["Catalog"];
}
}

Note from the Author or Editor:
Please change the first paragraph of page 268 to read:

The next step is to put the page into this display mode when the user clicks the Edit button. The following shows the code for the button's click event, and assumes that you added a string named mode with a value of browse to view state the first time the page loaded.

Both consumer and provider methods need to be made public, otherwise the WebPart connection between the two doesn't work.

Namely:
public void ShowTextBoxValue(string textBoxValue)
public string GetTextBoxValue()

instead of:
void ShowTextBoxValue(string textBoxValue)
string GetTextBoxValue()

Note from the Author or Editor:
On page 270, in the first code sample, in C#, change "string GetTextBoxValue()" to "public string GetTextBoxValue()"

In the second code sample, in C#, change "void ShowTextBoxValue(string textBoxValue)" to "public void ShowTextBoxValue(string textBoxValue)".

Text reads:

Duration - "this is the only required parameter"

but later in the table under VaryByParam, it is stated that "Either this attribute or the VaryByControl attribute is required when you use the @ OutputCache directive on ASP.NET pages and user controls. A parser error occurs if you fail to include it."

Also, the Microsoft web site http://msdn.microsoft.com/en-us/library/hdxfb6cy.aspx does not say that Duration is the only required parameter.

Remove the statement from Duration that this is the only required parameter.

Note from the Author or Editor:
Please change "This is the only required parameter." to "This is a required parameter."

The following example demostrates how to chache a page for 15 minutes

<%@ OutputCache Duration="15" ...

Duration is expressed in second so

Correct:
The following example demostrates how to chache a page for 15 seconds

Note from the Author or Editor:
Please change from "15 minutes" to "900 seconds".

Instruction 7 b reads:
"b. Inside ContentPlaceholderMain, add a TextBox control and name it UserNameTextBox."

Sample code under Step 9 reads:
"Session["UserName"] = NameTextBox.Text;"

NameTextBox and UserNameTextBox should be referring to the same control.

Also in the text of step 9 the same textbox is referred to as TextBoxUserName:
"Add code to the ButtonSubmit_Click method to determine
whether the user provided a value in the TextBoxUserName text box."

Note from the Author or Editor:
In Step 9, page 56, change "TextBoxUserName" to "UserNameTextBox". Also change "NameTextBox" to "UserNameTextBox" in the sample code (under both visual basic and C#).

The text references a GetSchedule method, even though no such method exists in the code example.

It must have been removed at some stage to simplify the example since the collection is now populated on Page_Load.

Note from the Author or Editor:
Correct. The first sentence of the paragraph should read, "This code adds dates to the calendar and then sets the Calendar control properties, such as style and size, in the Page_Load event handler." We should remove the sentence, "A method called GetSchedule is added to populate a collection of special dates."

Thanks for catching that!

By default, Visual Studio configures ...

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

,but by default VS2010 configures only with virtual path

<%@ Page Language="VB" MasterPageFile="~/MySite.Master" %>



and too (page #48)



In a Web.config

<pages MasterPageFile="MySite.Master" /> - don't work

only with virtual path

<pages MasterPageFile="~/MySite.Master" />

Note from the Author or Editor:
Valid point, please change both instances as described.

Not sure if I should report errata for the Practice Tests here.

[QUESTION 515P_1.2_04]
The correct answer has a mistake, in fact the @Master directive has no "master" attribute that can be set. Instead, the MasterPageFile attribute should be used:
<%@ Master Language="C#" MasterPageFile="~/Blue.master" />

Source: http://msdn.microsoft.com/en-us/library/x2b3ktt7%28v=vs.80%29.aspx


[QUESTION 515P_2.2_03]
The correct answer is incomplete. The consumer method GetStockSymbols() should have a string parameter to match the return type of the provider method.

[QUESTION 515P_1.5_04]
The Reference paragraph states that the asp:SqlDataSource is covered in Chapter 2, Lesson 3 of the book. However, there's no mention of that control in the second chapter of the book. The first time it's mentioned is in chapter 9, and properly covered in chapter 12.

Note from the Author or Editor:
These are all valid and the PTQs should be updated accordingly.

The WebGetAttribute is missing from the answer.
(http://msdn.microsoft.com/en-us/library/bb412204.aspx)

Rest services by convention use GET to list or retrieve resources.
(http://en.wikipedia.org/wiki/Representational_State_Transfer#RESTful_web_services)

Note from the Author or Editor:
On p. 611 Quick Check Answer #3 should read:

3. You mark the service with either the WebInvokeAttribute or WebGetAttribute class.

Should have been DataCollection.aspx and not the ProcessingPage.
<%@ PreviousPageType VirtualPath="~/ProcessingPage.aspx" %>

Please check ,
http://msdn.microsoft.com/en-us/library/ms178139.aspx

Note from the Author or Editor:
Correct, please change, "The processing page contains a Label control..." to "The DataCollection.aspx page contains a Label control..."

Answer to question 4 of Chapter 6, Lesson 1 should be D, not A.

D is deemed incorrect with this explaination: "ASP.NET does not create strongly typed properties inside the Resources class. Instead, you must use the Resources.Resource object."

This is in contradiction with the first paragraph of page 303, which states:
"ASP.NET creates an object that allows you to access global resource values programmatically by using the Resources.ResourceFilename.Resource syntax. This is a strongly typed class of the Resources.Resource object for each global resource file."

This is confirmed by Visual Studio intellisense.

Note from the Author or Editor:
The question is correct but somewhat unclear.

Please change question 4 on page 312 to read as follows:
4. You add a global resource with the name Login to the resource file named Resource.resx. How can you access that global resource programmatically?

Please then change the answer to question 4 on page 897 to read:
A. Correct: ASP.NET will automatically create a strongly typed object for your global resources. This object can be referenced as Resources.ResourceFileName.Resource (or Resources.Resource.Login in this case).

The book states: "if you use the Button web server control, ASP.NET renders it using the <button> HTML markup tag".
Nope, it doesn't. Asp.NET renders an <asp:Button runat="server" /> as an <input type="submit" />

Note from the Author or Editor:
Valid point. Please change this sentence:

"... if you use the Button web server control, ASP.NET renders it using the <button> HTML markup tag."

to:

"... if you use the Image web server control, ASP.NET renders it using the <img> HTML markup tag."

At the end of the 3rd paragaraph of "The ImageButton Control" section, it is listed that GenerateEmptyAlternateText is a property of ImageButton. However, it is NOT.

Note from the Author or Editor:
This is valid. Please remove GenerateEmptyAlternateText from that sentence.

SelectionMode of Calendar Control should be:
Day
Week
DayWeekMonth (Not WeekMonth)
None (Not one)

Note from the Author or Editor:
Correct, please update accordingly.

The note saying that "Projects created with the ASP.NET Web Application template are always precompiled" is misleading. While it is true that the code files are precompiled, this is NOT the case for .aspx files. Therefore, the section involving indicating whether or not a site should be updatable is equally applicable to ASP.NET Web Application template projects as well.

Note from the Author or Editor:
Valid point. Please change the last sentence of the note to,

"Visual Studio always precompiles code files contained within projects created with the ASP.NET Web Application template."

Case-Sensitive: Instead of <pages Theme=?themeName?> and <pages StyleSheetTheme=?themeName?>, it should be <pages theme=... and <pages styleSheetTheme=...

Note from the Author or Editor:
Valid; we need to make the change as described.

Again, attributes in web.config are case-sensitive.

Note from the Author or Editor:
Valid. In step 2, please change "<pages Theme=" to "<pages theme=". In step 5, please change "<pages StyleSheetTheme=" to "<pages styleSheetTheme=".

Attributes in web.config are case-sensitive: It should be 'theme' ans 'styleSheetTheme', not 'Theme' and 'StyleSheetTheme'.

Note from the Author or Editor:
Valid. Please change "<pages Theme=" to "<pages theme=" and "<pages StyleSheetTheme=" to "<pages styleSheetTheme=".

In "To enable pages to insert content
into a master page, you must add one or more ContentPlaceHolder controls to the content
page.", it should be used 'Content controls to the content page' or 'ContentPlaceHolder controls to the master page'.

Note from the Author or Editor:
Correct, it should be "ContentPlaceHolder controls to the master page"

In the source code the cells of the Table control are created and added to the Table, however as the initialization of the Table should not work in the Page_PreInit method because the controls are not still initialized at this point. That is why the code should the run in the Page_Init or in the Page_Load method. Is is correct?

Best regards,

Omar Diego

Note from the Author or Editor:
You're right, we need to change "Page_PreInit" on both pages 188 and 189 to "Page_Load".