> I'd guess it's a timing problem: MSI decides what it needs to do
> based
> on the state of the machine during script generation. It sees
> sampledb.txt on the machine in the right place with the expected
> content/timestamp and says "nothing to do." You then move it but MSI
> has
> already made
Ilya Slobodin wrote:
> SampleDb.txt is renamed to SampleDb.bak while the original file SampleDb.txt
> is not reinstalled (confusing)
>
I'd guess it's a timing problem: MSI decides what it needs to do based
on the state of the machine during script generation. It sees
sampledb.txt on the mach
> What does a verbose log say for the action state of that component?
Attached two grepped logs with different arguments, with and without
REINSTALL=ALL REINSTALLMODE=omus
1. msiexec /update Patch\Patch.msp /lv* Logs\PatchGood.log
File Sample.txt is patched
File SampleDb.txt is not touched (as e
Ilya Slobodin wrote:
> But, this solution looks like a workaround. Most likely this is not
> WiX but Windows Installer issue. Is this planned behavior or not?
>
I don't know -- I'm not on the Windows Installer team.
> That is correct. And I expect that since MoveFile record references
> the co
Hello Bob,
> I'd suggest creating a separate component for the backup
> and give it a condition of NOT PATCH.
Thanks for the solution. I added a new component witn CopyFile and
made it transitive. Now everything works as expected.
But, this solution looks like a workaround. Most likely this is n
Ilya Slobodin wrote:
> 1. Get the patch installed and
> 2. Keep the database file and
> 3. Keep using the MoveFile table to backup the database
>
> I have nothing against using REINSTALL & REINSTALLMODE. But, if set,
> MoveFile to Component action state relationship is broken, file is moved but
>
Bob,
Yes, I understand that I need the right arguments set from either
bootstrapper or command line. But, the question is what are these right
arguments. I need to:
1. Get the patch installed and
2. Keep the database file and
3. Keep using the MoveFile table to backup the database
I have nothi
Subject: Re: [WiX-users] Patch install: MoveFiles and component action states
Ilya Slobodin wrote:
> Any ideas how to avoid REINSTALL & REINSTALLMODE and install the patch?
>
Minor upgrades, whether in .msi or .msp forms, require those properties.
Generally patches are delivered as wrapp
Ilya Slobodin wrote:
> This makes MoveFile table completely non-functional when the file
> being moved is not included in the patch.
No, it means that without the right arguments, the patch isn't being
processed as you expect.
--
sig://boB
http://joyofsetup.com/
bodin
- Original Message -
From: "Bob Arnson" <[EMAIL PROTECTED]>
To: "General discussion for Windows Installer XML toolset."
Sent: Thursday, July 10, 2008 7:53 PM
Subject: Re: [WiX-users] Patch install: MoveFiles and component action
states
> Ilya Slobodi
Ilya Slobodin wrote:
> Any ideas how to avoid REINSTALL & REINSTALLMODE and install the patch?
>
Minor upgrades, whether in .msi or .msp forms, require those properties.
Generally patches are delivered as wrapper .exes to execute the patches
with the right command-line arguments.
--
sig://b
Sorry for the mistake in the explanation.
The problem does not depend on UI, it depends only on REINSTALL &
REINSTALLMODE
I have to use the following command line to get my update installed:
msiexec /passive /update Patch.msp REINSTALL=ALL REINSTALLMODE=omus
Best regards,
Ilya Slobodin
---
Hello,
I have modified the Sample Patch by Peter Marcu to test all the cases.
The MoveFile problem happens only if
1. Installer has UI
2. msiexec /update Patch.msp REINSTALL=ALL REINSTALLMODE=omus is used
The sample has no UI, so the simplest command line installs the update.
msiexec /update P
Hello,
We have a database file
The database file can be modified by user, on reinstall the modified
file is renamed to db.bak and original file is copied on it's place.
Everything worked well until I made the patch file that modifies
another file, e.g. somecode.dll.
During the pat
14 matches
Mail list logo
