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

■

I N T R O D U C I N G   . N E T  A S S E M B L I E S

518

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

---

Here, the XML content is contained within a file named CarLibraryPolicy.xml. The name of

the output file (which must be in the format policy...assemblyToConfigure) is

specified using the obvious /out flag. In addition, note that the name of the file containing the pub-

lic/private key pair will also need to be supplied via the /keyf option. Remember, publisher policy

files are shared, and therefore must have a strong name!

Once the al.exe tool has executed, the result is a new assembly that can be placed into the

GAC to force all clients to bind to version 2.0.0.0 of CarLibrary.dll, without the use of a specific

client application configuration file. Using this technique, you are able to design a “machinewide”

redirection for all applications using a specific version (or range of versions) of an existing assembly.