I have a installshield installer that couldn't be totally silently installed(setup.exe /s /f1"install.iss") because it always call the vc++ runtime redistribution in GUI mode. Is there a way to suppress the detection for this vcredist_x86.exe ? Thanks in advance.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
It seems that the setup.exe is extracting the msi files 2 approaches
1) extract the vc++ redist and install it first and then call the setup silently should work
2) check if the application is also extracted as a msi then you can use vc++ and application msi for silent installation

Both depend on what way you would like to deploy the application and what are the packaging tools available at hand
Answered 05/18/2011 by: rajdera1
Orange Belt

Please log in to comment
0
Thanks for your reply!
1> the problem is the after I install this vc++ redist, the installer still call it in GUI Mode. This is it show a maintenance window of vc++ redist.

2> No , it doesn't extract a msi installer.

Any other suggestions ?
Answered 05/19/2011 by: Savage455
Orange Belt

Please log in to comment
0
The behavior you described seems very strange to me. Why should an installer ALWAYS start the installation of the vcredist runtime causing a maintenance screen if it's already on the pc? Often there is a configuration file to suppress it (ini, cfg etc). But because it's a setup.exe (black-box) you never know how crap the installer is made.

I would ask the vendor how to suppress the vcredist installation. Because it's not a msi maybe repackaging is an option?
Answered 05/19/2011 by: pjbaars
Orange Belt

Please log in to comment
0
thanks. Go to the vendor is a solution. Also I came up a ugly workaround: use a vbs script to run before the setup.exe . when it calls the vc++ redistribution, It kill the process and exit and the installation goes on.
Answered 05/19/2011 by: Savage455
Orange Belt

Please log in to comment
0
You can also perform a check (in a wrapper vbscript or something) before installation wheter the vcredist is installed or not and if so, uninstall it. If not the installation can continue.
Answered 05/19/2011 by: pjbaars
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity