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

Exploring the Manifest of SharedCarLibClient

Recall that when you generate a strong name for an assembly, the entire public key is recorded in

the assembly manifest. On a related note, when a client references a strongly named assembly, its

manifest records a condensed hash value of the full public key, denoted by the .publickeytoken tag.

If you were to open the manifest of SharedCarLibClient.exe using ildasm.exe, you would find the

following (your public key token value will of course differ, as it is computed based on the public

key value):

.assembly extern CarLibrary

{

.publickeytoken = (21 9E F3 80 C9 34 8A 38)

.ver 1:0:0:0

}

If you compare the value of the public key token recorded in the client manifest with the

public key token value shown in the GAC, you will find a dead-on match. Recall that a public key

represents one aspect of the strongly named assembly’s identity. Given this, the CLR will only load

version 1.0.0.0 of an assembly named CarLibrary that has a public key that can be hashed down

to the value 219EF380C9348A38. If the CLR does not find an assembly meeting this description in

the GAC (and did not find a private assembly named CarLibrary in the client’s directory), a

FileNotFoundException exception is thrown.