InstallShield 2016
Project • This information applies to the following project types:
| • | Basic MSI | 
| • | DIM | 
| • | InstallScript MSI | 
| • | Merge Module | 
If you have selected ISSelfReg as the self-registration method for COM servers, and if your project contains any files (or dynamic links) marked as self-registered, InstallShield adds information about those files to the ISSelfReg table of your .msi database.
| Column Name | Description | 
| FileKey | Foreign key into the File table, identifying the file (.dll, .ocx, .exe, .tlb, .olb) to be self-registered. | 
| Cost | Reserved for future use. | 
| Order | A nonnegative number identifying the order in which self-registration will occur. Any files with an Order value of 1 will be registered first, followed by files with an Order value of 2, and so forth. Finally, all files with an Order value of 0 will be registered. | 
| CmdLine | For self-registering .exe files, stores a command line to be passed to the executable when it is self-registered. By default the field is empty, and the InstallShield run-time engine registers the .exe file with the /regserver argument and unregisters it with the /unregserver argument. To specify different arguments to pass during registration and unregistration, separate the arguments with a vertical bar (|), as in /hello|/goodbye. | 
See Also
Installing Self-Registering Files
| InstallShield 2016 Help LibraryAugust 2016 | Copyright Information | Flexera Software |