Always update files with minor updates (how)

I am creating an installation package using InstallShield Pro X. The update works correctly. However, the product manager wants the update to replace all files during the update, even if the creation date! = Change the date in the file.

I see that for this I need to set REINSTALLMODE = vamus, not vomus. However, I do not see how to tell InstallShield that I want it to use this setting. By default, setup.exe always passes vomus to the Windows installer.

There is a property in the InstallShield project called ReinstallModeText that I changed from omus to amus, but this did not seem to have an effect.

So, how do I install in the installation project, so that upon detection of setup.exe, it sends REINSTALLMODE = vamus to start the update? Thanks.

Update: I tried adding the following to the MSI command line value in the Release section:

REINSTALLMODE = vamus

This did not work. Setup.exe did not set REINSTALL = ALL on the command line, so I did it. I added that on the MSI command line and the update worked as expected. But the problem is not that it is NEW, these parameters are still set and the setup program fails.

+3
source share
4 answers

Studying this and testing more options, I think that the best answer is to change the product code in addition to the product version and author it as a major update, which first removes the previous version and then installs new files.

, . , , .

+2

REINSTALLMODE amus vamus ( ). MSI , , , , - , . REINSTALLMODE emus ( ). , Windows Windows (wikipedia) (Windows Server 2008 Vista). Windows , , , dllcache Windows, . ( ): System File Checker.

, , , RemoveFile, ( ).

, % ProgramFiles% , . alluser, EXE- .

.

+3

IS X, InstallShield "", , "Setup.exe" " MSI", , Setup.exe Windows Installer. . REINSTALLMODE = vamus

+1

, ReinstallModeText "amus". ModeText "vamus". "V" , , .

+1

Source: https://habr.com/ru/post/1709535/


All Articles