Isolation Options Dialog Box
AdminStudio 2022 R2 | 24.0 | Repackager
Edition:This feature is available in AdminStudio Professional and Enterprise Editions.
Application isolation reduces versioning conflicts by modifying an application so it always loads the versions of components—such as DLLs—with which it was originally developed and tested.
On the Isolation Options dialog box, which is opened by selecting Isolation Options from the Tools menu, you can specify the following Repackager isolation options:
| • | Assembly Options—Specify the type of assemblies Repackager will create, and the assembly naming conventions. See Manifest Options Tab |
| • | Digital Signature Options—Configure the certificate information required when using shared assemblies. See Digital Signature Tab. |
Note:The modifications you make on the Isolation Options dialog box will be recorded in the isolationconfig.ini file, which is stored in the AdminStudio Shared directory.
The Manifest Options tab allows you to configure several settings associated with manifests. The following settings are included:
|
Option |
Description |
||||||
|
Assembly Type |
This option allows you to select the type of assemblies that Repackager will create and use:
Note:Manifests for shared assemblies must be digitally signed. This can be done in the Digital Signature Tab. Note:A 2048-bit key is required to sign an assembly/manifest being installed to the WinSxS folder. |
||||||
|
Assembly Naming Conventions |
Specify your company and division information to define the default naming convention that Repackager will use when creating assemblies during application isolation By default, assembly names are specified in the form of: Company.Division.Assembly Note:See see About Assemblies and About Manifests for more information. |
||||||
|
Create a new component for each assembly |
Select this option if you want to create a new component for each assembly created during isolation. This check box applies to all assemblies created. Caution:If you are creating assemblies for applications files within multiple components, this option must be selected for successful application isolation. |
On the Digital Signature tab, you can configure the certificate information required when using shared assemblies.This required digital signature provides an extra layer of protection, allowing you to obtain information about the company who created a global assembly.
Caution:Repackager uses timestamping when signing global assemblies. Consequently, you must have an Internet connection on the computer when you create a global assembly.
You must configure the following options when signing these assemblies:
|
Item |
Description |
|
Certificate File |
Click the Browse ( A digital certificate identifies you and/or your company to end users and assures them the data they are about to receive has not been altered. |
|
Credentials |
Select this option to use credential files as the code signing technology. If you select this option, you must supply the name and location of both your software publishing credential files: SPC File and PVK File. Note:In order to receive a software publishing credentials and a private key, you must supply a certification authority, such as VeriSign, with specific information about your company and software. |
|
SPC File |
Specify the name and location of your software publishing credentials file (.spc). |
|
PVK |
Specify the name and location of your private key file (.pvk). |
|
Certificate Name in the Store |
Select this option to use the name of an existing certificate file in the Certificate Store as the code signing technology. The Certificate Store is a central repository for certificate files. Using a Certificate Store allows you to reuse the certificate files for different purposes as necessary. |
) button next to the field and navigate to the certificate file you are using to sign assemblies. Note:For more information, see About Digital Certificates.