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

.file ufo.netmodule

...

.class extern public AirVehicles.Ufo

{

.file ufo.netmodule

.class 0x02000002

}

.module airvehicles.dll

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

497

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

---

Again, realize that the only entity that links together airvehicles.dll and ufo.netmodule is the

assembly manifest. These two binary files have not been merged into a single, larger *.dll.

Consuming a Multifile Assembly

The consumers of a multifile assembly couldn’t care less that the assembly they are referencing is

composed of numerous modules. To keep things simple, let’s create a new C# client application at

the command line. Create a new file named Client.cs with the following module definition. When

you are done, save it in the same location as your multifile assembly.

using System;

using AirVehicles;

class Program

{

static void Main()

{

Console.WriteLine("***** Multifile Assembly Client *****");

Helicopter h  = new Helicopter();

h.TakeOff();