InstallShild not creating proper .ISS file
I have an InstallShield .EXE. I run this with a -r to create the setup.iss file. The setup.exe runs, launches an .MSI and once the .MSI runs I enter some information. "server name" "location" etc... The .MSI finishes and the software is installed. I then go to c:\windows\ and I find my setup.iss but it does NOT contain the "server name" or the other custom information that was entered into the .MSI install.
Why? What would cause that to happen?
-
Well, as you said, the exe launches an MSI , so you have your answer in first place. So i would suggest you to look into %TEMP% folder for the presence of the MSI. and then take the verbose log for the setting that you wish to have in the MSI. If you are planning to deploy msi silently i can be done too. In a nutshell, i dont feel the necessity of the ISS file, unless its just the EXE that installs the application. - talonsprem87 11 years ago
Answers (2)
setup.iss just captures dialogs directly related to the setup.exe. If an msi is launched outside of this process then it wouldn't capture those selections.
If there are only 1 msi (or if you are lucky and its the first one run) you can use the /v switch to pass either an mst for the msi or other msiexec based commands like setting properties (which hopefully the server would have one).
See http://kb.flexerasoftware.com/doc/Helpnet/installshield12helplib/IHelpSetup_EXECmdLine.htm#wp1021759
.iss only works for .EXE files. If the MSI is launching that is why the .iss isn't capturing anything. You won't need the .iss file to manipulate the .MSI
Research a little more about the software you are working with and see if the MSI has commands you can pass in to edit the settings during installation that you need (like server name or whatever)
If not, then use a transform file (.MST) which is purposely used for configuring .MSI settings.
