/l Display a listing of installed assemblies.
nNote Using partially named assemblies with the /u or /ul switch may remove multiple assemblies.
Loading Assemblies
The assembly loader goes through a very detailed process, called probing, to load an assembly.
The loader attempts to locate and load an assembly based on the exact version number in the
manifest. However, you can direct the loader to load a different version of an assembly by
specifying it in a config file, such as the application config file, the machine config file, or a
publisher policy file (a file that directs an application to use a newer version of an assembly).
The loader looks for partially named assemblies in the same directory as the running application
or in a subdirectory. If an assembly is strongly named, then the loader will first search the
GAC before probing local directories.
The assembly loader follows a certain process to locate the correct assembly during probing.
This series of steps is quite detailed, and you can find more about how the runtime loads assemblies
on Microsoft??™s developer website (see Appendix A), but here??™s the process in a nutshell:
1. The runtime first checks any config files for the correct version of the assembly that it??™s
loading.
Pages:
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182