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

The Identity of a Private Assembly

The full identity of a private assembly consists of the friendly name and numerical version, both of

which are recorded in the assembly manifest. The friendly name simply is the name of the module

that contains the assembly’s manifest minus the file extension. For example, if you examine the

manifest of the CarLibrary.dll assembly, you find the following:

.assembly CarLibrary

{

...

.ver 1:0:0:0

}

Given the isolated nature of a private assembly, it should make sense that the CLR does not

bother to make use of the version number when resolving its location. The assumption is that pri-

vate assemblies do not need to have any elaborate version checking, as the client application is the

only entity that “knows” of its existence. Given this, it is (very) possible for a single machine to have

multiple copies of the same private assembly in various application directories.