About Manifests

AdminStudio 2023 | 25.0 | Repackager

Manifests, which are used during isolation, are XML files that describe an application. Repackager can create two types of manifests: application manifests and assembly manifest.

Application Manifests Describe an Isolated Application

Application manifests are XML files that describe an isolated application. This descriptive information includes the relationship between the application and its dependent files.

Typically, the naming convention for a manifest is:

     ApplicationName.Extension.manifest

For example, if the application was HelloWorld.exe, the manifest file is called:

     HelloWorld.exe.manifest

Assembly Manifests Describe an Application’s Assemblies

Assembly manifests are XML files that describe an application’s assemblies. This includes components such as DLLs.

Information stored in the assembly manifest, such as COM registration information, ProgIDs, etc., is usually stored in the Registry. However, by making it independent from the Registry, only that application can use the dependent files described in the manifest. This enables you to have multiple versions of the same DLL or other portable executable file on a system without generating compatibility conflicts.

Typically, the naming convention for a manifest is:

     AssemblyName.Extension.manifest

For example, if the component was Goodbye.dll, the manifest file is called:

     Goodbye.dll.manifest

Manifests as New Components

When you create manifests, Repackager supports putting them into new components. If you do not select the Create new component for each assembly option on the Manifest Options tab of the Isolation Options dialog box, the manifest will be added to the same component as the assembly.