Assembly Build Configuration Properties

InstallShield 11 Universal

Available in InstallShield Universal Premier Only

After an Assembly Build Configuration has been added to the Releases view, set its Standard and Advanced properties as described below to build your project into an assembly.

Standard Properties

Property	Description
Output Directory	This is the directory to which the built assembly will be written. The default is the Assembly Gallery that is located in the <Universal home>/assemblygallery directory. If you have created additional Assembly Gallery locations, you can change this property to one of those locations. In addition to this property value, all built assemblies are automatically written to a directory structure that consists of the assembly's UUID and Version properties (set for the root product in the Installation Design view). For example, if the Output Directory property is left set at the default value, then the assembly's directory structure would be as follows: <Universal home>/assemblygallery/<UUID>/<Version>/assembly.dat
Include Product File	Select whether the build of this assembly should produce a productRef.inf file. This file is required if this assembly will ever be included in a Universal Dynamic Suite Installer. The productRef.inf file is written to the output directory structure described above. For example, if you set this property to "True," then the <Universal home>/assemblygallery/<UUID>/<Version> directory, which is created for this assembly when it is built, would contain the following files: assembly.dat productRef.inf To include this assembly in a built Dynamic Suite Installer, copy the entire directory structure illustrated above into the <suiteProjectName>/disk1/assemblies directory. At run time, the suite will install the referenced assembly.
Generate Manifest	Select whether you want the build output of this build configuration to include the creation of a manifest.xml file. This file contains detailed information about the assembly, and is presented in XML format. This file is for your administrative use only.

Advanced Properties

Property	Description
Build Category Filter	This property enables you to specify the build category(ies) to exclude when you build this assembly. Those software objects that are set with the build category(ies) specified will not be included in the build.
Comments (Premier Only)	This optional property enables you to specify comments about this action. These comments are stored in the project file and are for your use only. They are ignored at run time.
Software Object Key Overrides	This optional property enables you to specify new UUIDs for all of the software objects in your project (the root product, features, and components). This property does not apply to the referenced products in a Static Suite Installer. These UUIDs are stored only with this build configuration—the UUIDs that are set for each of these objects in the Installation Design view are not altered. This enables you, for example, to create and manage different tiers of your product in conjunction with the Build Category Filter property—the Express tier's software objects would have different UUIDs from the Professional tier's software objects, and so on. This property also applies when building an RPM Installer project (Premier Only) that you want to be able to target multiple platforms. The UUIDs for the software objects would be different for each targeted platform, which is set in the Platform property of the RPM Build Configuration. For example, you would build each RPM Installer project as an RPM assembly (using an RPM Assembly Build Configuration), setting the Software Object Key Overrides property different for the software objects in the assembly before each build for each targeted platform. You could then reference these assemblies in a Universal Installer project, conditionalizing each feature for the appropriate targeted platform. The end result would be one project that references (installs) several RPM assemblies, each of which targets a specific platform and whose software objects are assigned unique UUIDs. The default value of this property is "Use key overrides," which means that new UUIDs will be assigned automatically to each software object when this project is built with this build configuration. To use the UUIDs of each software object as they are set in Installation Design view for this build configuration: Click the ellipsis ("..."), and the Software Object Keys dialog box opens. In the Software Object Keys dialog box, select the check box next to Use Default Keys. To change the UUID of a software object(s) for this build configuration: Click the ellipsis ("..."), and the Software Object Keys dialog box opens. In the left side of the dialog box, select the software object for which you want to set a new UUID. In the right side of the dialog box, double-click the Software Object UUID field, and the field becomes editable. Double-click the field again, and the current UUID becomes highlighted. Type the new, maximum 32-character, alphanumeric UUID with no spaces. The only non-alphanumeric character you can use is the underscore ("_"). Press Enter to save the new UUID. --OR-- To reset the UUID for all of the software objects in your project, click Generate All New UUIDs. Click OK. The Software Object Key Overrides property is now set to "Use key overrides."

Property

Description

Build Category Filter

This property enables you to specify the build category(ies) to exclude when you build this assembly. Those software objects that are set with the build category(ies) specified will not be included in the build.

Comments
(Premier Only)

This optional property enables you to specify comments about this action. These comments are stored in the project file and are for your use only. They are ignored at run time.

Software Object Key Overrides

This optional property enables you to specify new UUIDs for all of the software objects in your project (the root product, features, and components).

Note

This property does not apply to the referenced products in a Static Suite Installer.

These UUIDs are stored only with this build configuration—the UUIDs that are set for each of these objects in the Installation Design view are not altered. This enables you, for example, to create and manage different tiers of your product in conjunction with the Build Category Filter property—the Express tier's software objects would have different UUIDs from the Professional tier's software objects, and so on.

This property also applies when building an RPM Installer project (Premier Only) that you want to be able to target multiple platforms. The UUIDs for the software objects would be different for each targeted platform, which is set in the Platform property of the RPM Build Configuration. For example, you would build each RPM Installer project as an RPM assembly (using an RPM Assembly Build Configuration), setting the Software Object Key Overrides property different for the software objects in the assembly before each build for each targeted platform. You could then reference these assemblies in a Universal Installer project, conditionalizing each feature for the appropriate targeted platform. The end result would be one project that references (installs) several RPM assemblies, each of which targets a specific platform and whose software objects are assigned unique UUIDs.

The default value of this property is "Use key overrides," which means that new UUIDs will be assigned automatically to each software object when this project is built with this build configuration.

Procedures

To use the UUIDs of each software object as they are set in Installation Design view for this build configuration:

Click the ellipsis ("..."), and the Software Object Keys dialog box opens.
In the Software Object Keys dialog box, select the check box next to Use Default Keys.

To change the UUID of a software object(s) for this build configuration:

Click the ellipsis ("..."), and the Software Object Keys dialog box opens.
In the left side of the dialog box, select the software object for which you want to set a new UUID.
1. In the right side of the dialog box, double-click the Software Object UUID field, and the field becomes editable.
2. Double-click the field again, and the current UUID becomes highlighted.
3. Type the new, maximum 32-character, alphanumeric UUID with no spaces. The only non-alphanumeric character you can use is the underscore ("_").
4. Press Enter to save the new UUID.
--OR--
To reset the UUID for all of the software objects in your project, click Generate All New UUIDs.
Click OK. The Software Object Key Overrides property is now set to "Use key overrides."