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

■

Note

Visual Studio 2008 will automatically reset references when you compile your applications! Therefore, if

you were to run your SharedCarLibClient.exe application within Visual Studio 2008, it will grab 

CarLibrary.dll

version 2.0.0.0! If you accidentally ran your application in this way, simply delete the current 

CarLibrary.dll

reference and select version 1.0.0.0 (which I suggested you place in a folder named CarLibrary Version 1.0.0.0).

Dynamically Redirecting to Specific Versions of a

Shared Assembly

When you wish to inform the CLR to load a version of a shared assembly other than the version

listed in its manifest, you may build a *.config file that contains a  element.

When doing so, you will need to create an  subelement that specifies the

friendly name of the assembly listed in the client manifest (CarLibrary, for this example) and an

optional culture attribute (which can be assigned an empty string or omitted altogether if you wish

to specify the default culture for the machine). Moreover, the  element will

define a  subelement to define the version currently in the manifest (via the

oldVersion attribute) and the version in the GAC to load instead (via the newVersion attribute).

Create a new configuration file in the application directory of SharedCarLibClient named

SharedCarLibClient.exe.config that contains the following XML data. Of course, the value of your

public key token will be different from what you see in the following markup, and it can be obtained

either by examining the client manifest using ildasm.exe or via the GAC.

C H A P T E R   1 5