Errata

... has no user interface (UI)

I think it should be ... has no Graphical User Interface (GUI)

Missing code?

On page 38, the program spec says that if the temp is higher than 32 degrees, the
program should assure you that there is no ice. The code on page 39 does not satisfy
that requirement. There seems to be a blank line 2 lines up from the class's closing
brace, where an else clause probably belongs to account for the temp > 32 case.

I class this as serious simply because you state something that is completely wrong
(though I can see it as an easy mistake!).
Example 3-14 on page 43 shows code to output numbers to 100, tabing right at end and
repeating every 10 numbers.
The box after this shows some examples of whitespace, which are valid, but then ends
with:

Because single for and if statements do not need braces, we can also rewrite the same
listing as:

for (int i = 0; i < 100; i++)
Console.Write("{0} ", i);

if (i % 10 == 0)
Console.WriteLine(" {0}", i);

However, without the braces in the for-loop, the variable, i, in the following if-
statement is out of scope! A subject you actually show by example in the code of
example 3-14 on the previous page!!
I'm sure you can see what I mean... because of the semi-colon at the end of the
single statement of the for-loop, you would get a line of 1 - 99, and then... well,
actually, this wouldn't compile, would it??

On pages 70 and 72, the System.DateTime.now property is accessed in order to retrieve
the current time.

However, on page 71 the third paragraph says "Examine the highlighted line in Main(),
where the DateTime object is created by calling the static method Now(). Now()
creates a DateTime object on the heap and returns a reference to it."

The highlighted line might _cause_ Now() to be called, but it's not in that code
line, so without an explanation of properties, which hasn't occurred yet, the careful
reader is left confused

I puzzled for a long time about the presence of two contructors for the same class in
this example. How can a class have more than one constructor? How would the C#
compiler decide which contstructor to use? I finally deduced (and confirmed by asking
a friend) that the compiler would have to use the number or type of arguments in the
method to decide. Finally, on page 87, the concept of overloading methods is
introduced.

Perhaps my confusion could have been avoided if a brief note about overloading
methods had been included prior to the example (or, alternately, if a different
example had been used).

The Time class referred to in the sentence

"For example, you might add the following static constructor to Time:"

comes after almost 4 pages of text and code examples that are completely unrelated to
the Time example.

It might be more clear to instead state

"For example, you might add the following static constructor to the Time class used
in Example 4-4:"

It is confusing to find a discussion of private (non-static) constructors sandwiched
in between sections on static constructors and static fields.

It would be more clear to include this section in or around the tip "Resist the
temptation" on page 75.

(Too serious to call it a typo!)

Figure 5-3 is supposed to show a picture of the refactored hierarchy described on the
bottom of page 96 and top of page 97.

Instead, it duplicates the picture in Figure 5-2!!

The code doesn't build correctly, the following errors occur in the Button class:
'ConsoleApplication8.Window.top' is inaccessible due to its protection level
'ConsoleApplication8.Window.left' is inaccessible due to its protection level

If I replace this:
public virtual void DrawWindow()
(
Console.WriteLine("top: {0}, left: {1}", top, left);
}

with this:
public virtual void DrawWindow()
{
base.DrawWindow();
}
the problem goes away

The tip box on 182 advises that the "params" keyword should
be used since "you cannot know how many strings will
be added". It seems to me that the "params" keyword
is meant to be used as a more restrictive version of
the va_list found in C, and that it would be more appropriate
to take the "params" keyword out. Thus, the constructor
should be declared as "public ListBoxTest(string[] initStrings)",
which says I am passing in an array of strings of unspecified
length. Am I missing something? I don't understand why
params is needed.

Following line should be added at the beginning of th example
using System.Drawing;

The section on "Using Monitors" implies that the system of monitors in C# is separate
from the system of locks, and that if you want to use Monitor.Wait and Monitor.Pulse,
you need to use Monitor.Enter and Monitor.Exit explicitly. This is not the case. To
quote the .NET framework documentation:

"The functionality provided by the Enter and Exit methods is identical to that
provided by the C# lock statement."

In other words:

lock (foo)