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

Exploring the ufo.netmodule File

Now, using ildasm.exe, open ufo.netmodule. As you can see, *.netmodules contain a module-level

manifest; however, its sole purpose is to list each external assembly referenced by the code base.

Given that the Ufo class did little more than make a call to Console.WriteLine(), you find the

following:

.assembly extern mscorlib

{

.publickeytoken = (B7 7A 5C 56 19 34 E0 89 )

.ver 2:0:0:0

}

.module ufo.netmodule

Exploring the airvehicles.dll File

Next, using ildasm.exe, open the primary airvehicles.dll module and investigate the assembly-

level manifest. Notice that the .file token documents the associated modules in the multifile

assembly (ufo.netmodule in this case). The .class extern tokens are used to document the names

of the external types referenced for use from the secondary module (Ufo):

.assembly extern mscorlib

{

.publickeytoken = (B7 7A 5C 56 19 34 E0 89 )

.ver 2:0:0:0

}

.assembly airvehicles

{

...

.hash algorithm 0x00008004

.ver 0:0:0:0

}