I have an MSI install where a user configuration text file(s) must not be overwritten, even though it might be older then the new file.
I do not want to change the REINSTALLMODE for the entire install.
I am running Wise Package Studio 5.1
We always do a "remove previous products" as part of every install.
I assume that this file(s) will not get uninstalled, since it was at one time changed by the user.
But now the new install will see it as an old file..... Correct?
These file(s) maybe under "Program Files" or in the users profile.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


The simplest route is to mark the component so that it remains during an uninstall. Also, presuming that the file has no version information, you can 'touch' its "Modified" date with an obviously old date/time. I normally use 01-01-1980. If the user has updated the file at all, the date will be current and thus not overwritten.
Answered 10/13/2008 by: VBScab
Red Belt

Please log in to comment
you could use APPSEARCH to lookup the file existance. If it exists set a PROPERTY such as FILEEXISTS=true then set a condition on the component to match

Component blah , Condition = "FILEEXISTS~=true"

should suffice
Answered 10/13/2008 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment