Another Richard wrote:
> There are times when I think the "unzip files" approach is legitimate.
> For instance, suppose you have a bunch of data files that represent a
> snapshot in time for a dynamically updating service. The service,
> when run, will consume the initial snapshot of files to bu
Ben Greenberg wrote:
> I can't understand why anyone would want to add the complexity of an unzip
> call into an MSI. It doesn't make sense.
Most of the time, you're right it doesn't.
I can see scenarios where an application is distributed to resellers who then
rebrand the software (hopefully
Dana wrote:
The best practice is not to use C# managed custom actions at all. If
you search an archive of this list here:
http://www.nabble.com/wix-users-f4470.html, you'll see plenty of reasons
why this is stated.
This is not a limitation of WiX, but rather a requirement imposed upon
all of
Dan,
I believe the information you need is also captured on the WiX wiki -
see http://wix.mindcapers.com/wiki/ICE38
Hope this helps,
Regards,
Richard
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dan Hoeger
Sent: Thursday, February 21, 2008 3:
Jeremy,
Just for stupidity's sake, is everything OK if you reverse the order of
the second test?
I.e. the second test would become:
Unless I'm missing something, the file would then be "valid" again,
since the product element is opened before the module element could
possibly b
My guess would be that the intention was that wix input files should be
valid xml. In your case, the initial file wasn't (even though the
"effective" file, after post-processing, would have been).
Personally, I wouldn't consider that a defect, more a case of "that's
how it works". :-)
Regar
Rob wrote:
I'm still very hesitant to [lock out posting by non subscribers] since
it raises the bar for people just starting to get involved with WiX (and
we don't need to make anything *harder* ).
While I understand the sentiment, the large quantities of spam probably
reduce the number of people
John Vottero asked:
What will keep the spammers from joining the list?
Absolutely nothing, but spammers are (generally) a lazy bunch and won't
do anything more than they have to. Most of the other SourceForge based
groups I subscribe to are locked to subscriber only posting, and they
have *signifi
Bob,
>From my POV, I'd say that having the option on should be the default,
but allow for it to be disabled.
I don't know if it is a good idea or not... but it might also be nice to
have a way to disable the option easily for multiple files, but not
necessarily all files, in a WiX fragment - I.e.
I'd say there's a 90+% chance we'd be getting that support call anyway,
just because the message appeared in the first place!
For some reason our customers always assume that because it's our
installation, anything that goes wrong *has* to be our fault... even
when they haven't followed the ins
101 - 110 of 110 matches
Mail list logo
