This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

// Use the get/set methods to interact with the object's name.

emp.SetName("Marv");

Console.WriteLine("Employee is named: {0}", emp.GetName());

Console.ReadLine();

}

Encapsulation Using Type Properties

Although you can encapsulate a piece of field data using traditional get and set methods, .NET lan-

guages prefer to enforce data protection using 

properties. First of all, understand that properties

always map to “real” accessor and mutator methods in terms of CIL code. Therefore, as a class

designer, you are still able to perform any internal logic necessary before making the value assign-

ment (e.g., uppercase the value, scrub the value for illegal characters, check the bounds of a

numerical value, and so on).

Here is the updated Employee class, now enforcing encapsulation of each field using property

syntax rather than traditional get and set methods:

class Employee

{

// Field data.

private string empName;

private int empID;

private float currPay;

// Properties.

public string Name

{

get { return empName; }

set { empName = value; }

}

public int ID

{

get { return empID; }

set { empID = value; }

}

public float Pay

{

get { return currPay; }

set { currPay = value; }

}

...

}

A C# property is composed by defining a get scope (accessor) and set scope (mutator) directly

within the property scope itself. Once we have these properties in place, it appears to the caller that

it is getting and setting a 

public point of data; however, the correct get and set block is called

behind the scenes to preserve encapsulation:

C H A P T E R   5