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.
do not replace files on a second install
Started by
bruno_pt-br
, Jul 15 2009 14:23
5 replies to this topic
Posted 15 July 2009 - 14:23
Hello people,
i have the following situation:
i have a setup where a component is with "never overwrite" and "Shared" set to "Yes" and it saves a xml file. After the install, i modified that xml and uninstall the product.
the folder with that .xml was not removed.... until that, it's good for me...
but when i make a second install, that .xml is replaced... and i want that the file not be replaced because that one i edit is newer than that one in the setup...
i hope i made myself clear...
somebody can help me?!
thanks
i have the following situation:
i have a setup where a component is with "never overwrite" and "Shared" set to "Yes" and it saves a xml file. After the install, i modified that xml and uninstall the product.
the folder with that .xml was not removed.... until that, it's good for me...
but when i make a second install, that .xml is replaced... and i want that the file not be replaced because that one i edit is newer than that one in the setup...
i hope i made myself clear...
somebody can help me?!
thanks
Posted 16 July 2009 - 14:12
Sounds weired. Did you create a log file of your second install?
Stefan Krüger
InstallSite.org twitter facebook
Posted 16 July 2009 - 14:59
Hello Stefan,
thanks for the answer... i copy this part of the log file. i think that this part is the most important, but i don't know if can help...
MSI (s) (24:C4) [10:53:28:021]: Executing op: FileCopy(SourceName=CUSTOM~1.XML|Configuracoes.xml,SourceCabKey=_84C2C14D91A946169A20A5379CDF2CAA,DestName=Configuracoes.xml,Attributes=16384,FileSize=113,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=62914560,HashOptions=0,HashPart1=-1628624069,HashPart2=1570965869,HashPart3=-1729940306,HashPart4=-875788504,,)
MSI (s) (24:C4) [10:53:28:021]: File: E:\Program Files\New Folder\Configuracoes.xml; Overwrite; Won't patch; REINSTALLMODE specifies all files to be overwritten
can help?
thanks
thanks for the answer... i copy this part of the log file. i think that this part is the most important, but i don't know if can help...
MSI (s) (24:C4) [10:53:28:021]: Executing op: FileCopy(SourceName=CUSTOM~1.XML|Configuracoes.xml,SourceCabKey=_84C2C14D91A946169A20A5379CDF2CAA,DestName=Configuracoes.xml,Attributes=16384,FileSize=113,PerTick=32768,,VerifyMedia=1,,,,,CheckCRC=0,,,InstallMode=62914560,HashOptions=0,HashPart1=-1628624069,HashPart2=1570965869,HashPart3=-1729940306,HashPart4=-875788504,,)
MSI (s) (24:C4) [10:53:28:021]: File: E:\Program Files\New Folder\Configuracoes.xml; Overwrite; Won't patch; REINSTALLMODE specifies all files to be overwritten
can help?
thanks
Posted 17 July 2009 - 15:15
QUOTE |
REINSTALLMODE specifies all files to be overwritten |
Looks like your REINSTALLMODE includes "a" (for all files"). If it's set to "amus" change it to "omus".
Stefan Krüger
InstallSite.org twitter facebook
Posted 21 July 2009 - 15:46
hello Stefan,
i understood what you post, but the strange is that i have another setup here (reinstallmode = "amus") that have a component with "never overwrite" set "yes". This component has a .config file and in a second install, this file is not replaced.
i understood what you post, but the strange is that i have another setup here (reinstallmode = "amus") that have a component with "never overwrite" set "yes". This component has a .config file and in a second install, this file is not replaced.
Posted 22 July 2009 - 17:32
"Never overwrite" only checks the key file. If the config file marked as key file of the respective component?
Note that you cannot change the key file selection in a small or minor update though!
Note that you cannot change the key file selection in a small or minor update though!
Stefan Krüger
InstallSite.org twitter facebook