WiX deliberately does not have any mechanism for automatically collecting
files because it's way too easy to break component rules. My initial guess
would be that you've added them to an existing component (which it is
strongly recommend you avoid) but the key file of that component isn't
changed,
;ll take a look.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Blankley
Sent: Monday, October 15, 2007 11:25 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Files in xml not being installed
Below is the output from 2 files.
t might already be on your system.
-Matt
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Blankley
Sent: Monday, October 15, 2007 11:25 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Files in xml not being installed
Below is th
Blankley
> Sent: Monday, October 15, 2007 10:58 AM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Files in xml not being installed
>
> Chad: Thanks for the suggestion.
> Unfortunately, the files that fail to be newly incorporated spit out the
> exact same inf
Component: ExceptionReport1098rox_26;
Installed: Absent; Request: Local; Action: Local
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Blankley
Sent: Monday, October 15, 2007 10:58 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Files in xml
Chad: Thanks for the suggestion.
Unfortunately, the files that fail to be newly incorporated spit out the
exact same info as files that were part of the original msi.
What's also weird is that there seems to be no consistency to this. Other
files are added fine (but not in that directory).
dir
Anytime I have anything odd going on I always look to a verbose log file
first.
MSIEXEC /L*v /I
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David
Blankley
Sent: Monday, October 15, 2007 7:04 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-use
7 matches
Mail list logo