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

partial class Employee

{

// Constructors

...

// Properties

...

}

C H A P T E R   5  

■

D E F I N I N G   E N C A P S U L AT E D   C L A S S  T Y P E S

175

8849CH05.qxd  10/22/07  1:34 PM  Page 175

---

while the private field data and type methods are defined within the initial Employee.cs:

partial class Employee

{

// Field data.

private string empName;

private int empID;

private float currPay;

private int empAge;

private string empSSN;

private static string companyName;

public void GiveBonus(float amount)

{

currPay += amount;

}

public void DisplayStats()

{

Console.WriteLine("Name: {0}", empName);

Console.WriteLine("ID: {0}", empID);

Console.WriteLine("Age: {0}", empAge);

Console.WriteLine("SSN: {0}", empSSN);

Console.WriteLine("Pay: {0}", currPay);

}

}

As you might guess, this can be helpful to new team members who need to quickly learn about

the public interface of the type. Rather than reading through a single (lengthy) C# file to find the

members of interest, they can focus on the public members. Of course, once these files are com-

piled by the C# compiler, the end result is a single unified type. To this end, the partial modifier is

purely a design-time construct.

Also know that the names you give to the files that contain partial type definitions are entirely

up to you. Here, Employee.Internal.cs was chosen simply to indicate that this file contains grungy

infrastructure code that most developers can ignore. The only requirement when defining partial

types is that the type’s name (Employee in this case) is identical and defined within the same .NET

namespace.