Geek Answers Handbook

Distribution of VC ++ Redist ... the running installer, when it is already installed, causes problems

Using the Inno installer, we distribute the VC ++ redistributable with our application so that we can run it automatically. We found that running it on a system where it is already installed requires us to restore / cancel the installation, which will completely confuse users.

Is there any way around this? Maybe the flag in the installer or something like that?

Thanks.

+6
installer visual-c ++ visual-c ++ - installer
source share
4 answers

Try the / q flag http://support.microsoft.com/kb/227091 (assuming you install it by calling msiexec.exe on their redistributable)

+4
source share

For some reason, none of the above answers worked for me. This happened, however:

[Run] Filename: {tmp}\vcredist_x86.exe; Parameters: "/passive /Q:a /c:""msiexec /qb /i vcredist.msi"" "; StatusMsg: Installing 2010 RunTime... [Files] Source: vendor/vcredist_x86.exe; DestDir: {tmp}

I got a hint for this by running vcredist_x86.exe /? As noted at the bottom of this thread: http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/a8d4d5b4-7927-4c86-95e8 -3cd8b3018ae8 /

As another note, another possible option for redistribution is just a static link against (your version) msvcrt to see comments at http://blogs.msdn.com/b/vcblog/archive/2007/10/12/how -to-redistribute-the-visual-c-libraries-with-your-application.aspx (although MS seems to frown on this type of static binding, at least you won't need a dll).

Distributing Visual C ++ Runtime Libraries (MSVCRT) can also be useful.

Also note that if you can guarantee that you will have control, you can simply include msvcr100.dll in the same directory as your executable file, and this will work, although this is not a very standard solution.

+3
source share

This thread solved my problems:

(taken from the comment in another answer)

+1
source share

Although this is not for the Inno installer, this related question provides a solution for the Visual Studio 2010 installation project. The problem is that SP1 vcredist changed the product code while Visual Studio uses the old code. This is why the installed check failed.

Visual C ++ 2010 Runtime Library Prerequisites Continue to Appear in the Created VS 2010 Installer

0
source share

More articles:


All Articles