Finally, installing an assembly into the GAC makes XCopy
deployment unavailable, as you must move the assembly into the GAC when installing your
application. Figure 5-2 shows the GAC listing. Notice that each assembly has a name, a version,
a culture, and a public key token.
Figure 5-2. Shared assemblies are located in the GAC.
If the Culture column is blank for an assembly, it means that it??™s culture-neutral, which
is common for assemblies that contain only code. If you develop applications that require
CHAPTER 5 n VB 2008 AND THE CLR 93
localization, we recommend that you isolate all of the resources into a separate assembly that
can be swapped out easily with a different culture without affecting the base code.
To deploy a shared assembly, use the command-line utility gacutil.exe. This utility is
used to view, install, and uninstall assemblies in the GAC. Table 5-1 describes some of the
available command-line switches that you can use with gacutil.exe.
Table 5-1. gacutil.exe Command-Line Switches
Switch Meaning
/i Install the assembly into the GAC.
/u Remove the assembly from the GAC, if no other references to it exist.
/il Use a text file containing assembly names to be installed.
/ul Use a text file containing assembly names to be removed.
Pages:
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181