RE: [WiX-users] Beginner's quesetions about simple.wxs

[Erv W. <Er...@ep...>]

Note, the tallow output is not quite "ready to use".  It doesn't put
GUIDs on the components, and the component names are unpredictable (vs.
being a something related to the contents).  I used tallow to generate
an initial file, but we now maintain that .wxs file by hand when we add
or remove files. =20

And yes, I bet that the MS Office team *does* maintain their list of
files by hand.

Hand maintenance is pretty much required if you want to follow the
component rules:

http://blogs.msdn.com/robmen/archive/2003/10/18/56497.aspx

http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/msi/se=
t
up/organizing_applications_into_components.asp

http://msdn.microsoft.com/library/default.asp?url=3D/library/en-us/msi/se=
t
up/changing_the_component_code.asp


-----Original Message-----
From: Bob Arnson [mailto:sf...@bo...]=20
Sent: Wednesday, October 13, 2004 12:56 PM
To: 'T.J. Yang'; sf...@bo...; Erv Walter;
wix...@li...
Subject: RE: [WiX-users] Beginner's quesetions about simple.wxs

[cut]

> Since tallow source code is avaiable, we may add a fiew switches so
> it can generate a wxi to list out all the files in a subdirectory.
> then .wxs can just include "srcdir.wxi" and
> "tallow -d c:\emacs -i -o srcdir.wxi"  run before candle.

It currently generates a fragment, which comes in handy because it
generates
the directories and components needed to handle subdirectories. But a
.wxi
could be handy, too.