- •Contents at a Glance
- •Table of Contents
- •Acknowledgments
- •Introduction
- •Who This Book Is For
- •Finding Your Best Starting Point in This Book
- •Conventions and Features in This Book
- •Conventions
- •Other Features
- •System Requirements
- •Code Samples
- •Installing the Code Samples
- •Using the Code Samples
- •Support for This Book
- •Questions and Comments
- •Beginning Programming with the Visual Studio 2008 Environment
- •Writing Your First Program
- •Using Namespaces
- •Creating a Graphical Application
- •Chapter 1 Quick Reference
- •Understanding Statements
- •Identifying Keywords
- •Using Variables
- •Naming Variables
- •Declaring Variables
- •Working with Primitive Data Types
- •Displaying Primitive Data Type Values
- •Using Arithmetic Operators
- •Operators and Types
- •Examining Arithmetic Operators
- •Controlling Precedence
- •Using Associativity to Evaluate Expressions
- •Associativity and the Assignment Operator
- •Incrementing and Decrementing Variables
- •Declaring Implicitly Typed Local Variables
- •Chapter 2 Quick Reference
- •Declaring Methods
- •Specifying the Method Declaration Syntax
- •Writing return Statements
- •Calling Methods
- •Specifying the Method Call Syntax
- •Applying Scope
- •Overloading Methods
- •Writing Methods
- •Chapter 3 Quick Reference
- •Declaring Boolean Variables
- •Using Boolean Operators
- •Understanding Equality and Relational Operators
- •Understanding Conditional Logical Operators
- •Summarizing Operator Precedence and Associativity
- •Using if Statements to Make Decisions
- •Understanding if Statement Syntax
- •Using Blocks to Group Statements
- •Cascading if Statements
- •Using switch Statements
- •Understanding switch Statement Syntax
- •Following the switch Statement Rules
- •Chapter 4 Quick Reference
- •Using Compound Assignment Operators
- •Writing while Statements
- •Writing for Statements
- •Understanding for Statement Scope
- •Writing do Statements
- •Chapter 5 Quick Reference
- •Coping with Errors
- •Trying Code and Catching Exceptions
- •Handling an Exception
- •Using Multiple catch Handlers
- •Catching Multiple Exceptions
- •Using Checked and Unchecked Integer Arithmetic
- •Writing Checked Statements
- •Writing Checked Expressions
- •Throwing Exceptions
- •Chapter 6 Quick Reference
- •The Purpose of Encapsulation
- •Controlling Accessibility
- •Working with Constructors
- •Overloading Constructors
- •Understanding static Methods and Data
- •Creating a Shared Field
- •Creating a static Field by Using the const Keyword
- •Chapter 7 Quick Reference
- •Copying Value Type Variables and Classes
- •Understanding Null Values and Nullable Types
- •Using Nullable Types
- •Understanding the Properties of Nullable Types
- •Using ref and out Parameters
- •Creating ref Parameters
- •Creating out Parameters
- •How Computer Memory Is Organized
- •Using the Stack and the Heap
- •The System.Object Class
- •Boxing
- •Unboxing
- •Casting Data Safely
- •The is Operator
- •The as Operator
- •Chapter 8 Quick Reference
- •Working with Enumerations
- •Declaring an Enumeration
- •Using an Enumeration
- •Choosing Enumeration Literal Values
- •Choosing an Enumeration’s Underlying Type
- •Working with Structures
- •Declaring a Structure
- •Understanding Structure and Class Differences
- •Declaring Structure Variables
- •Understanding Structure Initialization
- •Copying Structure Variables
- •Chapter 9 Quick Reference
- •What Is an Array?
- •Declaring Array Variables
- •Creating an Array Instance
- •Initializing Array Variables
- •Creating an Implicitly Typed Array
- •Accessing an Individual Array Element
- •Iterating Through an Array
- •Copying Arrays
- •What Are Collection Classes?
- •The ArrayList Collection Class
- •The Queue Collection Class
- •The Stack Collection Class
- •The Hashtable Collection Class
- •The SortedList Collection Class
- •Using Collection Initializers
- •Comparing Arrays and Collections
- •Using Collection Classes to Play Cards
- •Chapter 10 Quick Reference
- •Using Array Arguments
- •Declaring a params Array
- •Using params object[ ]
- •Using a params Array
- •Chapter 11 Quick Reference
- •What Is Inheritance?
- •Using Inheritance
- •Base Classes and Derived Classes
- •Calling Base Class Constructors
- •Assigning Classes
- •Declaring new Methods
- •Declaring Virtual Methods
- •Declaring override Methods
- •Understanding protected Access
- •Understanding Extension Methods
- •Chapter 12 Quick Reference
- •Understanding Interfaces
- •Interface Syntax
- •Interface Restrictions
- •Implementing an Interface
- •Referencing a Class Through Its Interface
- •Working with Multiple Interfaces
- •Abstract Classes
- •Abstract Methods
- •Sealed Classes
- •Sealed Methods
- •Implementing an Extensible Framework
- •Summarizing Keyword Combinations
- •Chapter 13 Quick Reference
- •The Life and Times of an Object
- •Writing Destructors
- •Why Use the Garbage Collector?
- •How Does the Garbage Collector Work?
- •Recommendations
- •Resource Management
- •Disposal Methods
- •Exception-Safe Disposal
- •The using Statement
- •Calling the Dispose Method from a Destructor
- •Making Code Exception-Safe
- •Chapter 14 Quick Reference
- •Implementing Encapsulation by Using Methods
- •What Are Properties?
- •Using Properties
- •Read-Only Properties
- •Write-Only Properties
- •Property Accessibility
- •Understanding the Property Restrictions
- •Declaring Interface Properties
- •Using Properties in a Windows Application
- •Generating Automatic Properties
- •Initializing Objects by Using Properties
- •Chapter 15 Quick Reference
- •What Is an Indexer?
- •An Example That Doesn’t Use Indexers
- •The Same Example Using Indexers
- •Understanding Indexer Accessors
- •Comparing Indexers and Arrays
- •Indexers in Interfaces
- •Using Indexers in a Windows Application
- •Chapter 16 Quick Reference
- •Declaring and Using Delegates
- •The Automated Factory Scenario
- •Implementing the Factory Without Using Delegates
- •Implementing the Factory by Using a Delegate
- •Using Delegates
- •Lambda Expressions and Delegates
- •Creating a Method Adapter
- •Using a Lambda Expression as an Adapter
- •The Form of Lambda Expressions
- •Declaring an Event
- •Subscribing to an Event
- •Unsubscribing from an Event
- •Raising an Event
- •Understanding WPF User Interface Events
- •Using Events
- •Chapter 17 Quick Reference
- •The Problem with objects
- •The Generics Solution
- •Generics vs. Generalized Classes
- •Generics and Constraints
- •Creating a Generic Class
- •The Theory of Binary Trees
- •Building a Binary Tree Class by Using Generics
- •Creating a Generic Method
- •Chapter 18 Quick Reference
- •Enumerating the Elements in a Collection
- •Manually Implementing an Enumerator
- •Implementing the IEnumerable Interface
- •Implementing an Enumerator by Using an Iterator
- •A Simple Iterator
- •Chapter 19 Quick Reference
- •What Is Language Integrated Query (LINQ)?
- •Using LINQ in a C# Application
- •Selecting Data
- •Filtering Data
- •Ordering, Grouping, and Aggregating Data
- •Joining Data
- •Using Query Operators
- •Querying Data in Tree<TItem> Objects
- •LINQ and Deferred Evaluation
- •Chapter 20 Quick Reference
- •Understanding Operators
- •Operator Constraints
- •Overloaded Operators
- •Creating Symmetric Operators
- •Understanding Compound Assignment
- •Declaring Increment and Decrement Operators
- •Implementing an Operator
- •Understanding Conversion Operators
- •Providing Built-In Conversions
- •Creating Symmetric Operators, Revisited
- •Adding an Implicit Conversion Operator
- •Chapter 21 Quick Reference
- •Creating a WPF Application
- •Creating a Windows Presentation Foundation Application
- •Adding Controls to the Form
- •Using WPF Controls
- •Changing Properties Dynamically
- •Handling Events in a WPF Form
- •Processing Events in Windows Forms
- •Chapter 22 Quick Reference
- •Menu Guidelines and Style
- •Menus and Menu Events
- •Creating a Menu
- •Handling Menu Events
- •Shortcut Menus
- •Creating Shortcut Menus
- •Windows Common Dialog Boxes
- •Using the SaveFileDialog Class
- •Chapter 23 Quick Reference
- •Validating Data
- •Strategies for Validating User Input
- •An Example—Customer Information Maintenance
- •Performing Validation by Using Data Binding
- •Changing the Point at Which Validation Occurs
- •Chapter 24 Quick Reference
- •Querying a Database by Using ADO.NET
- •The Northwind Database
- •Creating the Database
- •Using ADO.NET to Query Order Information
- •Querying a Database by Using DLINQ
- •Creating and Running a DLINQ Query
- •Deferred and Immediate Fetching
- •Joining Tables and Creating Relationships
- •Deferred and Immediate Fetching Revisited
- •Using DLINQ to Query Order Information
- •Chapter 25 Quick Reference
- •Using Data Binding with DLINQ
- •Using DLINQ to Modify Data
- •Updating Existing Data
- •Adding and Deleting Data
- •Chapter 26 Quick Reference
- •Understanding the Internet as an Infrastructure
- •Understanding Web Server Requests and Responses
- •Managing State
- •Understanding ASP.NET
- •Creating Web Applications with ASP.NET
- •Building an ASP.NET Application
- •Understanding Server Controls
- •Creating and Using a Theme
- •Chapter 27 Quick Reference
- •Comparing Server and Client Validations
- •Validating Data at the Web Server
- •Validating Data in the Web Browser
- •Implementing Client Validation
- •Chapter 28 Quick Reference
- •Managing Security
- •Understanding Forms-Based Security
- •Implementing Forms-Based Security
- •Querying and Displaying Data
- •Understanding the Web Forms GridView Control
- •Displaying Customer and Order History Information
- •Paging Data
- •Editing Data
- •Updating Rows Through a GridView Control
- •Navigating Between Forms
- •Chapter 29 Quick Reference
- •What Is a Web Service?
- •The Role of SOAP
- •What Is the Web Services Description Language?
- •Nonfunctional Requirements of Web Services
- •The Role of Windows Communication Foundation
- •Building a Web Service
- •Creating the ProductsService Web Service
- •Web Services, Clients, and Proxies
- •Talking SOAP: The Easy Way
- •Consuming the ProductsService Web Service
- •Chapter 30 Quick Reference
142 |
Part II Understanding the C# Language |
The C# compiler uses the names, types, number, and order of the fields to determine
whether two instances of an anonymous class have the same type. In this case, variables myAnonymousObject and anotherAnonymousObject have the same number of fields,
with the same name and type, in the same order, so both variables are instances of the same anonymous class. This means that you can perform assignment statements such as this:
anotherAnonymousObject = myAnonymousObject;
Note Be warned that this assignment statement might not accomplish what you expect. You’ll learn more about assigning object variables in Chapter 8, “Understanding Values and References.”
There are quite a lot of restrictions on the contents of an anonymous class. Anonymous classes can contain only public fields, the fields must all be initialized, they cannot be static, and you cannot specify any methods.
If you want to continue to the next chapter
Keep Visual Studio 2008 running, and turn to Chapter 8.
If you want to exit Visual Studio 2008 now
On the File menu, click Exit. If you see a Save dialog box, click Yes (if you are using Visual Studio 2008) or Save (if you are using Microsoft Visual C# 2008 Express Edition) and save the project.
Chapter 7 Quick Reference
To |
Do this |
Declare a class |
Write the keyword class, followed by the name of the class, followed by an |
|
opening and closing brace. The methods and fields of the class are declared |
|
between the opening and closing braces. For example: |
|
class Point |
|
{ |
|
... |
|
} |
|
Chapter 7 Creating and Managing Classes and Objects |
143 |
|
|
|
Declare a constructor |
Write a method whose name is the same as the name of the class and that |
|
|
has no return type (not even void). For example: |
|
|
class Point |
|
|
{ |
|
|
public Point(int x, int y) |
|
|
{ |
|
|
... |
|
|
} |
|
|
} |
|
Call a constructor |
Use the new keyword, and specify the constructor with an appropriate set |
|
|
of parameters. For example: |
|
|
Point origin = new Point(0, 0); |
|
Declare a static |
Write the keyword static before the declaration of the method. For |
|
method |
example: |
|
|
class Point |
|
|
{ |
|
|
public static int ObjectCount() |
|
|
{ |
|
|
... |
|
|
} |
|
|
} |
|
Call a static method |
Write the name of the class, followed by a period, followed by the name of |
|
|
the method. For example: |
|
|
int pointsCreatedSoFar = Point.ObjectCount(); |
|
Declare a static field |
Write the keyword static before the declaration of the field. For example: |
|
|
class Point |
|
|
{ |
|
|
... |
|
|
private static int objectCount; |
|
|
} |
|
Declare a const field |
Write the keyword const before the declaration of the field, and omit the |
|
|
static keyword. For example: |
|
|
class Math |
|
|
{ |
|
|
... |
|
|
public const double PI = ...; |
|
|
} |
|
Access a static field |
Write the name of the class, followed by a period, followed by the name of |
|
|
the static field. For example: |
|
double area = Math.PI * radius * radius;
Chapter 8
Understanding Values and
References
After completing this chapter, you will be able to:
QExplain the differences between a value type and a reference type.
QModify the way in which arguments are passed as method parameters by using the ref and out keywords.
QBox a value by initializing or assigning a variable of type object.
QUnbox a value by casting the object reference that refers to the boxed value.
In Chapter 7, “Creating and Managing Classes and Objects,” you learned how to declare your own classes and how to create objects by using the new keyword. You also saw how
to initialize an object by using a constructor. In this chapter, you will learn about how the characteristics of the primitive types, such as int, double, and char, differ from the
characteristics of class types.
Copying Value Type Variables and Classes
Collectively, the types such as int, float, double, and char are called value types. When you declare a variable as a value type, the compiler generates code that allocates a block of memory big enough to hold a corresponding value. For example, declaring an int variable causes the compiler to allocate 4 bytes of memory (32 bits). A statement that assigns a value (such as 42) to the int causes the value to be copied into this block of memory.
Class types, such as Circle (described in Chapter 7), are handled differently. When you declare a Circle variable, the compiler does not generate code that allocates a block of memory big enough to hold a Circle; all it does is allot a small piece of memory that can potentially hold the address of (or a reference to) another block of memory containing a Circle. (An address specifies the location of an item in memory.) The memory for the actual Circle object is al-
located only when the new keyword is used to create the object. A class is an example of a reference type. Reference types hold references to blocks of memory.
Note Most of the primitive types of the C# language are value types except for string, which is a
reference type. The description of reference types such as classes in this chapter applies to the string type as well. In fact, the string keyword in C# is just an alias for the System.String class.
145
146 |
Part II Understanding the C# Language |
You need to fully understand the difference between value types and reference types.
Consider the situation in which you declare a variable named i as an int and assign it the value 42. If you declare another variable called copyi as an int and then assign i to copyi, copyi will hold the same value as i (42). However, even though copyi and i happen to hold the same
value, there are still two blocks of memory containing the value 42: one block for i and the other block for copyi. If you modify the value of i, the value of copyi does not change. Let’s
see this in code:
int i = 42; // declare and initialize i
int copyi = i; // |
copyi contains |
a copy |
of the |
data in i |
|
i++; |
// |
incrementing i |
has no |
effect |
on copyi |
The effect of declaring a variable c as a Circle (the name of a class) is very different. When you declare c as a Circle, c can refer to a Circle object. If you declare refc as another Circle, it can also refer to a Circle object. If you assign c to refc, refc will refer to the same Circle object that c does; there is only one Circle object, and refc and c both refer to it. What has happened here is that the compiler has allocated two blocks of memory, one for c and one for refc, but
the address contained in each block points to the same location in memory that stores the actual Circle object. Let’s see this in code:
Circle c = new Circle(42);
Circle refc = c;
The following graphic illustrates both examples. The at sign (@) in the Circle objects represents a reference to an address in memory:
The difference explained here is very important. In particular, it means that the behavior of method parameters depends on whether they are value types or reference types. You’ll explore this difference in the following exercise.
Chapter 8 Understanding Values and References |
147 |
Note If you actually want to copy the contents of the c variable into refc rather than just copying the reference, you must make refc refer to a new instance of the Circle class and then copy the data field by field from c into refc, like this:
Circle refc |
= |
new Circle(); |
// Don’t try this |
refc.radius |
= |
c.radius; |
However, if any members of the Circle class are private (like the radius field), you will not be able to copy this data. Instead, you should make the data in the private fields accessible by exposing them as properties. You will learn how to do this in Chapter 15, “Implementing Properties to Access Fields.”
Use value parameters and reference parameters
1.Start Microsoft Visual Studio 2008 if it is not already running.
2.Open the Parameters project located in the \Microsoft Press\Visual CSharp Step by Step\Chapter 8\Parameters folder in your Documents folder.
The project contains three C# code files named Pass.cs, Program.cs, and WrappedInt.cs.
3.Display the Pass.cs file in the Code and Text Editor window. Add a public static method called Value to the Pass class, replacing the // to do comment, as shown in bold type in the following code example. This method should accept a single int parameter (a value type) called param and have the return type void. The body of the Value method should simply assign 42 to param.
namespace Parameters
{
class Pass
{
public static void Value(int param)
{
param = 42;
}
}
}
4.Display the Program.cs file in the Code and Text Editor window, and then locate the Entrance method of the Program class.
The Entrance method is called by the Main method when the program starts running. As explained in Chapter 7, the method call is wrapped in a try block and followed by a catch handler.
5.Add four statements to the Entrance method to perform the following tasks:
QDeclare a local int variable called i, and initialize it to 0.
QWrite the value of i to the console by using Console.WriteLine.
QCall Pass.Value, passing i as an argument.
QWrite the value of i to the console again.
148 Part II Understanding the C# Language
With the calls to Console.WriteLine before and after the call to Pass.Value, you can see whether the call to Pass.Value actually modifies the value of i. The completed Entrance
method should look exactly like this:
static void Entrance()
{
int i = 0; Console.WriteLine(i); Pass.Value(i); Console.WriteLine(i);
}
6.On the Debug menu, click Start Without Debugging to build and run the program.
7.Confirm that the value 0 is written to the console window twice.
The assignment statement inside the Pass.Value method that updates the parameter uses a copy of the argument passed in, and the original argument i is completely unaffected.
8.Press the Enter key to close the application.
You will now see what happens when you pass an int parameter that is wrapped inside a class.
9.Display the WrappedInt.cs file in the Code and Text Editor window. Add a public instance field called Number of type int to the WrappedInt class, as shown in bold type here.
namespace Parameters
{
class WrappedInt
{
public int Number;
}
}
10.Display the Pass.cs file in the Code and Text Editor window. Add a public static method called Reference to the Pass class. This method should accept a single WrappedInt parameter called param and have the return type void. The body of the Reference method should assign 42 to param.Number, like this:
public static void Reference(WrappedInt param)
{
param.Number = 42;
}
11.Display the Program.cs file in the Code and Text Editor window. Add four more statements to the Entrance method to perform the following tasks:
QDeclare a local WrappedInt variable called wi, and initialize it to a new WrappedInt object by calling the default constructor.
QWrite the value of wi.Number to the console.
Chapter 8 Understanding Values and References |
149 |
QCall the Pass.Reference method, passing wi as an argument.
QWrite the value of wi.Number to the console again.
As before, with the calls to Console.WriteLine, you can see whether the call to Pass. Reference modifies the value of wi.Number. The Entrance method should now look
exactly like this (the new statements are shown in bold type):
static void Entrance()
{
int i = 0; Console.WriteLine(i); Pass.Value(i); Console.WriteLine(i);
WrappedInt wi = new WrappedInt(); Console.WriteLine(wi.Number); Pass.Reference(wi); Console.WriteLine(wi.Number);
}
12.On the Debug menu, click Start Without Debugging to build and run the application.
As before, the first two values written to the console window are 0 and 0, before and after the call to Pass.Value. However, the next two values correspond to the value of wi.Number before and after Pass.Reference, and you should see that the values 0 and 42 are written to the console window.
13.Press the Enter key to close the application and return to Visual Studio 2008.
In the previous exercise, the value of wi.Number is initialized to 0 by the compiler-generated default constructor. The wi variable contains a reference to the newly created WrappedInt object (which contains an int). The wi variable is then copied as an argument to the Pass. Reference method. Because WrappedInt is a class (a reference type), wi and param both refer to the same WrappedInt object. Any changes made to the contents of the object through the param variable in the Pass.Reference method are visible by using the wi variable when the method completes. The following diagram illustrates what happens when a WrappedInt object is passed as an argument to the Pass.Reference method:
