I wrote a small program to walk a directory hierarchy and generate the XML
for a fragment that defines a ComponentGroup for the root folder that you
specify. It's an easy program to write and the output can be customized to
the way I like it, i.e. a lot cleaner than the output from the WiX tool,
Matthew Janulewicz wrote:
> I don't think there is an elegant way to do this, as the Wix
> tools (or any other tools for that matter) can't predict what
> ComponentRef's you want under which features.
Everything under a certain directory put in one feature seems
to be a fairly good first approxi
Yeah, looks like the way to go. For the curious, I made an XSL template to
do it (mostly as an excuse to learn XSL). I don't really know what I'm
doing, but here's my partial solution anyway: (it generates just the raw
text of the inside of the block, rather than actually modifying
the original .w
In the past I've used a perl script to "twaddle" the tallow output into a form
that can be used in a feature... These days I've
been breaking up my source files and using to collect the
components in each file.
--
Eric Fesh
Customer Support Engineer/Software Test Engineer
Verari Systems Softw
ComonentRef tags.
-Matt
_
From: Steve Bennett [mailto:[EMAIL PROTECTED]
Sent: Monday, December 18, 2006 3:18 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creating features with lots of components
Hi all,
Is there a good way to generate the code for a f
Hi all,
Is there a good way to generate the code for a feature with lots of
components? Generating the code for the components is ok with tallow/mallow.
But is there a slightly elegant way to generate all the tags?
Short of awk or similar?
Surprisingly WiXEdit doesn't seem to do this.
S
6 matches
Mail list logo
