O'Reilly logo

Head First C#, 3rd Edition by Andrew Stellman, Jennifer Greene

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

Chapter 4. Types and References: It’s 10:00. Do you know where your data is?

image with no caption

Data type, database, Lieutenant Commander Data... it’s all important stuff. Without data, your programs are useless. You need information from your users, and you use that to look up or produce new information to give back to them. In fact, almost everything you do in programming involves working with data in one way or another. In this chapter, you’ll learn the ins and outs of C#’s data types, see how to work with data in your program, and even figure out a few dirty secrets about objects (pssst...objects are data, too).

The variable’s type determines what kind of data it can store

image with no caption

There are a bunch of types built into C#, and each one stores a different kind of data. You’ve already seen some of the most common ones, and you know how to use them. But there are a few that you haven’t seen, and they can really come in handy, too.

Types you’ll use all the time

It shouldn’t come as a surprise that int, string, bool, and double are the most common types.

  • int can store any whole number from –2,147,483,648 to 2,147,483,647.


    A whole number doesn’t have a decimal point.

  • string can hold text of any length (including the empty string "").

  • bool is a Boolean value—it’s either true or false.

  • double can store real numbers from ±5.0 × 10–324 to ±1.7 × 10308 with up to 16 significant figures. That range looks weird and complicated, but it’s actually pretty simple. The “significant figures” part means the precision of the number: 35,048,410,000,000, 1,743,059, 14.43857, and 0.00004374155 all have seven significant figures. The 10308 thing means that you can store any number as large as 10308 (or 1 followed by 308 zeros)—as long as it only has 16 or fewer significant figures. On the other end of the range, 10–324 means that you can store any number as small as 10–324 (or a decimal point followed by 324 zeros followed by 1)...but, you guessed it, as long as it only has 16 or fewer significant figures.


    These numbers are called “floating-point”...as opposed to a “fixed point” number, which always has the same number of decimal places.

More types for whole numbers

Once upon a time, computer memory was really expensive, and processors were really slow. And, believe it or not, if you used the wrong type, it could seriously slow down your program. Luckily, times have changed, and most of the time if you need to store a whole number you can just use an int. But sometimes you really need something bigger...and once in a while, you need something smaller, too. That’s why C# gives you more options:


A lot of times, if you’re using these types it’s because you’re solving a problem where it really helps to have the “wrapping around” effect that you’ll read about in a few minutes.

  • byte can store any whole number between 0 and 255.

  • sbyte can store any whole number from –128 to 127.


    The “s” in sbyte stands for “signed,” which means it can be negative (the “sign” is a minus sign).

  • short can store any whole number from –32,768 to 32,767.

  • ushort can store any whole number from 0 to 65,535.

  • uint can store any whole number from 0 to 4,294,967,295.


    The “u” stands for “unsigned.”

  • long can store any whole number between minus and plus 9 billion billion.

  • ulong can store any whole number between 0 and about 18 billion billion.

Types for storing really HUGE and really tiny numbers

Sometimes seven significant figures just isn’t precise enough. And, believe it or not, sometimes 1038 isn’t big enough and 10–45 isn’t small enough. A lot of programs written for finance or scientific research run into these problems all the time, so C# gives us multiple types to handle floating-point values:

  • float can store any number from ±1.5 × 10–45 to ±3.4 × 1038 with 7 significant digits.


    double is a lot more common than float. Many XAML properties use double values.

  • double can store any number from ±5.0 × 10–324 to ±1.7 × 10308 with 15-16 significant digits.

  • decimal can store any number from ±1.0 × 10–28 to ±7.9 × 1028 with 28–29 significant digits.


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


    When you used the Value property in your numericUpDown control, you were using a decimal.

Literals have types, too


A “literal” just means a number that you type into your code. So when you type “int i = 5;”, the 5 is a literal.

When you type a number directly into your C# program, you’re using a literal...and every literal is automatically assigned a type. You can see this for yourself—just enter this line of code that assigns the literal 14.7 to an int variable:

int myInt = 14.7;

Now try to build the program. You’ll get this:

image with no caption

That’s the same error you’ll get if you try to set an int equal to a double variable. What the IDE is telling you is that the literal 14.7 has a type—it’s a double. You can change its type to a float by sticking an F on the end (14.7F). And 14.7M is a decimal.


If you try to assign a float literal to a double or a decimal literal to a float, the IDE will give you a helpful message reminding you to add the right suffix. Cool!


The “M” stands for “money”—seriously!

A few more useful built-in types

Sometimes you need to store a single character like Q or 7 or $, and when you do you’ll use the char type. Literal values for char are always inside single quotes ('x', '3'). You can include escape sequences in the quotes, too ('\n' is a line break, '\t' is a tab). You write an escape sequence in your C# code using two characters, but your program stores each escape sequence as a single character in memory.


You’ll learn a lot more about how char and byte relate to each other in Chapter 9.

And finally, there’s one more important type: object. You’ve already seen how you can create objects by creating instances of classes. Well, every one of those objects can be assigned to an object variable. You’ll learn all about how objects and variables that refer to objects work later in this chapter.

Brain Power

The Windows desktop calculator app has a really neat feature called “Programmer” mode, where you can see binary and decimal at the same time!

You can use the Windows desktop calculator to convert between decimal (normal, base-10) numbers and binary numbers (base-2 numbers written with only ones and zeros)—put it in Programmer mode, enter a number, and click the Bin radio button to convert to binary. Then click Dec to convert it back. Now enter some of the upper and lower limits for the whole number types (like –32,768 and 255) and convert them to binary. Can you figure out why C# gives you those particular limits?

Windows 8 has two different calculators, a Windows Store app and a desktop app. Use Search to find the desktop app, and use its “View” menu to switch between its modes.

A variable is like a data to-go cup

All of your data takes up space in memory. (Remember the heap from last chapter?) So part of your job is to think about how much space you’re going to need whenever you use a string or a number in your program. That’s one of the reasons you use variables. They let you set aside enough space in memory to store your data.


Not all data ends up on the heap. Value types usually keep their data in another part of memory called the stack. You’ll learn all about that in Chapter 14.

Think of a variable like a cup that you keep your data in. C# uses a bunch of different kinds of cups to hold different kinds of data. And just like the different sizes of cups at the coffee shop, there are different sizes of variables, too.

image with no caption

Numbers that have decimal places are stored differently than whole numbers. You can handle most of your numbers that have decimal places using float, the smallest data type that stores decimals. If you need to be more precise, use a double. And if you’re writing a financial application where you’ll be storing currency values, you’ll want to use the decimal type.

It’s not always about numbers, though. (You wouldn’t expect to get hot coffee in a plastic cup or cold coffee in a paper one.) The C# compiler also can handle characters and non-numeric types. The char type holds one character, and string is used for lots of characters “strung” together. There’s no set size for a string object, either. It expands to hold as much data as you need to store in it. The bool data type is used to store true or false values, like the ones you’ve used for your if statements.

image with no caption

10 pounds of data in a 5-pound bag

image with no caption

When you declare your variable as one type, that’s how your compiler looks at it. Even if the value is nowhere near the upper boundary of the type you’ve declared, the compiler will see the cup it’s in, not the number inside. So this won’t work:

int leaguesUnderTheSea = 20000;

short smallerLeagues = leaguesUnderTheSea;

20,000 would fit into a short, no problem. But since leaguesUnderTheSea is declared as an int, the compiler sees it as int-sized and considers it too big to put in a short container. The compiler won’t make those translations for you on the fly. You need to make sure that you’re using the right type for the data you’re working with.

image with no caption

Even when a number is the right size, you can’t just assign it to any variable

Let’s see what happens when you try to assign a decimal value to an int variable.

Do this

  • ➊ Create a new Windows Forms project and add a button to it. Then add these lines to the button’s Click() method:

    decimal myDecimalValue = 10;
    int myIntValue = myDecimalValue;
    MessageBox.Show("The myIntValue is " + myIntValue);
  • ➋ Try building your program. Uh oh—you got an error that looks like this:

    image with no caption
  • ➌ Make the error go away by casting the decimal to an int. Once you change the second line so it looks like this, your program will compile and run:

    image with no caption

So what happened?

The compiler won’t let you assign a value to a variable if it’s the wrong type—even if that variable can hold the value just fine—because that’s the underlying cause behind an enormous number of bugs, and the compiler is helping by nudging you in the right direction. When you use casting, you’re essentially making a promise to the compiler that you know the types are different, and that in this particular instance it’s OK for C# to cram the data into the new variable.


Take a minute to flip back to the beginning of the last chapter and check out how you used casting when you passed the NumericUpDown. Value to the Talker Tester form.

You can read more about the value types in C# here: http://msdn.microsoft.com/en-us/library/s1ax56ch.aspx

When you cast a value that’s too big, C# will adjust it automatically

Wrap it yourself!

There’s no mystery to how casting “wraps” the numbers—you can do it yourself. Just pop up the Windows desktop calculator, switch it to Scientific mode, and calculate 365 Mod 256 (using the Mod button, which does a modulo calculation). You’ll get 109.

You’ve already seen that a decimal can be cast to an int. It turns out that any number can be cast to any other number. But that doesn’t mean the value stays intact through the casting. If you cast an int variable that’s set to 365 to a byte variable, 365 is too big for the byte. But instead of giving you an error, the value will just wrap around: for example, 256 cast to a byte will have a value of 0. 257 would be converted to 1, 258 to 2, etc., up to 365, which will end up being 109. And once you get back to 255 again, the conversion value “wraps” back to zero.

image with no caption

Yes! The + operator converts for you.

What you’ve been doing is using the + operator, which does a lot of converting for you automatically—but it’s especially smart about it. When you use + to add a number or Boolean to a string, then it’ll automatically convert that value to a string, too. If you use + (or *, /, or -) with two different types, it automatically converts the smaller type to the bigger one. Here’s an example:

image with no caption

Since an int can fit into a float but a float can’t fit into an int, the + operator converts myInt to a float before adding it to myFloat.

C# does some casting automatically

There are two important conversions that don’t require you to do the casting. The first is done automatically any time you use arithmetic operators, like in this example:

image with no caption

The other way C# converts types for you automatically is when you use the + operator to concatenate strings (which just means sticking one string on the end of another, like you’ve been doing with message boxes). When you use + to concatenate a string with something that’s another type, it automatically converts the numbers to strings for you. Here’s an example. The first two lines are fine, but the third one won’t compile.

long x = 139401930;

MessageBox.Show("The answer is " + x);


The C# compiler spits out an error that mentions something about invalid arguments (an argument is what C# calls the value that you’re passing into a method’s parameter). That’s because the parameter for MessageBox.Show() is a string, and this code passed a long, which is the wrong type for the method. But you can convert it to a string really easily by calling its ToString() method. That method is a member of every value type and object. (All of the classes you build yourself have a ToString() method that returns the class name.) That’s how you can convert x to something that MessageBox.Show() can use:


When you call a method, the arguments must be compatible with the types of the parameters


A parameter is what you define in your method. An argument is what you pass to it. A method with an int parameter can take a byte argument.

Try calling MessageBox.Show(123)—passing MessageBox.Show() a literal (123) instead of a string. The IDE won’t let you build your program. Instead, it’ll show you an error in the IDE: “Argument ‘1’: cannot convert from ‘int’ to ‘string’.” 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.

But MessageBox.Show() isn’t the only method that will give you compiler errors if you try to pass it a variable whose type doesn’t match the parameter. All methods will do that, even the ones you write yourself. Go ahead and try typing this completely valid method into a class:

image with no caption

It works just fine if you pass it what it expects (a bool)—call MyMethod(true) or MyMethod(false), and it compiles just fine.

But what happens if you pass it an integer or a string instead? The IDE gives you a similar error to the one that you got when you passed 123 to MessageBox.Show(). Now try passing it a Boolean, but assigning the return value to a string or passing it on to MessageBox.Show(). That won’t work, either—the method returns an int, not a long or the string that MessageBox.Show() expects.


You can assign anything to a variable, parameter, or field with the type object.

When the compiler gives you an “invalid arguments” error, it means that you tried to call a method with variables whose types didn’t match the method’s parameters.

if statements always test to see if something’s true

You did this in the code you wrote in “Save the Humans”—go back and have a look; see if you can spot it.

Did you notice how we wrote our if statement like this:

if (yesNo) {

We didn’t have to explicitly say “if (yesNo == true)”. That’s because an if statement always checks if something’s true. You check if something’s false using ! (an exclamation point, or the NOT operator). “if (!yesNo)” is the same thing as “if (yesNo == false)”. In our code examples from now on, you’ll usually just see us do “if (yesNo)” or “if (!yesNo)”, and not explicitly check to see if a Boolean is true or false.

Answers in Exercise Solution.

Debug the mileage calculator

There’s something wrong with the mileage calculator. Whenever your code doesn’t work the way you expect it to, there’s always a reason for it, and your job is to figure out what that reason is. Let’s figure out what went wrong here and see if we can fix it.

Do this


    Let’s track down that problem by adding a button to your form that shows the value of the milesTraveled field. (You could also use the debugger for this!)

    image with no caption

    When you’re done with the form, double-click on the Display Miles button to add some code to the project.


    All we need to do is get the form to display the milesTraveled variable, right? So this line should do that:

    private void button2_Click(object sender, EventArgs e) {
           MessageBox.Show(milesTraveled + " miles", "Miles Traveled");
  • RUN IT.

    Type in some values and see what happens. First enter a starting mileage and ending mileage, and click the Calculate button. Then click the Display Miles button to see what’s stored in the milesTraveled field.

    image with no caption

    No matter what numbers you use, the number of miles always matches the amount owed. Why?

Combining = with an operator

Take a good look at the operator we used to subtract ending mileage from starting mileage (-=). The problem is it doesn’t just subtract, it also assigns a value to the variable on the left side of the subtraction sign. The same thing happens in the line where we multiply the number of miles traveled by the reimbursement rate. We should replace the -= and the *= with just - and *:

image with no caption

So can good variable names help you out here? Definitely! Take a close look at what each variable is supposed to do. You already get a lot of clues from the name milesTraveled—you know that’s the variable that the form is displaying incorrectly, and you’ve got a good idea of how that value ought to be calculated. So you can take advantage of that when you’re looking through your code to try to track down the bug. It’d be a whole lot harder to find the problem if the incorrect lines looked like this instead:

image with no caption

Objects use variables, too

So far, we’ve looked at objects separate from other types. But an object is just another data type. Your code treats objects exactly like it treats numbers, strings, and Booleans. It uses variables to work with them:

Using an int

  • ➊ Write a statement to declare the integer.

    int myInt;
  • ➋ Assign a value to the new variable.

    myInt = 3761;
  • ➌ Use the integer in your code.

    while (i < myInt) {

Using an object

  • ➊ Write a statement to declare the object.

    image with no caption
  • ➋ Assign a value to the object.

    spot = new Dog();
  • ➌ Check one of the object’s fields.

    while (spot.IsHappy) {
image with no caption

Objects are just one more type of variable your program can use.

If your program needs to work with a whole number that’s really big, use a long. If it needs a whole number that’s small, use a short. If it needs a yes/no value, use a boolean. And if it needs something that barks and sits, use a Dog. No matter what type of data your program needs to work with, it’ll use a variable.

Refer to your objects with reference variables

When you create a new object, you use code like new Guy(). But that’s not enough; even though that code creates a new Guy object on the heap, it doesn’t give you a way to access that object. You need a reference to the object. So you create a reference variable: a variable of type Guy with a name, like joe. So joe is a reference to the new Guy object you created. Any time you want to use that particular guy, you can reference it with the reference variable called joe.


That’s called instantiating the object.

So when you have a variable that is an object type, it’s a reference variable: a reference to a particular object. Take a look:

image with no caption

References are like labels for your object

In your kitchen, you probably have containers of salt and sugar. If you switched their labels, it would make for a pretty disgusting meal—even though the labels changed, the contents of the containers stayed the same. References are like labels. You can move labels around and point them at different things, but it’s the object that dictates what methods and data are available, not the reference itself.

image with no caption

When your code needs to work with an object in memory, it uses a reference, which is a variable whose type is a class of the object it’s going to point to. A reference is like a label that your code uses to talk about a specific object.

You never refer to your object directly. For example, you can’t write code like Guy.GiveCash() if Guy is your object type. The C# compiler doesn’t know which Guy you’re talking about, since you might have several instances of Guy on the heap. So you need a reference variable, like joe, that you assign to a specific instance, like Guy joe = new Guy().

Now you can call (non-static) methods like joe.GiveCash(). joe refers to a specific instance of the Guy class, and your C# compiler knows exactly which instance to use. And, as you saw above, you might have multiple labels pointing to the same instance. So you could say Guy dad = joe, and then call dad.GiveCash(). That’s OK, too—that’s what Joe’s kid does every day.

If there aren’t any more references, your object gets garbage-collected

If all of the labels come off of an object, programs can no longer access that object. That means C# can mark the object for garbage collection. That’s when C# gets rid of any unreferenced objects, and reclaims the memory those objects took up for your program’s use.

  • Here’s some code that creates an object.

    Guy joe = new Guy()
     { Name = "Joe", Cash = 50 };
    image with no caption
  • Now let’s create a second object.

    Guy bob = new Guy()
     { Name = "Bob", Cash = 75 };
    image with no caption
  • Let’s take the reference to the first object, and change it to point at the second object.

    image with no caption

For an object to stay in the heap, it has to be referenced. Some time after the last reference to the object disappears, so does the object.

Multiple references and their side effects

You’ve got to be careful when you start moving around reference variables. Lots of times, it might seem like you’re simply pointing a variable to a different object. But you could end up removing all references to another object in the process. That’s not a bad thing, but it may not be what you intended. Take a look:

  • Dog rover = new Dog();
    rover.Breed = "Greyhound";



    image with no caption
  • Dog fido = new Dog();
    fido.Breed = "Beagle";
    Dog spot = rover;



    image with no caption
  • Dog lucky = new Dog();
    lucky.Breed = "Dachshund";
    fido = rover;



    image with no caption

Brain Power

Why do you think we didn’t add a Swap() method to the Elephant class?

Two references means TWO ways to change an object’s data

Besides losing all the references to an object, when you have multiple references to an object, you can unintentionally change an object. In other words, one reference to an object may change that object, while another reference to that object has no idea that something has changed. Watch:

Do this

  • ➊ Add another button to your form.

    image with no caption
  • ➋ Add this code for the button. Can you guess what’s going to happen when you click it?

    image with no caption
  • ➌ OK, go ahead and click the new button. Wait a second, that’s the Lucinda message box. Didn’t we call the WhoAmI() method from Lloyd?

    image with no caption

A special case: arrays

If you have to keep track of a lot of data of the same type, like a list of heights or a group of dogs, you can do it in an array. What makes an array special is that it’s a group of variables that’s treated as one object. An array gives you a way of storing and changing more than one piece of data without having to keep track of each variable individually. When you create an array, you declare it just like any other variable, with a name and a type:

Strings and arrays are different from the other data types you’ve seen so far, because they’re the only ones without a set size (think about that for a bit).

image with no caption

Use each element in an array like it is a normal variable

When you use an array, first you need to declare a reference variable that points to the array. Then you need to create the array object using the new statement, specifying how big you want the array to be. Then you can set the elements in the array. Here’s an example of code that declares and fills up an array—and what’s happening on the heap when you do it. The first element in the array has an index of zero.

image with no caption

Arrays can contain a bunch of reference variables, too

You can create an array of object references just like you create an array of numbers or strings. Arrays don’t care what type of variable they store; it’s up to you. So you can have an array of ints, or an array of Duck objects, with no problem.

Here’s code that creates an array of seven Dog variables. The line that initializes the array only creates reference variables. Since there are only two new Dog() lines, only two actual instances of the Dog class are created.

image with no caption

When you set or retrieve an element from an array, the number inside the brackets is called the index. The first element in the array has an index of zero.

An array’s length

You can find out how many elements are in an array using its Length property. So if you’ve got an array called heights, then you can use heights. Length to find out how long it is. If there are seven elements in the array, that’ll give you 7—which means the array elements are numbered 0 to 6.

Welcome to Sloppy Joe’s Budget House o’ Discount Sandwiches!

Sloppy Joe has a pile of meat, a whole lotta bread, and more condiments than you can shake a stick at. But what he doesn’t have is a menu! Can you build a program that makes a new random menu for him every day?

Do this

  • Start a new project and add a MenuMaker class.

    If you need to build a menu, you need ingredients. And arrays would be perfect for those lists. We’ll also need some way of choosing random ingredients to combine together into a sandwich. Luckily, the .NET Framework has a built-in class called Random that generates random numbers. So we’ll have four fields in our class: a Randomizer field that holds a reference to a Random object, and three arrays of strings to hold the meats, condiments, and breads.

    image with no caption
    image with no caption
  • Add a GetMenuItem() method to the class that generates a random sandwich.

    The point of the class is to generate sandwiches, so let’s add a method to do exactly that. It’ll use the Random object’s Next() method to choose a random meat, condiment, and bread from each array. When you pass an int parameter to Next(), the method returns a random number that’s less than that parameter. So if your Random object is called Randomizer, then calling Randomizer.Next(7) will return a random number between 0 and 6.

    So how do you know what parameter to pass into the Next() method? Well, that’s easy—just pass in each array’s Length. That will return the index of a random item in the array.

    image with no caption

Objects use references to talk to each other

So far, you’ve seen forms talk to objects by using reference variables to call their methods and check their fields. Objects can call one another’s methods using references, too. In fact, there’s nothing that a form can do that your objects can’t do, because your form is just another object. And when objects talk to each other, one useful keyword that they have is this. Any time an object uses the this keyword, it’s referring to itself—it’s a reference that points to the object that calls it.

image with no caption

    Let’s add a method to the Elephant class. Its first parameter is a message from an elephant. Its second parameter is the elephant that said it:

    public void TellMe(string message, Elephant whoSaidIt) {
        MessageBox.Show(whoSaidIt.Name + " says: " + message);

    Here’s what it looks like when it’s called. You can add to button4_Click(), but add it before the statement that resets the references! (lloyd = lucinda;)

    lloyd.TellMe("Hi", lucinda);

    We called Lloyd’s TellMe() method, and passed it two parameters: “Hi” and a reference to Lucinda’s object. The method uses its whoSaidIt parameter to access the Name parameter of whatever elephant was passed into TellMe() using its second parameter.


    Now let’s add this SpeakTo() method to the Elephant class. It uses a special keyword: this. That’s a reference that lets an object talk about itself.

    image with no caption

    Let’s take a closer look at how this works.

    lloyd.SpeakTo(lucinda, "Hello");

    When Lloyd’s SpeakTo() method is called, it uses its whoToTalkTo parameter (which has a reference to Lucinda) to call Lucinda’s TellMe() method.

    image with no caption

    So Lucinda acts as if she was called with ("Hello", lloyd), and shows this message:

    image with no caption

Where no object has gone before

There’s another important keyword that you’ll use with objects. When you create a new reference and don’t set it to anything, it has a value. It starts off set to null, which means it’s not pointing to anything.

image with no caption
image with no caption

Note: each snippet from the pool can be used more than once.

image with no caption

Answers in Pool Puzzle Solution.

Build a typing game

You’ve reached a milestone...you know enough to build a game! Here’s how your game will work. The form will display random letters. If the player types one of them, it disappears and the accuracy rate goes up. If the player types an incorrect letter, the accuracy rate goes down. As the player keeps typing letters, the game goes faster and faster, getting more difficult with each correct letter. If the form fills up with letters, the game is over!

Do this

image with no caption

    Here’s what the form will look like in the form designer:

    image with no caption

    You’ll need to:

    • Turn off the minimize box and maximize box. Then set the form’s FormBorderStyle property to Fixed3D. That way, the player won’t be able to accidentally drag and resize it. Then resize it so that it’s much wider than it is tall (we set our form’s size to 876, 174).

    • Drag a ListBox out of the toolbox onto the form. Set its Dock property to Fill, and its MultiColumn property to True. Set its Font to 72 point bold.

    • In the toolbox, expand the All Windows Forms group at the top. This will display many controls. Find the Timer control and double-click on it to add it to your form.

    • Find the StatusStrip in the All Windows Forms group in the toolbox and double-click on it to add a status bar to your form. You should now see the StatusStrip and Timer icons in the gray area at the bottom of the form designer:

      image with no caption

    See how you can use a Timer to make your form do more than one thing at once? Take a minute and flip to #4 in the “Leftovers” appendix to learn about another way to do that.


    You’ll be using three new controls, but they’re easy to work with!

    Even though you haven’t seen a ListBox, StatusStrip, or Timer before, you already know how to set their properties and work with them in your code. You’ll learn a lot more about them in the next few chapters.


    Take a closer look at the status bar at the bottom of the screenshot. On one side, it’s got a series of labels:

    image with no caption

    And on the other side, it’s got a label and a progress bar:

    image with no caption

    Add a StatusLabel to your StatusStrip by clicking its drop-down and selecting StatusLabel. Then do the following:

    • Use the Properties window to set its (Name) to correctLabel and its Text to “Correct: 0”. Add three more StatusLabels: missedLabel, totalLabel, and accuracyLabel, and set their Text properties to “Missed: 0”, “Total: 0”, and “Accuracy: 0%”.

      image with no caption
    • Add one more StatusLabel. Set its Spring to True, TextAlign to MiddleRight, and Text to “Difficulty”. Finally, add a ProgressBar and name it difficultyProgressBar.

    • Set the StatusStrip’s SizingGrip property to False (hit Escape if you’ve got a child StatusLabel or ProgressBar selected to return the IDE’s focus to the parent StatusStrip).


    Did you notice how your Timer control didn’t show up on your form? That’s because the Timer is a nonvisual control. It doesn’t actually change the look and feel of the form. It does exactly one thing: it calls a method over and over again. Set the Timer control’s Interval property to 800, so that it calls its method every 800 milliseconds. Then double-click on the timer1 icon in the designer. The IDE will do what it always does when you double-click on a control: it will add a method to your form. This time, it’ll add one called timer1_Tick. Here’s the code for it:

    image with no caption

    If the form is going to display the total number of keys the player pressed, the number that were missed and the number that were correct, and the player’s accuracy, then we’ll need a way to keep track of all that data. Sounds like a job for a new class! Add a class called Stats to your project. It’ll have four int fields called Total, Missed, Correct, and Accuracy, and a method called Update with one bool parameter: true if the player typed a correct letter that was in the ListBox, or false if the player missed one.

    image with no caption
    image with no caption

    You’ll need an instance of your new Stats class to actually store the information, so add a field called stats to store it. And you already saw that you’ll need a field called random—it’ll contain a Random object.

    Add the two fields to the top of your form:

    public partial class Form1 : Form
        Random random = new Random();
        Stats stats = new Stats();

    Before you go on, there are three properties you need to set. Set the Timer control’s Enabled property to True, the ProgressBar control’s Maximum property to 701, and the Form’s KeyPreview property to True. Take a minute and figure out why you need those properties. What happens if you don’t set them?


    There’s one last thing your game needs to do: any time the player hits a key, it needs to check if that key is correct (and remove the letter from the ListBox if it is), and update the stats on the StatusStrip.

    Go back to the form designer and select the form. Then go to the Properties window and click on the lightning bolt button. Scroll to the KeyDown row and double-click on it. This tells the IDE to add a method called Form1_KeyDown() that gets called every time the user presses a key. Here’s the code for the method:

    image with no caption
    image with no caption

    This game only runs once. Can you figure out how to modify it so the player can start a new game when it’s displaying “Game Over”?


    Your game’s done! Give it a shot and see how well you do. You may need to adjust the font size of the ListBox to make sure it holds exactly seven letters, and you can change the difficulty by adjusting the values that are subtracted from timer1.Interval in the Form1_KeyDown() method.

Controls are objects, just like any other object

You’ve built plenty of forms by dragging controls out of the toolbox. It turns out that those controls are just regular old objects. And since they’re objects, you can add references to them and work with them like you’d work with an instance of a class that you wrote yourself. Let’s see a live example of that by building a program that animates some Label controls by bouncing them back and forth on a form.

Do this

  • ➊ Create a new Windows Forms Application and build this form.

    image with no caption
  • Add a class called LabelBouncer. Here’s the code for it:

    image with no caption

    All you need to do to bounce a label across a form is to create a new instance of the LabelBouncer class, set its MyLabel field to point to a Label control on the form, and then call its Move() method over and over again.

    Each time the Move() method is called, the LabelBouncer nudges the label by changing its Left property. If the GoingForward field is true, then it nudges it to the right by adding 5; otherwise, it nudges it to the left by subtracting 5.

    Every control has a Parent property that contains a reference to the form, because the form is an object too!

  • Here’s the code for the form. See if you can figure out exactly what’s going on here. It uses an array of LabelBouncer objects to bounce labels back and forth, and has the Timer’s Tick event handler method call their Move() methods over and over again.

    The form stores an array of LabelBouncer references in a field called bouncers. When the ToggleBouncing() method is called, it uses the index parameter to check an element of the array. If the element is null, it creates a new LabelBouncer object and stores its reference in the array; otherwise, it clears the element by setting it to null.

    image with no caption
    image with no caption

    Since controls are just objects, you can pass references to them as method parameters and store them in arrays, fields, and variables.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required