On 17-Sep-10 14:17, Oleksandr Y. Nechyporenko wrote:
> I've assumed that it is a good idea to group files which used for same
> function into one component.
Not if you want to patch them independently.
> Anyway it seems to be a problem with pyro.exe when RegistryValue is used as
> keypath.
You
_id=105970&ati
d=642714
--
Best Regards,
Oleksandr Y. Nechyporenko
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Friday, September 17, 2010 7:43 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Warning 21 File in Com
On 16-Sep-10 09:08, Oleksandr Y. Nechyporenko wrote:
> Since RegistryValue allowed as KeyPath, there should be way to notify that
> KeyPath file was changed, but I can't understand how to do it.
It's allowed but that doesn't mean it's a good choice. If you want to
create patches, use one file p
@gmail.com]
Sent: Thursday, September 16, 2010 14:18
To: 'General discussion for Windows Installer XML toolset.'
Subject: [WiX-users] Warning 21 File in Component was changed,but the
KeyPath file was not
Thanks Yan,
We have more than 500 files in installer, and most of them can be
chan
ws Installer XML toolset.'
Subject: [WiX-users] Warning 21 File in Component was changed,but the
KeyPath file was not
Thanks Yan,
We have more than 500 files in installer, and most of them can be
changed
separately, I don't think that it to create new component for every
file.
Ov
Thanks Yan,
We have more than 500 files in installer, and most of them can be changed
separately, I don't think that it to create new component for every file.
Overall my main question, if I use Registry Entry as KeyPath like
What part of this RegistryValue I should change in next build to
6 matches
Mail list logo