for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module Help
What feedback? All I saw was a childish quip/troll post.
Personally I'm sick of the component rules and it's associated gotchas. These
are artificial problem caused by an overly complicated design.
Developers want
John Hall wrote:
I have written a tool that auto-generates .wxs files for some parts of
my project - we ship a lot of example scripts. It only handles files and
generates one component per file. The tool maintains a database (well,
an XML file) that lists all the GUIDs ever allocated, and adds
: Bob Arnson [EMAIL PROTECTED]
Subject: Re: [WiX-users] Merge Module Help
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Date: Wednesday, July 23, 2008, 9:32 AM
John Hall wrote:
I have written a tool that auto-generates .wxs files
for some parts
Christopher Painter wrote:
This would be a pretty easy scenario to handle. Check the WXS against the
XML and if a component is missing, throw an error and suggest the puncture
component pattern ( transitive=true condition=false, 0 byte files for
storage )
Throw an error isn't the
FWIW, I personally would rather manage the process by exception, instead of
*always*.
Chris
On Wed, Jul 23, 2008 at 11:33 AM, Bob Arnson [EMAIL PROTECTED] wrote:
Christopher Painter wrote:
This would be a pretty easy scenario to handle. Check the WXS against
the XML and if a component is
that declares the event as a warning and
automatically implements the punctured components pattern but I think that
assumes too much that the missing file is correctly missing.
--- On Wed, 7/23/08, Bob Arnson [EMAIL PROTECTED] wrote:
From: Bob Arnson [EMAIL PROTECTED]
Subject: Re: [WiX-users] Merge
Christopher Karper wrote:
FWIW, I personally would rather manage the process by exception, instead of
*always*.
Yes, some help is usually better than none.g It's all about managing
expectations. If it's possible to automatically generate the original
setups, not being able to generate
I was thinking that the missing file would be the exception. Can you clarify
what you have in mind?
--- On Wed, 7/23/08, Christopher Karper [EMAIL PROTECTED] wrote:
From: Christopher Karper [EMAIL PROTECTED]
Subject: Re: [WiX-users] Merge Module Help
To: General discussion for Windows
Christopher Painter wrote:
Once again you pedantically pick through my comment without actually offering
anything constructive yourself.
Wow, I'm really put in my place, aren't I?
--
sig://boB
http://joyofsetup.com/
-
John Hall wrote:
I have written a tool that auto-generates .wxs files for some parts
of my project - we ship a lot of example scripts. It only handles
files and generates one component per file. The tool maintains a
database (well, an XML file) that lists all the GUIDs ever
allocated,
John Hall wrote:
Ah, we don't do patches, which is why it works for me :)
That's also an option.g That's what ClickThrough does, using early
major upgrades every time. In that case, you don't even need stable IDs.
--
sig://boB
http://joyofsetup.com/
.
Thank you.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Wednesday, July 23, 2008 08:54
To: [EMAIL PROTECTED]
Cc: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module Help
Christopher Painter wrote
XML toolset.
Subject: Re: [WiX-users] Merge Module Help
John Hall wrote:
Ah, we don't do patches, which is why it works for me :)
That's also an option.g That's what ClickThrough does, using early
major upgrades every time. In that case, you don't even need stable IDs.
--
sig://boB
http
using auto-generated-stable Guids?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Hall
Sent: Wednesday, July 23, 2008 01:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module Help
The case that gets
the
Component/@Guid creates.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Wednesday, July 23, 2008 08:47
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module Help
Christopher Karper wrote
1. How do you manage updates to the database in source
control? Do people update the file before building or does
the build machine checkout/checkin automatically? If the
latter, what source control systems does it support... (you
can see where I'm going smile/)?
We use cvsnt as our
PROTECTED]
Subject: Re: [WiX-users] Merge Module Help
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Date: Wednesday, July 23, 2008, 11:39 AM
Hey, wait a minute here.
First, Automating Component/@Guids requires a bullet-proof
solution. The side
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Merge Module Help
That's an excellent point. The devil, as always, is in the details of when
someone screws up. Since Murphy is looking out for us, it never manages to
work ideally. :)
-Jamey
/2008 21:11
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Merge Module Help
Based on what people said in earlier messages, I'm migrating to using a
wixlib with a fragment generated by Heat. A lack of samples or useful
documentation had left me doing trial
] Merge Module Help
I can't really answer intelligently to question #1, as to question #2,
I'll
do my best.
Heat is really built for initial import functionality, not continual
maintenance. You do not want your GUIDs changing on your components with
each build, it will turn upgrades
exist somewhere?
-Jamey
-Original Message-
From: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of Christopher Karper
Sent: Friday, July 18, 2008 5:52 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module Help
I
updates, but it is very much not ideal. The biggest problem with this is
the lag in the Visual Studio IDE when dealing with a roughly 3 MB XML file
for the merge module.
Don't use VS to edit your XML. Something like Notepad2 or Vim or any
modern text editor should work great.
I'm surprised
I'm surprised that Heat doesn't have the functionality of leaving the
existing GUIDs in place. I just presumed I wasn't seeing how to do it.
There was (is?) a project called Paraffin (http://xrl.us/mnhwj) for
managing GUIDs. I've never used it so I can't vouch for it, but it may
be what
] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of Luke Bakken
Sent: Saturday, July 19, 2008 8:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module Help
I'm surprised that Heat doesn't have the functionality of leaving the
existing GUIDs
: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of Luke Bakken
Sent: Saturday, July 19, 2008 8:09 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module Help
I'm surprised that Heat doesn't have the functionality of leaving
, July 19, 2008 11:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module Help
This is a constant feature request (I'm surprised there isn't a feature
request already). Generating Component GUIDs that follow the Component
Rules is an *extremely
: Re: [WiX-users] Merge Module Help
James Minnis wrote:
Right now, I'm generating a merge module
Do you have a specific need for a merge module? (i.e., are you sharing
it with others so they can create installers?) If not, avoid merge
modules. They needlessly complicate things, as you're
Of James Minnis
Sent: Saturday, July 19, 2008 13:08
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Merge Module Help
I couldn't find a feature request for that with a couple of quick searches,
but it is possible that I missed it.
This is definitely not a trivial
: [EMAIL PROTECTED] [mailto:wix-users-
[EMAIL PROTECTED] On Behalf Of Rob Mensching
Sent: Saturday, July 19, 2008 1:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Merge Module Help
I think you've over-simplified the Component Rules. Once a Component
I'm working on a fairly large installer. It contains roughly 7000 files in
165 folders and a total of 670 MB of uncompressed data. Needless to say,
I'm generating the files, components, and directories using Heat.
Right now, I'm generating a merge module WXS file using Heat and then using
the
I can't really answer intelligently to question #1, as to question #2, I'll
do my best.
Heat is really built for initial import functionality, not continual
maintenance. You do not want your GUIDs changing on your components with
each build, it will turn upgrades into a nightmare, and will make
31 matches
Mail list logo
