I have MSI setup project created in VS2008.
The next properties - 'RemovePreviousVersions ' and 'DetectNewerInstalledVersion' - are set to 'true'.
'Version' - 1.0.3 - is incremented before every build, and as result 'ProductCode' is changed too.
The files of periously installed version are NOT overwritten !!!
Is there any proper solution?
I currently start the setup with bat file with the next command line inside:
setup.exe REINSTALLMODE=amus
but it is annoying way because of dealing of black dos window/
I tried to change parameters inside msi file (with Orca) without effect.
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
RemovePreviousVersions or REINSTALLMODE
Started by
Yehuda
, Aug 16 2011 07:56
2 replies to this topic
Posted 19 August 2011 - 06:40
Effectively, what you are creating is as Major Upgrade since you are changing the Product Version and the Product Code(GUID). But you have not mentioned anything about what you are doing with the Upgrade table.
It would be of immense help if you fill the Upgrade table so as to create a Major Upgrade. This will help you to avoid REINSTALLMODE and the CLI.
This should be the proper solution, in my opinion.
It would be of immense help if you fill the Upgrade table so as to create a Major Upgrade. This will help you to avoid REINSTALLMODE and the CLI.
This should be the proper solution, in my opinion.
Posted 22 August 2011 - 16:27
As far as I know Visual Studio will create the Upgrade table entry if these flags are set. So a log file should help.
Note that the version resource in each changed file also needs to be incremented.
Note that the version resource in each changed file also needs to be incremented.
Stefan Krüger
InstallSite.org twitter facebook