Basically you are right (though in this case all what you pointed out
does not apply). But it makes me think that this is a serious problem
for any installer. I mean if someone wants to sabotage an install, all
it has to do is to place bogus exe files, with the same name as the
installed ones in th
János Brezniczky wrote:
> Let's assume the file has been successfully replaced by the new "version".
> Should that new version be later uninstalled together with the package which
> overwritten it?
>
>
> 2007/11/29, Szentpali Janos <[EMAIL PROTECTED]>:
>
>> I have an executable x.exe that I need
Let's assume the file has been successfully replaced by the new "version".
Should that new version be later uninstalled together with the package which
overwritten it?
2007/11/29, Szentpali Janos <[EMAIL PROTECTED]>:
>
> I have an executable x.exe that I need to install over x.exe if it
> already
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darrell
([EMAIL PROTECTED])
Sent: Friday, August 24, 2007 1:36 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Overwrite an Existing File (More Info)
Looking into this I found the following from the Windows Installer Log.
MSI (s) (BC:A8)
ied - hash
matches source file"
Phil Wilson
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Darrell
([EMAIL PROTECTED])
Sent: Friday, August 24, 2007 1:36 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Overwrite an Existing File (Mo
Looking into this I found the following from the Windows Installer Log.
MSI (s) (BC:A8) [16:12:38:802]: Executing op:
FileCopy(SourceName=iumwmdfq.con|docinfo.exe.config,SourceCabKey=config,DestName=docinfo.exe.config,Attributes=512,FileSize=11567,PerTick=32768,,VerifyMedia=1,CheckCRC=0,,,Ins
6 matches
Mail list logo
