Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Never overwrite one or two files

Updated: 21 May 2010 | 4 comments
DomC's picture
0 0 Votes
Login to vote

I have an MSI install where a user's 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 user's profile.

discussion Filed Under:

Comments

PuterFix's picture
28
Oct
2008
0 Votes 0
Login to vote

Never Overwrite Component Setting

Hi,

To do this make sure the files you don't want to overwrite are in their own components. Then if you go into the component details there is an option to "Never overwrite is key path exists".

For example if there is a file called settings.xml that may be on the computer the in your package make sure the settings.xml file is in it's own component and set it as the key path. Then tick the box mentioned above. If you tick this option it is important that there are no other files that are needed in this component as it is the whole component that will not install.

I hope that all makes sense and helps :-)

Justin

He who dies with the most toys wins!!

He who dies with the most toys wins!!

siddi's picture
29
Oct
2008
0 Votes 0
Login to vote

companion file

another method could be the use of companion files. You can make a companion file for this,this file will only be replaced if the companion file is updated...you can read more about this concept in the help files of wise..
Cheers, Siddi

Rgds, Siddi

Lets share and encourage knowledge..

piyushnasa's picture
29
Oct
2008
0 Votes 0
Login to vote

I think otherwise

The use of companion file will make the file to be replaced, however the requirement here is not to replace the older file. I think the option mentioned of checking option of component, not to install if key path exists, by Justin is the correct way to use it. If you could have used REINSTALLMODE then option pmus would have been a good option.

Piyush Nasa Altiris Certified Professional (ACP)

http://msiworld.blogspot.com/

siddi's picture
29
Oct
2008
0 Votes 0
Login to vote

with an eg

What I meant here is to make a file companion(eg, exe, whose version is not changed or updated) which is not changing.If the companion file is not changed then the file will not be replaced. The method to be used also depends on the further maintenance of the application.

Rgds, Siddi

Lets share and encourage knowledge..

Rgds, Siddi

Lets share and encourage knowledge..