- per-application configuration
Configuration that can override a specific assembly's global application configuration. A per-application configuration is specified by an application configuration manifest file installed in the same folder as the executable file. The manifest file describes the version, or range of versions, of side-by-side assemblies to be used by the application. Per-application configuration might be used when a new version of an assembly is incompatible with an application. In this case, the application's default or global configuration can be overridden for a specific side-by-side assembly.
- private side-by-side assembly
A private side-by-side assembly is only visible to a specified application. It is installed locally to an isolated application and the assembly's code becomes private to the application context. The dependencies of a private side-by-side assembly are described in the application manifest file. Private side-by-side assemblies can be used to offset the negative effects of assembly sharing, such as DLL conflicts, and to facilitate application deployment.
- public key token
A 16-character hexadecimal string that represents the last 8 bytes of the SHA-1 hash of the public key under which the assembly is signed. The public key used to sign the catalog must be 2048 bits or greater. Required for all shared side-by-side assemblies.