I appreciate the feedback.
Can you log bugs on sourgeforge for both issues you mentioned. I'm looking at
putting some significant time into fixing bugs in WiX over the next few months
and its easiest for me to track all of them if they are all logged on
sourceforge.
With bugs, you will also be
eter Marcu" <[EMAIL PROTECTED]>; "Bob Arnson"
<[EMAIL PROTECTED]>; "Cristian Baiu" <[EMAIL PROTECTED]>
Cc:
Sent: Tuesday, October 02, 2007 8:24 PM
Subject: RE: [WiX-users] Fw: Some STUPID Limitations in WiX
I meant pyro when I said torch below.
-Origin
has a different product code.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Tuesday, October 02, 2007 9:07 AM
To: Cristian Baiu
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Fw: Some STUPID Limitations in WiX
Cristian Baiu
erent product code.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Tuesday, October 02, 2007 9:07 AM
To: Cristian Baiu
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Fw: Some STUPID Limitations in WiX
Cristian Baiu wrote:
>
Cristian Baiu wrote:
> So far I don't know how to instruct pyro to address my patch to all
> MSIs unless I make differences for
> all of them and pass all these difference sets to pyro.
> Can you please advice me if it's possible to target multiple MSIs with
> only one set of differences and how ?
Cristian N. Baiu wrote:
> My question regarding patching the msm is: if I create a patch for adressed
> to only one of the products which patches a MSM component and the patch is
> applied to a machine were two products containing the MSM's components are
> installed then will the patch update t
6 matches
Mail list logo
