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

// Don't forget to import the CarLibrary namespace!

using CarLibrary;

namespace CSharpCarClient

{

public class Program

{

static void Main(string[] args)

{

Console.WriteLine("***** C# CarLibrary Client App *****");

// Make a sports car.

SportsCar viper = new SportsCar("Viper", 240, 40);

viper.TurboBoost();

// Make a minivan.

MiniVan mv = new MiniVan();

mv.TurboBoost();

Console.ReadLine();

}

}

}

This code looks just like the code of the other applications developed thus far in the text. The

only point of interest is that the C# client application is now making use of types defined within a

separate custom assembly. Go ahead and run your program. As you would expect, the execution of

this program results in the display of various message boxes.

It is also important to point out that Visual Studio 2008 has also placed a copy of CarLibrary.

dll into the \bin\Debug folder of the CSharpCarClient project folder. This can be verified by click-

ing the Show All Files button of the Solution Explorer (see Figure 15-10).

Figure 15-10.

Visual Studio 2008 copies private assemblies to the client’s directory.

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

493

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

---

As explained later in this chapter, CarLibrary.dll has been deployed as a “private” assembly.

Therefore the CLR loads the local copy of the .NET binary on behalf of the current client

(CSharpCarClient.exe).