Often we come across situations like how to update MSI properties during setup installation, which we may have hard coded at design time. It takes a lot of time to search in the help sections, or on Google, if the solution is needed in a go. Here is a way how to do that, which I had implemented a lot of times. Any better way is most welcomed.
Like your compiled .msi file, setup.exe can accept a number of command-line parameters.
With these parameters, we can specify data such as which language installer should run in, and whether to run setup.exe silently.
NOTE:
Command-line options that require a parameter must be specified with no space between the option and its parameter. For example, Setup.exe /v"ALLUSERS=2" is valid, while Setup.exe /v "ALLUSERS=2" is not. Quotation marks around an option's parameter are required only if the parameter contains spaces. If a path within a parameter contains spaces, you may need to use quotation marks within quotation marks, as in the following example: Setup.exe /v"INSTALLDIR=\"c:\My Files\"".
Ex:
setup.exe /v"MSIPROPERTY=Value"
where, MSIPROPERTY is any Msi Property setup inside the installer code.
More help on command line options
Like your compiled .msi file, setup.exe can accept a number of command-line parameters.
With these parameters, we can specify data such as which language installer should run in, and whether to run setup.exe silently.
NOTE:
Command-line options that require a parameter must be specified with no space between the option and its parameter. For example, Setup.exe /v"ALLUSERS=2" is valid, while Setup.exe /v "ALLUSERS=2" is not. Quotation marks around an option's parameter are required only if the parameter contains spaces. If a path within a parameter contains spaces, you may need to use quotation marks within quotation marks, as in the following example: Setup.exe /v"INSTALLDIR=\"c:\My Files\"".
Ex:
setup.exe /v"MSIPROPERTY=Value"
where, MSIPROPERTY is any Msi Property setup inside the installer code.
More help on command line options