You can deploy assembly using cab files.
There are two ways to load assemblies from cab files.
You can give the URL of the cab file to Assembly.LoadFrom. For example,
2. Use app.config, and specify codebase hint, then use Assembly.Load.
<assemblyIdentity name=”myasm” culture = “neutral” publicKeyToken=”0123456789abcdef “/>
<codeBase version=”18.104.22.168″ href=”http://myserver/myasm.cab”/>
When we locate the cab file, we extract them to a temporary directory. The temporary directory becomes the application base now and we will probe the desired assembly in the temporary directory. We then copy the assembly to download cache, and remove the temporary directory we created. The final assembly location you see from Assembly.Location will be in download cache directory.
There are subtle difference in using Assembly.LoadFrom and codebase hint.
In Assembly.LoadFrom case, after we extract the cab file, we will only look for assembly with the same name as the cab file, excluding the extension. In our example above, we will only look for myasm.dll/myasm.exe.
In codebase hint case, we will look for the assembly specified in Assembly.Load, instead of the name of the cab file. This means, the cab file does not have to have the same name as the assembly.
A side effect of codebase hint behavior is that you can put multiple assemblies in one cab file. You will need to specify multiple assemblyBinding statements in app.config file to use the same cab file as codebase hint for different assemblies.
If you use this technique, due to how we extract the cab file and find the assembly (see above), we will download, and extract the same cab file multiple times. So bundling multiple assemblies in one cab file may actually hurt performance, instead of improving performance.
Of course, in reality, we use IE to download the cab file. You may benefit from IE’s caching of the downloaded cab file. You really want to measure your scenario, to decide if you want to use this technique or not.