InstallShield 2019 Express Edition
Most applications require certain COM servers in order to operate properly. In order for the operating system to recognize these COM servers, you need to register them.
InstallShield supports two methods for registering a COM server on a target machine:
| • | The COM information can be extracted from the file and used to register the COM server during the installation. |
| • | The file can be self-registered if it supports self-registration. Note that self-registration is not as reliable as having Windows Installer register and unregister the file with extracted COM information. |
The first method listed—extracting the COM information—is the recommended method.
Important • Some applications, like WinRunner, insert hook .dll files into the COM extraction engine. This causes COM extraction to fail and displays the following message: “ISRegSpy detects following module %1 hooked into this process, which causes ISRegSpy to malfunction. You need to shut the application down and restart COM extraction.” If you encounter this message, shut down the application and restart COM extraction, as the dialog box instructs.
Do not select the self-registering property for .exe files that are not self-registering. To self-register an .exe file, you need to launch the .exe file with the /regserver command. However, if the .exe file does not support the command-line switch, the .exe file will be launched during extraction at build time.
To register a COM server with InstallShield:
| 1. | In the View list under Specify Application Data, click Files. |
| 2. | Right-click the file you want to register and then click Properties. The Properties dialog box opens. |
| 3. | Click the COM & .NET Settings tab. |
| 4. | In the Registration Type list, select the type of registration that you want to perform on the file. |
| 5. | Click OK. |
See Also
InstallShield 2019 Express Edition Help LibraryApril 2019 |
Copyright Information | Flexera |