silently install vcredist pre-requisites - Advanced Installer Community
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

silently install vcredist pre-requisites

I seem to be struggling finding the correct Silent (no UI) settings for installing these two prerequisites so that they occur "unattended":

Visual C++ 2008 SP1 Redistributable
Visual C++ 2010 SP1 Redistributable x86

I don't mind if the user sees a progress bar, but they should not be required to do any clicks and should not have the ability to cancel.

Can anyone help?

Thanks.
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: silently install vcredist pre-requisites

Hi,

I recently worked a lot with the redistributables for VC++ 2012 and 2005, so I can tell you the command lines used for them, maybe they work for your versions too.

- for 2012 I used the simple command line: /install /quiet

- for 2005 I used this command line: /q:a /c:"VCREDI~2.EXE /q:a /c:""msiexec /i vcredist.msi /qn"" "
As this installer is actually a self extraction EXE which does not executes the MSI, you have to call the MSI specifically from the command line

What Is VERY important, if you place both packages in the same Advanced Installer project, rename one of them or set them different extraction folders
in the Setup Files tab of each prerequisite. This is mandatory because the setup package built extracts the prerequisites into a single folder by default,
so if you have two prerequisites with the same name one of them will get overwritten when extracted and the installer will not work correctly.

Here is a blog with installer resources that might interest you:
http://blogs.msdn.com/b/astebner/archiv ... ageIndex=2
http://blogs.msdn.com/b/astebner/archiv ... ageIndex=4

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Re: silently install vcredist pre-requisites

Hi Bogdan,
Thank you. That makes perfect sense, because my second of the two redist EXEs was the only one that was getting installed. So I will take your rename advice and see; I have called the 2008 redist "vcredist_x86_vs2008sp1_MFC_SecUp.exe", and the 2010 redist "vcredist_x86_vs2010sp1_MFC_SecUp.exe" and placed those source files in the same "Prerequisites" folder, hopefully that is OK since their names are now different.

I do know from prior (other, older) Installer experience that the command line for the silent install of these two redist's have been as follows

Code: Select all

vcredist_x86_vs2008sp1_MFC_SecUp.exe /qb!
vcredist_x86_vs2010sp1_MFC_SecUp.exe /passive /norestart
Ok, that worked. Giving them different names was key. And the switches I mentioned above gave me the effect I was looking for which was to prevent the user from having to or being able to interact with those redist installs.

(SIDENOTE:Wouldn't it be nice if MS would maintain some consistency with these switches? Or at least make the newer ones be backward compatible with the old ones...but I digress. :lol: )

Return to “Common Problems”