InstallShield 2019 » Advanced Settings for a Component
Project • The Assembly area for a component is available in the following project types:
| • | Basic MSI |
| • | DIM |
| • | InstallScript MSI |
| • | Merge Module |
| • | MSI Database |
| • | MSM Database |
| • | Transform |
The following settings are available in the Assembly area under the Advanced Settings node of the Components view and the Setup Design view:
|
Setting |
Description |
|
Manifest |
For a .NET assembly, this setting is automatically set to the first .exe or DLL file in the component. For a Win32 assembly, this setting is automatically set to the first file in the component with the .manifest extension. The file name of the manifest is the application executable name, followed by the .manifest extension. This setting should be left blank if Global Assembly Cache is selected for the assembly's File Application setting. The Manifest setting cannot be deleted. |
|
File Application |
For a .NET assembly, this setting lets you specify whether to install the assembly in the global assembly cache. Select the appropriate file to install the assembly in your application's private cache, or select Global Assembly Cache to install the assembly in the global assembly cache. For a Win32 assembly, this setting lets you specify whether to install the assembly privately for the selected .exe or to install the assembly to the global assembly cache. If you select Global Assembly Cache, the assembly can be used by any .NET application on the target system. The File Application setting cannot be deleted. The value of this setting affects the component’s Destination setting. If the File Application setting is set to Global Assembly Cache, the component’s Destination setting is also set to Global Assembly Cache. For optimal advertising and repair, select the executable file that uses the assembly in this component. Note • To install a .NET assembly to the global assembly cache, the assembly must meet certain criteria. For details, consult Microsoft's .NET documentation. To install a Win32 assembly to the global assembly cache, your files must be signed and have catalog (.cat) files. For details, see “Creating Signed Files and Catalogs” in the Platform SDK help. |
|
Properties |
Enter the property names and values. To create a new entry, right-click in the grid and click New. For a Win32 assembly, you must enter values for the following properties: type, name, version, language, publicKeyToken, and processorArchitecture. For a private .NET assembly, you must enter values for the following properties: Name, Version, and Culture. For a global .NET assembly, you must enter values for the following properties: Name, Version, Culture, and PublicKeyToken. InstallShield adds the property name and value that you enter to the MsiAssemblyName table of your Windows Installer database. You can view the records in this table using the Direct Editor. Note • The property and values that you enter for your assembly must match the information in the assembly’s manifest file. If they do not match, the assembly might be left on the target system when your product is uninstalled. |
See Also
Advanced Settings for a Component
InstallShield 2019 Help LibraryApril 2019 |
Copyright Information | Flexera |