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

■

I N T R O D U C I N G   . N E T  A S S E M B L I E S

485

8849CH15.qxd  10/22/07  1:46 PM  Page 485

---

Figure 15-5.

The primary module records secondary modules in the assembly manifest.

At this point you (hopefully) have a better understanding about the internal composition of a

.NET binary file. With this necessary preamble out of the way, we are ready to dig into the details of

building and configuring a variety of code libraries.

Building and Consuming a Single-File Assembly

To begin exploring the world of .NET assemblies, you’ll first create a single-file *.dll assembly

(named CarLibrary) that contains a small set of public types. To build a code library using Visual

Studio 2008, simply select the Class Library project workspace (see Figure 15-6).

C H A P T E R   1 5  

■

I N T R O D U C I N G   . N E T  A S S E M B L I E S

486

8849CH15.qxd  10/22/07  1:46 PM  Page 486

---

Figure 15-6.

Creating a C# code library

The design of your automobile library begins with an abstract base class named Car that

defines a number of protected data members exposed through custom properties (feel free to use

automatic property syntax if you wish; see Chapter 13). This class has a single abstract method

named TurboBoost(), which makes use of a custom enumeration (EngineState) representing the

current condition of the car’s engine:

using System;

namespace CarLibrary

{