Errata

The author uses "Personal Home Page" acronym to describe PHP.

But, now PHP stands for PHP: Hypertext Preprocessor. This confuses many people because the first word of the acronym is the acronym. This type of acronym is called a recursive acronym.

This explanation can be found at http://www.php.net/manual/en/faq.general.php#faq.general.acronym.

In 1995, Rasmus Lerdorf named "Personal Home Page" Tools.

With the launch of PHP 3.0, in June 1998, it was named plain "PHP", with the meaning being a recursive acronym - PHP: Hypertext Preprocessor. See the history of PHP at http://www.php.net/manual/en/history.php.php.

The classic ASP code bellow:

<input name="TextBox1" type="text" value='<% Request.Form["TextBox1"] %>' />

Must be:

<input name="TextBox1" type="text" value='<%= Request.Form["TextBox1"] %>' />

<%= ... %> is equivalent to <% Response.Write(...) %>

Rogerio Moraes de Carvalho
Twitter: @rogeriomc

"In an ASP.NET page, any user action (such as clicking or changing the current selection) originates a postback."

Server click events originates a postback, but server change events only originates a postback if the AutoPostBack boolean property is true. The default value is false.

The affirmation that "any user action" originates a postback is not so real. The truth is that most client-side events are not translated to server-side events. For example, the onmouseover client-side event.

The following book code is invalid in C#:

public interface IHttpHandler
{
public void ProcessRequest(HttpContext context);
public bool IsReusable;
}

The correct code must be:

public interface IHttpHandler
{
void ProcessRequest(HttpContext context);
bool IsReusable { get; }
}

Notes:
- In C#, the modifier 'public' is not valid for interfaces.
- In C#, interfaces cannot contain fields. In that case, IsReusable is a read-only property, not a field. The correct is showed above.

"Each page consists of two files: an .aspx markup file describing the expected HTML template and a C# (or Visual Basic) class file that contains postback handlers and any ancillary methods."

This is the main choice for Web Forms pages: an markup code for the interface (.aspx), and a class page for code-behind (.aspx.cs or .aspx.vb). But, it is possible to mix markup code with the Page class code in only one .aspx page.

"Postback" appears in the figure as an event of the page life cycle, but it isn't.

The following list shows the page life-cycle events that you will use most frequently:
- PreInit
- Init
- InitComplete
- PreLoad
- Load
- Control events
- LoadComplete
- PreRender
- PreRenderComplete
- SaveStateComplete
- Render
- Unload
More information: "ASP.NET Page Life Cycle Overview": http://msdn.microsoft.com/en-us/library/ms178472.aspx

The "Your code-behind class" box in the figure omits the "class" keyword.

The following code is in the book:
public _Default : System.Web.UI.Page
{

}

The following code corrects the book's code:
public class _Default : System.Web.UI.Page
{

}

Note: Since ASP.NET 2.0, the code-behind class use the"partial keyword modifier.

"Any customization is possible only in the code-behind class of a page."

Actually, a customization is possible in a user defined class. It can inherit the System.Web.UI.Page class, for example. In this case, some pages can inherit directly from the user defined page class.