Programming ASP.NET, 2nd Edition
by Jesse Liberty, Dan Hurwitz

This errata page lists errors outstanding in the most recent printing.

If you have technical questions or error reports, you can send them to
booktech@oreilly.com.  Please specify the printing date of your copy.

This page was updated November 9, 2004.

Here's a key to the markup:
	[page-number]: serious technical mistake
	{page-number}: minor technical mistake
	<page-number>: important language/formatting problem
	(page-number): language change or minor formatting problem
	?page-number?: reader question or request for clarification



Confirmed errors:


(6) 2nd paragraph of sidebar;
    www.MyServer.com/HellowWorld.htm
should be:
    www.MyServer.com/HelloWorld.htm



(22)  2nd to last paragraph;
Bad line break: "The .sln file contains a list..." breaks after "."!



(46)  Macro Explorer paragraph;
Extraneous "the" in "The Macro Explorer is the one of the main tools..."
It should say:
"The Macro Explorer is one of the main tools..."


(51)  Connect to Device paragraph;
"physical" is misspelled in "...to either a phyiscal mobile device or an emulator."
It should say:
"...to either a physical mobile device or an emulator."


[255]  first paragraph;
In the following sentence:

You can set and retrieve values of things in the state bag using the ViewState keyword, ...

ViewState is NOT a keyword but an (protected) attribute of the Page class.



Page 266 -  Penultimate paragraph
Currently: Session state is stored in server memory ... the session state is not lost.
Should Be: By default, sesstion state is stored in server memory as part of the ASP.NET process. However, as will be shown shortly, it can be configured to be stored separately from the ASP.NET process, either on a separate state server or in a SQL Server database, in which case it will survive a crash or restart of the ASP.NET process.



Page 274 - [1/28/04] Penultimate paragraph
Currently: Session state is stored in server memory ... the session state is not lost.
Should Be: By default, sesstion state is stored in server memory as part of the ASP.NET process. However, using the the mode attribute of the sessionState tag in web.config, it can be configured to be stored separately from the ASP.NET process, either on a separate state server or in a SQL Server database, in which case it will survive a crash or restart of the ASP.NET process.



{351}  Example 8-8, ServerValidator method;
Same problem as on page 348: as written, e.IsValid is never set to false.



(547)  3rd text paragraph;
The text 
"Notice that you are hardwiring the status (1 = open), the action (Bug Created) and the owner (6 = a person in QA)." 
refers to owner number 6, but the code snippet directly above refers to owner number 1. 
Since Example 12-3 also refers to owner 1, the text should be "(1 = the first user)".