This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: What is the command line to pass the .ini file with all install property values.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 07, 2013
01:09 PM
What is the command line to pass the .ini file with all install property values.
Hello,
I have a Basic MSI installer and would like to create an .ini file that has all install property values, such as INSTALLDIR, USERNAME, _IsSetupTypeMin, etc. During the install, is there a command line to pass in after .exe so that it will read the default value from each property inside the .ini file first and pre-filled the value in the installation? Not silent but in normal mode. But values should be read and fill from .ini.
Thanks in advance,
T.
I have a Basic MSI installer and would like to create an .ini file that has all install property values, such as INSTALLDIR, USERNAME, _IsSetupTypeMin, etc. During the install, is there a command line to pass in after .exe so that it will read the default value from each property inside the .ini file first and pre-filled the value in the installation? Not silent but in normal mode. But values should be read and fill from .ini.
Thanks in advance,
T.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 11, 2013
09:03 AM
Basic Msi's don't use response files. They do use public properties which can be passed in when running from the command-line. You might look at "command-line options [Windows Installer]" in the InstallShield Help for hints on how you might do this.
It is possible, however, to create a response-type file for your MSI by creating your file as you suggest in and .ini or .xml format and then creating a first action custom action which reads the file when present and assigns its values to your properties. I have done this in the past, typically using an .xml file where property values are defined. If the project is a Setup.exe, you can have your custom action look for your file in the SETUPEXEDIR, if found, read it's values and assign them.
It is possible, however, to create a response-type file for your MSI by creating your file as you suggest in and .ini or .xml format and then creating a first action custom action which reads the file when present and assigns its values to your properties. I have done this in the past, typically using an .xml file where property values are defined. If the project is a Setup.exe, you can have your custom action look for your file in the SETUPEXEDIR, if found, read it's values and assign them.