InstallShield 2016
Project • This information applies to InstallScript Object projects.
InstallShield enables you to create your own InstallShield objects that can be used in any of your installation projects or distributed for use by other installation developers. Objects replace the templates found in earlier versions of InstallShield.
Note • Objects that you create can be used only with InstallShield X or later, InstallShield DevStudio, or InstallShield Professional 6.1 or later.
Creating an object is little different from creating a standard installation project. One difference is the importance of scope. When you create an object, you need to ensure that the object’s scope is optimal for its intended use. The scope of an object affects its usability. If the scope is too narrow, the object may be insufficient for your needs. If the scope is too large, the object may to be too cumbersome to be practical.
The following sections describe the steps in the object creation process.
Creating an Object
Currently, there are two ways to create an object. You can create a new InstallScript Object project from the New Project dialog box or convert an existing InstallScript project into an InstallScript object.
To convert an existing InstallScript project into an InstallScript object:
| 1. | On the File menu, click Save Project As. A Save As dialog box opens. |
| 2. | Select a folder in which to create a copy of the project. Note that you cannot save the new object project in the same folder as the original project. |
| 3. | In the File name box, type a name for the new project. |
| 4. | In the Save as type list, select InstallScript Object Project (*.ism). |
| 5. | Click Save. |
An object project file (.ism file) with the name that you specified, and all project subfolders, are created in the location that you specified. That project opens in InstallShield.
Object Design
The purpose of an object is to install a discrete piece of functionality. For example, you may need to install the latest version of DirectX in order for your application to run. Rather than including all the necessary files separately in your installation project, you can include the DirectX object that comes with InstallShield. Imagine if this same object contained, for example, Visual Basic run-time .dll files and MDAC support. The object would be too large for your needs. It would install files that are not needed and would increase the time required for the installation process. Therefore, it is a good idea to streamline your object as much as possible. Do not try to include four different technologies in one object. Instead, create four separate objects.
Objects follow the same structure as traditional installations, with one major difference—objects do not support setup types. The highest level of organization in an object is the feature. Under features fall components. Additionally, objects do not support shell objects. If you would like to create shell objects from an object, you will need to do so via script.
For more information, see Designing Objects.
Building an Object
Building an object is very similar to building an installation project. The easiest way to complete this task is to use the Release Wizard. The main difference between building an object and building an installation project is the fact that you do not need to specify a media type for an object. The wizard enables you to create media in the CD-ROM format only.
For more information, see Building an Object from the User Interface.
Testing Objects
As with any other software endeavor, it is a good idea to test before you release to the public. Testing an object is easy—just create a standard installation project, add your object to it, build it, and run it. If it works as planned, you are ready to include your object in projects. If not, you will need to debug. See Testing and Debugging an Object. (Note that if you have the object project and its associated installation project open in separate instances of InstallShield and you modify and rebuild your object, you must close and reopen the associated installation project to incorporate those modifications.)
Distributing Objects
As used here, distributing an object does not mean including that object in an installation and installing the files from that object on a target machine. Instead, distributing an object refers to creating an installation that will make that object available on other users’ machines for use in their installation projects. Because you do not want to install the logic contained within an object, you cannot just add it to a component as you normally would. To help you register your objects, you can use the InstallShield Object Installer object. When you associate this object with a feature, you will be prompted to select the object from your local gallery that you would like to distribute.
For more information, see Distributing an Object.
InstallShield 2016 Help LibraryAugust 2016 |
Copyright Information | Flexera Software |