Launch Window Installer as part of MSI
Dear All
I have an MSI which is checking for Window Install minimum 3.0 and if it does not exists on the system then Installs it.
Problem : I have the exe as part of MSI but each time when I run MSI it runs the Windows Install 3.0 installer, but I only wants to run it if it is required to be.
Thanks in Advance
I have an MSI which is checking for Window Install minimum 3.0 and if it does not exists on the system then Installs it.
Problem : I have the exe as part of MSI but each time when I run MSI it runs the Windows Install 3.0 installer, but I only wants to run it if it is required to be.
Thanks in Advance
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
timmsie
13 years ago
Posted by:
Ash786
13 years ago
Sorry lads I am not too expert in package installer. I was asked to do few small jobs while we are looking for someone with the experience. I have done the following
1) Set the System Requirement Windows Installer Runtime Version = Runtime version 2.0 or higher
2) Added Execute program from installation just after validate tag in Execute Immediate tab
Now if I run my MSI which has the Windows Installer Runtime 3.0 the MSI still launches "Execute program from installation" . I want to add a condition which should do the following but I am not sure how to do this
Check if Windows Installer Runtime => 2.0 Then
Do Nothing
Else
"Execute program from installation"
I hope I am making sense here :)
1) Set the System Requirement Windows Installer Runtime Version = Runtime version 2.0 or higher
2) Added Execute program from installation just after validate tag in Execute Immediate tab
Now if I run my MSI which has the Windows Installer Runtime 3.0 the MSI still launches "Execute program from installation" . I want to add a condition which should do the following but I am not sure how to do this
Check if Windows Installer Runtime => 2.0 Then
Do Nothing
Else
"Execute program from installation"
I hope I am making sense here :)
Posted by:
rakesh.kumar
13 years ago
Posted by:
thugz888
13 years ago
Posted by:
mazessj
13 years ago
Adding to timmsie's suggestion...
You should avoid embedding an installer within an installer, especially a Windows Installer engine update. The Windows Installer update could cause the Windows Installer engine to become unavailable until you reboot. Also, the Windows Installer update can't replace the files in the current session if they're in use.
If you enable the .EXE option in Build Options, you can use the Prerequisites page in Installation Expert to specify which runtime installer(s) to include with your package.
You should avoid embedding an installer within an installer, especially a Windows Installer engine update. The Windows Installer update could cause the Windows Installer engine to become unavailable until you reboot. Also, the Windows Installer update can't replace the files in the current session if they're in use.
If you enable the .EXE option in Build Options, you can use the Prerequisites page in Installation Expert to specify which runtime installer(s) to include with your package.
Posted by:
Ash786
13 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.