Errata

"enums" s/b "Enums"

"events" s/b "Events"

TOC summary ends with Lab 3.
Doesn't include "appendix i: leftovers", starting on page 703.

"startbuilding" s/b "start building"

"You'll make your object's data private, add methods to protect how that data is accessed."

s/b

"You'll make your object's data private, and add methods to protect how that data is accessed."

"subscibe" s/b "subscribe"

This should be "#5 Windows Presentation Framework" -- it's missing the # at the beginning.

Missing period.

"installation That should" s/b
"installation. That should"

Screenshot on page replaced in reprint with an image that shows how the installer looks now that the final version of Visual Studio Express is out ( vs08setup.png). Even though the picture looks different all of the text stays the same.

"execises" s/b "exercises"

In the header and first line of body text change "Windows Presentation Framework" to "Windows Presentation Foundation".

Here are two interfaces. IClown defines a clown who honks his horn and has a funny thing. IScaryClown inherits from clown. A scary clown does everything a clown does, plus he has a scary thing and scares little children.

The FunnyFunny class implements the IClown interface. We made the funnyThingIHave field protected so that it can be accessed by any instance of a subclass of FunnyFunny.

The ScaryScary class implements the IScaryClown interface. It also inherits from FunnyFunny, and since FunnyFunny implements IClown, that means ScaryScary does too. Take a look at how the ScareLittleChildren() method accesses the funnyThingIHave backing f

Here's a button that instantiates FunnyFunny and ScaryScary. Take a look at how it uses as to downcast someFunnyClown to an IScaryClown reference.

This is supposed to be a filled-in answer. There should be dotted-line blanks under it.

remove the top right annotation "We've blown up..."

Change "writes the action code, or the code that does the work" to "writes the code that actually does the work"

1. It is Not the Size property but the "Size Mode" property that we change to "Zoom"

2. The book says, setting the "size mode" property to "zoom" will match the size of the picture box control to the size of the picture we put in it, but actually it is the reverse. The size of the picture/image will be changed to match the size of the picturebox control.

3. I love you guys!! (and it is not an error in the book!)

Note from the Author or Editor:
In the third line of text for step 2, change "Size property" to "Size Mode property"

Add an annotation pointing to the paragraph for #2 that says:
You can also use the "Properties" window in the IDE to set the Size property. The little black arrow is just there to make it easy to access the most common properties of any control.

to this:
You'll see a Select Resource window pop up. Click the "Local Resource" radio button to enable the "Import..." button at the top of the form. Click that button, find your logo, and you're all set:

Add a new annotation to this page underneath the middle one that starts 'Choose "Zoom"' with an arrow pointing up at that annotation. It should say:
Then click "Choose Image" to bring up the Select Resource dialog box so you can import a local resource.

If you click on Form1.resx in the Solution Explorer, you can see the logo that you imported.

to this:
Go to the Solution Explorer and click on the plus icon next to Form1.cs to expand it (if it's not already expanded). This will display two files: Form1.Designer.cs and Form1.resx. Double-click on Form1.resx, click on the arrow next to "Strings", and select "Images" from the drop-down list (or hit Ctrl-2) to see the logo that you imported.

Add an annotation pointing to the third screenshot on the page that's displaying pictureBox1.Image. The annotation should read:
If you chose the other "Import..." button from the Select Resource dialog on the last page, then your image will show up in the Resources folder in the Solution Explorer instead. Don't worry -- just go back to Select Resources, choose "Local Resource", and re-import the image into the resources and it'll show up here.

Click on the Add button in the Add New Item window.

"queries that you are stored" should be "queries that are stored"

Add an annotation that points to the IsIdentity line in the screenshot on this page that says "You'll need to click on the right column and select Yes from the drop down next to IsIdentity to designate ContactID as your record Identifier."

Instead of saying "you're going to track", the book says "your going to track"

laverne.smith@xyzindustries.com

"the other five columns" should read "the other six columns"

Note from the Author or Editor:
In the second line of body text, change "the other five columns" to "the other columns"

Add a note in the blank space in the top-left corner of the page:

In very rare cases, a few people sometimes have problems getting the SQL database to work. If you run into any trouble, don't worry -- go to the Head First C# forum at http://headfirstlabs.com/hfcsharp/ for help troubleshooting the problem.

And replace the top paragraph of body text with:
?The Visual Studio IDE is built to work with databases, and it comes with a lot of built-in tools that help you when you?re handling a lot of data. One of the most powerful tools you have is the database diagram, which you can use to view and edit complex relationships between the tables in your database. So let?s go ahead and build a database diagram for your database.?

?The IDE then uses the database diagram to auto generate code to work with your database.?
To this:
?The IDE will read your database and build a database diagram for you automatically.?

Objectville Paper Company is in the United States, so the CEO writes dates so that 05/26/07 means May 26, 2007. If your machine is set to a different location, you may need to enter dates differently -- you might need to use 26/05/07 instead.

Phone number[(212)555-81125] has too many numbers in it. It should be (212)555-8125.

Both emails are missing the "." between xyzindustries and com

Click the plus sign next to the People table to expand it -- you'll see the columns that you added to your table. When you click on the People table in the Data Sources window and drag it onto your form, the IDE automatically adds data controls to your form that the user can use to browse and enter data. By default it adds a DataGridView, which lets the user work with the data using one big spreadsheet-like control. Click the arrow next to the People table and select Details -- that tells the IDE to add individual controls to your form for each column in the table.

Change it to say this: "Click this arrow and choose 'Details' to tell the IDE to add individual controls to your form rather than one large spreadsheet-like data control."

In the bottom annotation, change "fields" to "columns".

Every time you build your program, the IDE puts a fresh copy of the database in the bin folder. This will overwrite any data you added when you ran the program. When you debug your program, the IDE rebuilds it if the code has changed -- which means that your database will sometimes get overwritten when you run your program in the IDE. If you run the program directly from the bin/debug or bin/release folder, or if use the installer to install it on your machine, then you won't see this problem.

Add this sentence to the annotation: "They're part of ContactDB.mdf database file, which gets installed along with your program."

Remove the word "just" from the bottom annotation ("The Properties window in the IDE is a really easy way").

change "select it" to "tell the IDE to fill it in for you"

The underline isn't lined up with the words "inside a class"

Add another annotation underneath this one pointing up at it that says: "You'll see slightly different using lines if you're using Visual Studio 2005"

Change "Let's remove the Main method" to "Open up the program you wrote in Chapter 1 and remove the Main method"

Change "messagebox" to "MessageBox"

Put a period after "adapted" and capitalize "The" in "The drill's"

Add a sentence to the end of the annotation: The test is run before the code block, and the block is executed only if the test is true.

Add a sentence to the end of the annotation: This is called the iterator, and it's run immediately after all of the statements in the code block.
(make the color of "immediately after" black and underline it)

The annotation "Hint: q starts out equal to zero" is wrong as q starts out equal to 2 as initialized by the header of the for loop.

Note from the Author or Editor:
In the bottom right annotation, change "equal to zero" to "equal to 2"

Add an annotation pointing up at the Sharpen that says: "Remember, a for loop always runs the conditional test at the beginning of the block, and the iterator at the end of the block"

Change this: ?Yes, there are a few namespaces you?re not allowed to use.?
To this: ?Technically there aren?t any namespaces you?re not allowed to use. But there are several namespaces that .NET uses, and it?s a bad idea to use them yourself.?

to this: "from 0 to 253"

Change the second annotation to: ?This line tells the program to stop your loop momentarily and do the other things it needs to do, like refresh the form, check for mouse clicks, etc. Try taking out this line and seeing what happens. The form doesn?t redraw itself, because it?s waiting until the loop is done before it deals with those events.?
Add another annotation pointing up at it: ?Later on in the book, you?ll learn about a better way to let your programs do more than one thing at a time! But for now, use Application.DoEvents() to make sure your form stays responsive while it?s in a loop.?

We used "&& Visible" instead of "&& Visible == true". It's just like saying "if it's visible" instead of "if it's true that it's visible" -- they mean the same thing.

Change "&& Visible == true" to "&& Visible"

The solution for Code Magnets given is not the only solution. Try:
string Result = ""; //declarations and initial assignments

int x = 3;

while (x > 0) {
if (x > 2) {
Result = Result + "a";
}

if (x == 2) {
Result = Result + "b c";
}
x = x - 1;
Result = Result + "-";

if (x==1) {
Result = Result + "d";
x = x - 1;
}
}
MessageBox.Show(Result);

Note from the Author or Editor:
Add an annotation at the very bottom of the page:

This Code Magnets has more than one solution! Can you find another way to arrange the magnets and get the same result?

The book gives "1en" in the code on page 89. That did not work. My youngest son pointed out that "You can't prefix variables with numbers." The correction is to change "1en" to "en1". Then the program worked properly.

Note from the Author or Editor:
Change "len" to "length" in the text for step #3 -- make sure the font is kept as courier new:

Then double-click on the button and have it run this code that calls
BlahBlahBlah() and assigns its return value to an integer called length:


Then change the two occurrences of "len" in the code that follows to "length":


int length = Talker.BlahBlahBlah(textBox1.Text, (int) numericUpDown1.Value);
MessageBox.Show(?The message length is ? + length);

The line says "When it's called, it pops up a MessageBox with the message repated..." repated is not repeated - grammatical error.

"repated" should be "repeated"

"... a number of its numberOfTimes parameter." change to:
"... a number for its numberOfTimes parameter."

"Open any project that uses a button called button1, and use the IDE to
search the entire project for the text "new button1".

should read

"Open any project that uses a button called button1, and use the IDE to
search the entire project for the text "button1 = new".

semicolon missing after "Navigator navigator1 = new Navigator()" in the second line of code under step 2 on page 94, fourth line of code on page 95, fourth line of code on page 96

Fill in its name and method.

Should be:

Fill in its name and methods.

Note from the Author or Editor:
This is p107 in the second edition. Bottom annotation: change "method" to "methods"

first off, this errata submission form needs a field for the printing revision (and a hint telling users how to find it). Mine was the [9/08] version. This is the latest version as far as I know.


Assuming the code on page 111 is left as-is, the text for Step 3 at the bottom of page 110 is seriously incorrect. I would revise the sentence after the Step 3 heading text to be:

"We'll use each guy's GiveCash() method to transfer cash FROM a guy, and we'll use his ReceiveCash() method to transfer cash TO a guy."

This is in fact the EXACT OPPOSITE the current text which says:

"We'll use each guy's GiveCash() method to give cash to a guy, and we'll use his ReceiveCash() method to take cash back from him."


In the graphical text associated with Step 3, there are 4 instances of ReceiveCash() that need to be changed to GiveCash().

For the graphics at the bottom of page 110 to be correct, the only way the Joe object can go from having $100 to having $75 is by having a calling program invoke joe.GiveCash(25), NOT joe.ReceiveCash(25).


Those two method names, GiveCash() and ReceiveCash(), are from the point of view of the object (as is made clear in the text on page 111).

This caused me quite a bit of confusion.

Note from the Author or Editor:
Change the bottom annotation to this:

The method returns the number of bucks that were taken. We called it "ReceiveCash" because the form's receiving cash from Joe. Do you think we chose good method names? Can you think of better ones?

top annotation, third line: change "lives" to "live"

In the title line, change "six labels" to "three labels"
In the first line of the paragraph, change "The labels on the right-hand side of the form" to "The top two labels".
In the second line of the paragraph, change "the third label on the right" to "the third label"
In the last line, change "label4 and label5" to "label1 and label2"

A program to help a zoo keeper track her animals'feeding schedules might have classes for different kinds of food and types of animals.

Should be:

A program to help a zoo keeper track her animals' feeding schedules might have classes for different kinds of food and types of animals.

Note from the Author or Editor:
This is p118 in the second edition -- there's a space missing before "feeding" in the first line of the second bullet

"Object intializers save you time and..." s/b "intializers".

Note from the Author or Editor:
In the first line of the sidebar, change "intializers" to "initializers"

In the first line of body text, change boldfaced text ?value types? to ?types?.
In the first boldfaced heading, change ?Value types? to ?Types?.

When your program needs to deal with currency, you usually want to use a decimal to store the number.

* Change this: ?scientific application where the numbers need to be extremely accurate, the decimal type has the most precision.?
To this: ?financial application where you?ll be storing currency values, you?ll want to use the decimal type.?

* In the bottom paragraph, change ?There?s no set size for a string variable? to ?There?s no set size for a string object?

* Remove this annotation:
string is pretty unique. It?s the only data type without a set size, except for objects (think about that for a bit).

* In the thought bubble, change ?casting this whole time?? to ?converting types all along??
* In the heading underneath it, change ?casts for you? to ?converts for you?
* In the second line of body text underneath that, change ?a lot of casting? to ?a lot of converting?
* In the third-to-last line in that paragraph, change ?automatically casts? to ?automatically converts?
* In the second-to-last line on the page, change ?casts myInt? to ?converts myInt?

In the bottom paragraph, change this: ?(an argument is another name for a method?s parameter)?
To this: ?(an argument is what C# calls the value that you?re passing into a method?s parameter)?

"Now try passing it a boolean, but assigning the return value to a long" should change to: "Now try passing it a boolean but assigning the return value to a string."

Add this to the end of the first paragraph: ?(Sometimes C# can do the conversion automatically ? like if your method expects an int, but you pass it a short ? but it can?t do that for ints and strings.)?

* In the instructions, change ?know them all? to ?know a lot of them? [p161, too]
* Add an annotation to the top of the page: ?Actually, C# does give you a way to use reserved keywords as variable names, by putting @ in front of the keyword. You can do that with non-reserved names too, if you want to.?

instructions - replace "odometer" with "mileage reading from the car's odometer"

"Every one of these labels is reference variable, but ...??
Change the annotation just underneath and to the right of the picture to this: ?Every one of the labels is a different reference variable, but they all point to the SAME Guy object.?

Change the last annotation to: "The WhoAmI() method should pop up this message box. Make sure the message includes the ear size and the title bar includes the name."

strings and arrays are different from all of the other data types you?ve seen because they?re the only ones without a set size (think about that for a bit).

last line change "nubmered" to "numbered"

Currently: "Add a GetMenItem()..."
Should be: "Add a GetMenuItem()..."

Currently: "... reference ot it somewhere."
Should be: "... reference to it somewhere."

Note from the Author or Editor:
'ot' should be 'to

Currently: "... reference ot it somewhere."
Should be: "... reference to it somewhere."

Change "(non-static) a" to "a (non-static)"

Add a colon after "labels" -- "References are like labels:"

In the last answer, sixth line, change "with an class" to "with a class"

add an annotation pointing to "public Label MyLabel; // My Label" that reads:

"Once you set MyLabel to one of the labels on the form, you'll be able to
change the label's text using MyLabel.Text. And the same goes for
MyRadioButton!"

Add an annotation pointing to the screenshot that says: Make sure you set each PictureBox's SizeMode property to Zoom

the "Close" is cut off

Change 94 to 54 (to match page 190)

Note from the Author or Editor:
In the second edition, this is page 195

Change "loyalCustomerAmount" to loyalCustomerOrderAmount to match the code on p189 & p190

Note from the Author or Editor:
In the second edition, this is on page 196

Even though you created a local variable called loyalCustomerAmount and set it to 54, that didn't change the object's loyalCustomerAmount value, which is still 60 -- so it won't print the secret ingredient.

3rd annotation, last line.
The errata changed "private numberOfCows field" to "private numberOfCows property." Isn't field correct? Technically, numberOfCows is the backing field, NumberOfCows is the property. The other changes by this errata appear correct.

Note from the Author or Editor:
In the third errata, change the last three words from this:

private numberOfCows property.

to this:

private numberOfCows field.

In the second annotation, change ?You use properties? to ?You?ll often use properties?

Change the first few words from this: Name this button Calculate
to this: Name this button "calculate"

"Add a button the form that executes this statement."

to:

"Add a button to the form that executes this statement."

Add an annotation pointing to the second line of code ("public int FeedMultiplier"):
This automatic property acts just like an int field. It has a public get, which means any other class can read the value of FeedMultiplier. But since its set is private, that makes it read-only -- it can only be set by an instance of Farmer.

In line 3 of the body text, change ?You?ve seen how you poor? to ?You?ve seen how poor?

---

p197- In the body text on the top of p197, in the fourth line change this:

very first thing that gets run when the class is created

to this

very first thing that gets run when the class is instantiated

add a comma after private ("...fields that need to be initialized are private, then an object initializer...")

In Step 1:
Change the last sentence of the paragraph for step 1 from:
"Then we?ll set the two properties."
to
"We'll change feedMultiplier from a const to an int. We'll need a value for it, so let's make sure it gets passed into the constructor. We'll use the constructor to set the number of cows, too."

Right underneath that, change the code from this:

public Farmer(int numberOfCows, int feedMultiplier) {
FeedMultiplier = feedMultiplier;
this.NumberOfCows = numberOfCows;
}

to this:

private int feedMultiplier;
public Farmer(int numberOfCows, int feedMultiplier) {
this.feedMultiplier = feedMultiplier;
NumberOfCows = numberOfCows;
}

In the second annotation in the left margin of p197, change "new()" to "new" and put it in Courier.

Add two annotations to p197 pointing to the code "private int feedMultiplier;":

* We'll change feedMultiplier from a const to an int field.

* Since we changed FeedMultiplier from a public const to a private int field, we changed its name so its starts with a lowercase f. That's a pretty standard naming convention you'll see throughout the book.

Also, in the annotation pointing to "NumberOfCows", remove "this." from "this.NumberOfCows" -- it should just be "NumberOfCows".

p198 - the "Way Up Close" box at the top of the page

Make sure the code in this box matches the code on page 197:

private int feedMultiplier;
public Farmer(int numberOfCows, int feedMultiplier) {
this.feedMultiplier = feedMultiplier;
NumberOfCows = numberOfCows;
}

In this annotation:

We need to set the feed multiplier first, because the second statement calls the NumberOfCows set accessor, which needs FeedMultiplier to have a value in order to set BagsOfFeed.

change "FeedMultiplier" to "feedMultiplier" (with a lowercase f)

In this annotation:

You?ll often see the this keyword a constructor. By calling this.NumberOfCows, we?re telling C# to set the NumberOfCows property using its public set accessor.

Make sure it points to "this." in the "this.feedMultiplier = feedMultiplier;" line in the code. Then change the annotation to say this instead:

We need a way to differentiate the field called feedMultiplier from the parameter with the same name. That's where the "this." keyword comes in really handy.

Change this annotation:

If you leave off ?this.? then C# will call the private set accessor instead. Give it a shot?remove ?this.? and see for yourself.

to this:

Since "this" is always a reference to the current object, this.feedMultiplier refers to the field. If you leave "this" off, then feedMultiplier refers to the parameter. So the first line in the constructor sets the private feedMultiplier field equal to the second parameter of the constructor.

Also in the last paragraph of the No Dumb Questions answer, change:

The InitializeComponent() method is called inside the form's constructor is so that the controls all get initialized...

to:

The InitializeComponent() method is called inside the form's constructor so that the controls all get initialized

---

change "one that's declare inside a field and called..." to "one that looks ljust like a field to other objects, and called..."

Add the following text to the beginning of the paragraph:

"Case matters in C#. You can have two different variables called Party and party in the same method.
It'll be confusing to read, but your code will compile just fine."

CalculateCostODecorations() is missing an "f" after the "O". It should be changed to "CalculateCostOfDecorations()".

This block of code is missing a colon;

public class Rowboat boat {
public string rowTheBoat() {
return "stroke natasha"
}
}

should be

public class Rowboat : boat {
public string rowTheBoat() {
return "stroke natasha"
}
}

This block of code is missing a colon;

public class Rowboat boat {
public string rowTheBoat() {
return "stroke natasha"
}
}

should be:

public class Rowboat : boat {
public string rowTheBoat() {
return "stroke natasha"
}
}

Change the first sentence of the body text from this:
If your class has a constructor, then any class that inherits from it must call that constructor.
To this:
If your class has constructors which take parameters, then any class that inherits from it must call one of those constructors.
In the middle right-hand annotation, change ?didn?t inherit the constructor properly? to ?didn?t call the base constructor?

In step 2, second bullet, change ?subclasses only inherit? to ?subclasses can only see?
Add an annotation pointing to that bullet that says: ?Later on, you?ll learn about the ?protected? keyword. A protected field is public to a subclass, but private to everyone else.?

On page number 239, Number 2, second sentence, it says "Once the queen's done assinging". Should be assigning.

On page 240, sixth bullet, second line, it says "He keeps track of how many shifts are left in the current job.". It should be "in the ShiftsLeft".

On page number 239, Number 2, second sentence, it says "Once the queen's done assinging". Should be assigning.

In the box where the head says "String.IsNullOrEmpty", the sentence goes a bit weird. "Since each bee stores its current job as a string, the way the worker knows whether or not he's not currently doing a job is to check if his CurrentJob property-". If his CurrentJob what?

Note from the Author or Editor:
Change the first sentence in the String.IsNullOrEmpty() box at the bottom of the page to:
Each bee stores its current job as a string. So a worker can figure out if he's currently doing a job by checking his CurrentJob property ? it'll be equal to an empty string if he?s waiting for his next job.

In the box where the head says "String.IsNullOrEmpty", the sentence goes a bit weird. "Since each bee stores its current job as a string, the way the worker knows whether or not he's not currently doing a job is to check if his CurrentJob property-". If his CurrentJob what?

Change the first sentence in the ?String.IsNullOrEmpty()? box at the bottom of the page to:
Each bee stores its current job as a string. So a worker can figure out if he?s currently doing a job by checking his CurrentJob property ? it?ll be equal to an empty string if he?s waiting for his next job.

Add an annotation pointing to the Bee class diagram: "Sometimes we'll show you return values and private members in class diagrams."

* "Add Existing Item" helper box;
The box titled "Add Existing Item" leaves out the step to choose "Add Existing Item" from the menu. It says:

- Right click on the project name in the new project's Solution Explorer in the IDE
- Navigate to the old project's folder

It is between these two steps that the "Choose 'Add Existing Item' from the menu" would be useful here. I was trying to follow the directions, not realizing that one of the key steps is the title of the box.

* In the third line in the box on the bottom of the page, change this:
right-click on the project name in the new project?s Solution Explorer in the IDE, navigate to ...
to this:
right-click on the project name in the new project?s Solution Explorer in the IDE, select ?Add Existing Item? from the menu, navigate to ...

The error is in the illustration of the Queen object and two workers. The first worker object is labeled 'NectarCollan object' and the second one is labeled 'NectalCollar object'. Presumably both labels should say 'NectarCollector object'.

Change this: ?So if you want your interface to require a field with a certain name and type, just use a property instead ? it?ll accomplish the same thing.?
To this: ?So if you?ve got a problem that looks like it might be solved by adding a field to an interface, try using a property instead ? the odds are that it?ll do what you?re looking for.?

Q: I still don't quite get how interfaces improve the beehive code. You'll still need to add a NectarStinger class, and it'll still have duplicate code... right?

A: Interfaces aren't about preventing you from duplicating code. They're about letting you use one class in more than one situation. The goal is to create one worker bee class that can do two different jobs. You'll still need to create classes for them -- that's not the point. The point of the interfaces is that now you've got a way to have a class that does any number of jobs. Let's say you have a PatrolTheHive() method that takes a StingPatrol object and a CollectNectar() method that takes a NectarCollector object. But you don't want StingPatrol to inherit from NectarCollector or vice versa -- each class has public methods and properties that the other one shouldn't have. Now take a minute and try to think of a way to create one single class whose instances could be passed to both methods. Seriously, put the book down, take a minute and try to think up a way! How do you do it?

Interfaces fix that problem. Now you can have create an IStingPatrol reference which -- and that reference can point to any object that implements IStingPatrol, no matter what the actual class is. It can point to a StingPatrol, or a NectarStinger, or even a totally unrelated object. If you've got an IStingPatrol reference pointing to an object, then you know you can use all of the methods and properties that are part of the IStingPatrol interface, regardless of the actual type of the object.

But the interface is only part of the solution. You'll still need to create a new class that implements the interface, because it doesn't actually come with any code. Interfaces aren't about avoiding the creation of extra classes or avoiding duplicate code. They're about making one class that can do more than one job without relying on inheritance, because inheritance brings along a lot of extra baggage -- you'll have to inherit every method, property and field, not just the ones that have to do with the specific job.

Can you think of ways that you could still avoid duplicating code while using an interface? You could create a separate class called Stinger or Proboscis to contain the code that's specific to stinging or collecting nectar. NectarStinger and NectarCollector could both create a private instance of Proboscis, and any time they need to collect nectar, they'd call its methods and set its properties.

Change "Update your button so that the object initializer sets the FunnyThingIHave property, and the button calls"
to "Update your button so that it calls"

The second "accessor" is misspelled "accssor".

The two code blocks should be in the same font -- reduce the font size for the top code block so it matches the bottom one.

"the FunnyThingIHave set accessor should return"

"set" should be "get"

Note from the Author or Editor:
In the first bullet for step #3, change "set" to "get" in the last sentence:

The FunnyThingIHave get accessor should return the same thing.

In the second bullet, change the second sentence to:
You can?t mark a class private?unless that class lives inside another class, in which case it?s only available to instances of its container class. Then it?s private by default, and if you want it to be public you need to mark it public..

Add the following sentence to the end of the fourth bullet: ?You can combine this with protected ? anything you mark protected internal can only be accessed from within the assembly or from a subclass.
Add an annotation underneath the bottom bullet: ?Sealed is a modifier, but it?s not an access modifier. That?s because it only affects inheritance ? it doesn?t change the way class can be accessed.?

- Turn this into a 1-2-3 spread (like pages 258-259)? There will be a (1) above "public interface IClown {", a (2) above "public class FunnyFunny : IClown {", a (3) on page 275 above "public class ScaryScary : ...", and a (4) above "private void button1_C

Add a sentence to the end of the answer, right after "store data by itself.":
A property is a way to make something that looks like a field to other objects, but since it's really a method it doesn't actually store any data.

Change the headline to: "Like we said, some classes should never be instantiated"

The third and fourth sentences of the paragraph don't fit with the rest of the paragraph. These sentences say, "So let's implement it! Once we do, the error will go away." These sentences are repeated in what I think is their correct place about 3/4 of the way down the page, after a screen shot of an error message.

So let's implement it! Once we do, the error will go away. Any time you extend an abstract class, you need to make sure that you override all of its abstract methods. Luckily, the IDE makes this job easier. Just type "public override" -- as soon as you press space, the IDE will display a drop-down box with a list of any methods that you can override. Select the SetMissionInfo method and fill it in:

Change "is just like an interface" to "is just like what you'd see in an interface"

Interface says "And that's just plan rude" - plan should be plain.

Interface says "And that's just plan rude" - plan should be plain.

Change "check it off the list" to "check it off the following list"

(that'll be passed in by form)
should be
(that'll be passed in by the form)

Remove "0," from a line of code
Change this: int rand = random.Next(0, myLocation.Exits.Length);
to this: int rand = random.Next(myLocation.Exits.Length);

Change: This shows "30", 10 * 3.
to this: since Fetch has an index of 10, this statement sets score to 30.

In the first answer, change ?What you saw was a constructor? to ?What you saw was a method?

Change "and limit the type" to "which limits its members to that type"

Change "to build your own sorting logic" to "to build a separate class to help the List sort out its members"

Change "box underneath it, when you" to "box underneath it. When you"

The annotation should point to "dic-tion-ar-y" and not the text underneath it.

Change "The first item" to "These represent types. The first type"

change "obects" to "objects"

// Ask the other players for a value. first
should be:
// Ask the other players for a value. First

Page 350, under the Deal() method, currently reads:
"call each player's PullOutBooks() method."

It should read:
"call the Game class's PullOutBooks() method, described beneath."

Note from the Author or Editor:
About halfway down the page, change this line:

// foreach loop to call each player?s PullOutBooks() method.

to this

// foreach loop to call the PullOutBooks() method for each player.

The text in my book says: "...Set the BackColor Poperty of each to Color.Transparent (If you use the Properties window to set the property, just type it into the BackColor row)"

When I type "Color.Transparent" into the BackColor row, I get the following error from Visual Studio 2008 Express SP1: "Color.Transparent is not a valid value for Int32."

It seems to work as expected if I leave out "Color.", and just type "Transparent".

Note from the Author or Editor:
In the second edition, this is on page 189. In the upper right-hand corner annotation, second line, change "to Color.Transparent" to "to Transparent".

Add an annotation that points to this line of code: "if (Nearby(enemy.Location, target, radius)) {"
it should say: "The Nearby() method in the Mover class only takes two parameters, a Point and an int, and it compares the Point to the Mover field location. You'll need to add an overloaded Nearby() that's almost identical, except that it takes three parameters, two Points and a distance, which compares the first Point to the second Point (instead of location)."

Check use the Game ....
should be
Check the Game...

5th Point Text;
Text is identical to 1st point text on previous page, and should clearly not be.
In step 4, change the first few words to: check the Game object?s
In step 5, change the body text to this:
The rest of the method does three things. First it checks to see if the player?s already picked up the weapon in the room, so it knows whether or not to display it. Then it checks to see if the player died. And finally, it checks to see if the player?s defeated all of the enemies. If he has, then the player advances to the next level.

change "and add way" to "and add a way"

third paragraph, second to last last line:

change "user-friendly ending -- maybe" to "user-friendly ending? Maybe you can"

Move the underline so that it's under "am"

Page 398, third comment;

"The initialDirectory propery" should be "The initialDirectory property"

Page 399;

The second comment on the left hand side of the page says "..and opens the folder specified in the InitialFolder property". But there is no InitialFolder in the code, there's an InitialDirectory.

Note from the Author or Editor:
(398) middle annotation;
propery should be property

(399) The second comment on the left hand side of the page says "..and opens the folder specified in the InitialFolder property". But there is no InitialFolder in the code, there's an InitialDirectory.

In the bottom left-hand annotation, change InitialFolder to InitialDirectory.

propery should be property

Change "An OpenFileDialog box object" to "An OpenFileDialog object"

In the bottom left-hand annotation, change InitialFolder to InitialDirectory.

Change "the Log stream, so the Dispose()" to "pointed to by sw -- which was declared in the using statement, so the Dispose()"

Change the leftmost annotation from this:
Every case must end with ?break;?.
To this:
Every case ends with ?break;? so C# knows where one case ends and the next begins. (You can also end a case with ?return? ? the program will compile as long as there?s no way for one case to ?fall through? to the next one.)

"you can go back to fhe file....."
should be
"you can go back to the file...."

List<Passangers>object
should be
List<Passengers>object

In the curved text under the bottom circle in the box, change ?List<Passangers> object? to ?List<Passengers> object?.

Add an annotation pointing to [Serializable]: You need to add this attribute to the top of any class in order to serialize it.

The arrow for this annotation is slightly misaligned -- it needs to point to "(Deck)"

Make "unicode" uppercase - "Unicode"

You forgot to tell us the 4th Hebrew letter, U+05E9, as you're telling us what to choose on the character map. You only mention it as an afterthought at the bottom of the page.

Note from the Author or Editor:
In the first line of text for step #3, change this:

"double-click on the Shin character"

to this"

"double-click on the Shin character, which has the code U+05E9"

change:
then paste the letters over "Eureka!" so it looks like this:
to:
then paste the letters over "Eureka!" and add the Encoding.Unicode parameter, so it looks like this:

Add an annotation pointing to ?ReadBlock()? in the top paragraph:
The reason the method?s called ?ReadBlock()? is that when you call it, it ?blocks? (which means it keeps executing and doesn?t return to your program) until it?s either read all the characters you asked for or run out of data to read.

Add an annotation (without an arrow) to the space in the bottom left-hand corner:
The hex dumper works just fine for text files. But there?s a problem. Use File.WriteAllBytes() to write an array of bytes with values over 127 to a file and then run it through your dumper. Uh-oh ? they?re all read in as ?fd?! That?s because StreamReader is built to read text files, which only contain bytes with values under 128. Here?s a bonus exercise: See if you can figure out how to use the BinaryReader class to fix the problem!

change "add a third parameter" to "change the third parameter"

In the sidebar in the lower-right corner, change the text ?using two bytes each.? to ?using two or more bytes each.?
Add an annotation at the bottom of the page pointing to the sidebar: ?This encoding is called UTF-8, which .NET uses by default. You can tell File.WriteAllText() to use a different encoding by passing it a different Encoding object. You can learn more about Unicode encodings at http://unicode.org.?

In the title bar of the third class box on the bottom, change ?OverFlowException? to ?OverflowException?

The text states:
"The Exception class has a couple of useful members. The Message properties stores an easy-to-read
message..." It should be: "... The Message property ..." as there's only one of them.
In the first line of the second paragraph, change ?Message properties? to ?Message property?.

"Whenever you program throws an exception, the runtime environment will search through
your code looking for a catch block to that matches it."
Either that "to " should not be there or it should say "... to match it".
In the second answer (the top two lines of the second column), change:
for a catch block to that matches it
to:
for a catch block that matches it

The "EX" label on the Exception object should have a white text background, not transparent, so it looks white and not grey

There should be no line break between "new" and "YourClass();"

change "You'll often see one using statement inside of another."
to "You'll see nested using statements like this when you need to declare two IDisposable references in the same block of code."

the arrow is pointing to an underscore that's misaligned -- it should be under "Log"

Surely the underline is misplaced and should be under "must", not over it?

Third paragraph, second sentence;
The text states:
"First, let's use a built-in object that implements IDisposable, Stream."
Change to:
"First, let's use built-in object Stream, which implements IDisposable."

change "Take a look at the DivisorCalculator"
to "Take a look at this Calculator class"

The note states:
"The umpire checks every ball ... and monitor what happens."
This should be "... umpires check ..." or "... monitors ...".
In the last line of the annotation pointing to the Umpire object, change ?monitor? to ?monitors?

There is inconsistent use of singular/plural in the last paragraph:

"... So you write code to raise an event, and then you write code to handle those events ... Then,
whenever an event is raised, your handlers kick into action."

To be consistent, this should be:

"... you write code to raise an event, and ... write code to handle that event" and "... your
handler kicks into action."

In the last paragraph on the page, change ?your handlers kick? to ?your handler kicks?

change this annotation to: Here's what each object that handles the event gets to work with. It also gets a reference to the object that raised the event.

Add another sentence to the end of this annotation: sender is a reference to the object that raised the event, and e is a reference to an EventArgs object.

remove the word "pre-made" from the second line of the annotation

messagebox.show should say "You just clicked on the form"

first annotation;
"You can see all of the events for a control by click on it..."

should be

"...clicking on it...."

The text for note 1 states:

"You can see all of the [pre-made] events for a control by click on it and then click on this
events button in the properities window."

"pre-made" has already been deleted in an earlier update.

The English is a bit strained, but the simplest way to fix it is to change the "click"s to
"clicking"s.

It would also be sensible to correct the spelling and Capitalization of "properities window" to
"Properties window" while you're at it.

In the top right annotation, change ?You can see all of the events for a control by click on it?
To ?You can see all of the events for a control: just click on it?

Add an annotation pointing to the code under step 6:

"When you click these buttons, they chain different event handlers onto the form's Click event."

Then add an annotation under it, pointing up at it:

"That means you won't see anything when you click the buttons! You'll need to click on the form, because the buttons change the form's behavior by modifying its Click event."

in the line:

"this.Load += new EventHandler(Minivan);"

"Load" is already highlighted in the solution but "Minivan" is not. As "Minivan" is one of the items
that had to be added from the Pool, it should also be highlighted.

By the way, "Van", "Car", and "Tricycle" are possible alternative names for the "Minivan" event handler.
There's nothing to prevent them being used in the Pool Puzzle, provided whichever name is chosen is used
in both the Form1() constructor and for the 4th event handler. Perhaps "Tricycle" should be replaced by
"Bicycle", and "Van" or "Car" replaced by "Towtruck". The third of these could be removed from the Pool
as it isn't really necessary, except as a source of confusion.

In the pool puzzle on page 504, change the third line of code from this:

this.______ += new EventHandler(____________);

to this:

this.______ += new EventHandler(Minivan);

Change "You chain several" to "You can chain several"

The last word of the last sentence is cut off -- add the word "constructor."

The last note states:
"The first one you'll learn about is called the "Publisher-Subscriber" pattern."
I started reading HFDP before HFC#... and actually, it's called the "Observer" pattern!
In the bottom right-hand annotation, change this:
the ?Publisher-Subscriber? pattern,
To this:
the ?Observer? (or ?Publisher-Subscriber?) pattern,

The fifth sentence states:

"So if you mark an event private, then other instances if the same class can subscribe to it."

That "... if the same class" should be "... of the same class".

Add an annotation at the bottom of the page pointing up at the bottom paragraph:
Since this simulator will be animated, we'll be drawing it frame by frame. We'll use the words "frame," "cycle," and "turn" interchangeably.

Remove the asterisk from the beginning of the annotation. Change "We used" to "You'll use".

The note states:
"*Hint: We used NectarGatheredPerTurn, nectar, and NectarHarvested in this method, but nothing else."
The variable for the flower's nectar is called "Nectar" (on p520).
I'm wondering whether the list style "first, second, and third" has been used previously in this book. I
would have thought it should be "first, second and third" - i.e. no final comma - but maybe that's just
me!
In second line of the annotation under step 4, capitalize ?Nectar?

Change "its" to "it's"

In Step 1, the skeleton code for the Hive class states "... locations should be private, ...".
Step 3 says the GetLocation() method should "look up that string in the Locations dictionary, ...".
I think "Locations" should be treated as a variable name - in other words with correct (lower) case and
in fixed-width font.
In the second line of step 3, change ?Locations? to ?locations? and put it in the Courier code font

The annotations and their arrows are misaligned. They need to be shifted down.

Change "hive and world in the constructor" to "hive and world as parameters to its constructor"

Change "The World class keeps up with all the bees" to "The World class uses a List of Bee objects to keep track of all the bees"

Change "Point object" to "Point"

Add this after the first sentence: "Plus, it'll come in handy when we do the animation."

"No reason reinvent the wheel..."
should be
"No reason to reinvent the wheel..."

Sentence 2 starts:
"However, just becase .NET uses them that way, ..."
That should be "... because ...".
In the third line of the last answer, change ?becase? to ?because?

The annotations are overlapping the box

Change "dropdown that appears on the form" to "dropdown that appears on the ToolStrip when you're in the form designer"

Change "Use the dropdown" to "Use the dropdown that appears on the StatusStrip in the designer"

Add a new annotation above this one with an arrow pointing down at it. It should say:
The labels in the right-hand column will show the stats. Name them "Bees", "Flowers", "HoneyInHive", etc.

Add the "Behind the Scenes" picture (like on p576) to the upper right-hand corner of the page.

In the second-to-last line of the ?DateTime & TimeSpan? box, change ?obect? to ?object?

Add another annotation underneath the first one that says: "Just double-click on a ToolStrip button in the designer to make the IDE add its event handler, just like a normal button."

In the second line of body text, change Langauge to Language

move the arrow from the second-to-last annotation a little to the right ? it?s overlapping the code.

The annotation is pointing to an underline, but the underline is misaligned--it needs to be moved up

Change "great simulator" to "cool simulator"

Change "We'll add a Print button to the stats window" to "We'll make the Print button in the stats window work"

Change the two sentences underneath that to:

"The stats window has working Open and Save buttons, but the Print button doesn't work yet. We'll be able to reuse a lot of the graphics code to get the Print button on the ToolStrip to print an info page about what's going on.

Add an annotation pointing to the screenshot that says: "Double-click on Resources.resx to bring up the Resources page."

add an annotation pointing to the line of code under step 3 that says: "When the program's running, each picture is stored in memory as a Bitmap object."

change "and and" to "add and"

Change "you see in the form's Properties window" to "you see in the Properties window for any control"

Bullet point 3 is repeated
Replace the three lines of the body text under step 3 with this (?animationTimer.Dispose()? should be in Courier code font):
Change the new Dispose() method that the IDE added for you so that it calls animationTimer.Dispose().

change "inside hive picture." to "inside hive picture, and its BackgroundImageLayout property to Stretch."

"...other class needs to update to any..."
should be
"...other class needs to update any..."
In the fourth line of the upper right-hand annotation, change ?to any of its properties? to ?any of its properties?.

change "an array of four of them" to "in this case, an array of four of them"

Add an annotation pointing at this code that says: "These lines take each of the Bitmap objects that store the bee pictures and shrink them down using the ResizeImage() method we wrote."

Change "trickier..." to "slower..."

change "programmatically" to "in code"

change "got CreateGraphics() method" to "got a CreateGraphics() method"

change "When a class implements IDisposable, any time you instantiate it you should call its dispose() method."
to "When you instantiate a class that implements IDisposable, you should always call its Dispose() method when you're done with the object. That way it knows to clean up after itself."

Remove the last sentence ("You'll see more about that in just a minute.")

change "most amateur computer games..." to "some amateur computer games, for example."

Add an annotation pointing to "DrawBee" that says: "We'll reuse our DrawBee() method from a few pages ago."

Replace this annotation with: "Don't worry about drawing the Clone and List objects -- just add the objects for the Captain, the Swindler, the clone factory and Swindler's escape plane."

indent the "clones.Remove(clone);" line by three spaces

Change the fifth paragraph from this:
Finally, .NET sends the garbage collector out again. This time, your object is dead, and the collector tosses it away. Here, finally, your destructor runs... possibly several minutes after the last reference to the object was removed or changed.
To this:
Finally, .NET sends the garbage collector out again. Your destructor runs... possibly several minutes after the last reference to the object was removed or changed. Now that it?s been finalized, your object is dead, and the collector tosses it away.

change this annotation to: "The Clone will create the C:Temp directory and serialize itself out to a file called Clone.dat."

change this annotation to: "We hardcoded the filename -- we included them as string literals in the code. That's fine for a small demo program like this, but it's not the most robust design. Can you think of problems this might cause, and how you could avoid them?"

In the first question, fourth line, change this:
?may have already been collected.?
To this:
?may have already been finalized.?

Add an annotation pointing to the second paragraph of body text in the middle of the page:
?All structs inherit from System.ValueType, which in turn inherits from System.Object. That?s why every struct has a ToString() method ? it gets it from Object. But that?s all the inheriting that structs are allowed to do.?

In the sidebar, change this:
?Structs are best used for storing data, but are not as useful as objects when it comes to representing actual behavior.?
To this
?Structs are best used for storing data, but the lack of inheritance and the way they?re managed in memory can be a serious limitation.?
Add an annotation pointing to this sentence: ?That?s why you don?t usually find yourself defining your own structs. But that doesn?t mean they don?t have their uses!?

In the second line of body text, change ?string? to ?decimal?.
Change the second line of code under the first bullet from this: string name = ?Fingers?;
to this: bool Scary = true;
And in annotation pointing to that line of code, change this: ?int and bool?
To this: ?int and bool?

Next to step 1, add this annotation (no arrow):
Remember back in the beginning of the book when we said that methods and statements ALWAYS live in classes? Well, it turns out that's not quite exactly 100% accurate -- they can also live in structs.

Add an annotation on page 642 pointing to step #2: ?There?s a special case where value types don?t get boxed: if they live inside an object. If you?ve got a class with an int field, that int doesn?t need to be boxed before it?s added to the heap, because it?s already got a container ? the object that it?s a part of.?

Add an annotation pointing to the word "sealed" in the first line that says: "Remember the sealed access modifier from Chapter 7? It's how you set up a class that can't be extended."

Change these sentences to: "If you can extend the class, then you'll usually end up doing that -- extension methods aren't meant to be a replacement for inheritance. But they come in really handy when you've got classes that you can't extend."

Add this to the end of the first paragraph: "Create a new project, and add a file called MyExtensions.cs."

change "Add using Emergency; to your code." to "Now go to your form code and add using MyExtensions; to the top, and add a button to the form so you can try out your new extension method inside its event handler."

Change "All of the Objectville" to "All of the Objectville Paper Company"

change "Objectville paper" to "Objectville Paper Company data"

We gave you Ready Backe Code for the LINQ query in Chapter 12. We'll see exactly how it works in a few pages.

Put the two lines of code in boldface

change "Jim" to "Jimmy"

Change "It's easy to mine Jimmy's data" to "Jimmy could analyze his comic book data"

Whoops, sorry, sent that before I'd overtyped the new description!

The annotation states:
This first LINQ query divides the Line objects in the line[] array into two groups, grouped by their Value, ...

Surely there are three groups, with Value = 1, 2 and 3? We actually want only the first two, but that hasn't happened yet.

Note from the Author or Editor:
In the second line of the top annotation, change 'into two groups' to 'into groups'

Whoops, sorry, sent that before I'd overtyped the new description!

The annotation states:
This first LINQ query divides the Line objects in the line[] array into two groups, grouped by their Value, ...

Surely there are three groups, with Value = 1, 2 and 3? We actually want only the first two, but that hasn't happened yet.

In the second line of the top annotation, change ?into two groups? to ?into groups?

change "class with two fields" to "class with two automatic properties"

The annotation, second sentence states:

"When you use an object initializer, you create an anonymous by typing a series of names and values inside curly brackets."

It should say something like "... you create an anonymous object..." or "an anonymous type object", though the latter is not so good.

Note from the Author or Editor:
In third line of the bottom left-hand annotation, change 'you create an anonymous' to 'you create an anonymous object'

The annotation, second sentence states:

"When you use an object initializer, you create an anonymous by typing a series of names and values inside curly brackets."

It should say something like "... you create an anonymous object..." or "an anonymous type object", though the latter is not so good.

In third line of the bottom left-hand annotation, change ?you create an anonymous? to ?you create an anonymous object?

The answer starts:-

"Yes, you do have to create them. LINQ object that implements the IEnumerable interface."

This doesn't make sense. The first sentence could say just:-

"Yes, you do."

"have to add them" would match the terminology of the question.

That second sentence could state:-

"LINQ can only be used with objects that implement the IEnumerable interface."

or, slightly shorter but perhaps not so clear:-

"LINQ objects must implement the IEnumerable interface."

though that runs better into the following explanation.

Also, para 2 sentence 2 says:-

"When you add it to your project, it automatically does everything..."

The first "it" should the "them" to match the LINQ to SQL classes (plural), while the second "it" refers to the IDE, so it would be clearer if it said "the IDE"! The following "it"s would then refer to the IDE again.

Note from the Author or Editor:
Change the first two sentences of the fourth answer to:

A: Yes, you do. LINQ needs an object that implements the IEnumerable interface.

In the second paragraph of the fourth answer, change 'it' to 'they' and match the number throughout:

That's why the IDE provides the LINQ to SQL classes for you. When you add them to your project, they automatically do everything you need in order to connect LINQ to a SQL database: they let you drag database
objects into its Object Relational Designer, and when you do they automatically read your database?s tables and create classes (like the People class) that LINQ can use to access them.

The answer starts:-
"Yes, you do have to create them. LINQ object that implements the IEnumerable interface."
This doesn't make sense. The first sentence could say just:-
"Yes, you do."
"have to add them" would match the terminology of the question.

That second sentence could state:-

"LINQ can only be used with objects that implement the IEnumerable interface."
or, slightly shorter but perhaps not so clear:-
"LINQ objects must implement the IEnumerable interface."
though that runs better into the following explanation.

Also, para 2 sentence 2 says:-
"When you add it to your project, it automatically does everything..."
The first "it" should the "them" to match the LINQ to SQL classes (plural), while the second "it" refers to the IDE, so it would be clearer if it said "the IDE"! The following "it"s would then refer to the IDE again.

Change the first two sentences of the fourth answer to:

A: Yes, you do. LINQ needs an object that implements the IEnumerable interface.

In the second paragraph of the fourth answer, change ?it? to ?they? and match the number throughout:

That?s why the IDE provides the LINQ to SQL classes for you. When you add them to your project, they automatically do everything you need in order to connect LINQ to a SQL database: they let you drag database
objects into its Object Relational Designer, and when you do they automatically read your database?s tables and create classes (like the People class) that LINQ can use to access them.

Change "there can only be two shots" to "there can only be two player shots"

change "all keypresses" to "which keys are currently being held down"

Change "The Stars keeps" to "The Stars object keeps"

change "Adjust the timer" to "Adjust the timers"

change "Refresh()" to "Invalidate()"

Add this sentence to the end of the paragraph: "You can start the game out in this state, so the user has to hit S to start a new game."

replace the whole paragraph with this text: So the form should have a Paint event handler (make sure you set the form's DoubleBuffered property to true!). You'll delegate the rest of the drawing to the Game object by calling its Draw() method every time the form's Paint event fires.

"Add add" s/b "Add"

Plus, it'll even figure out that it should create a static method, since it doesn't use any fields.

"applicaiton" s/b "application"

Missing period.

"application Just" s/b
"application. Just"

In the header and first line of body text change ?Windows Presentation Framework? to ?Windows Presentation Foundation?.

Index "argument"