Blair,
Thanks for the information. The ComponentGroup element was the key piece of information I needed to coax Google into presenting some excellent commentary on the pros and cons of the different approaches.
----- Original Message -----
From: "Blair" <
[hidden email]>
To: "General discussion for Windows Installer XML toolset." <
[hidden email]>
Sent: Wednesday, October 28, 2009 10:53:50 AM GMT -07:00 US/Canada Mountain
Subject: Re: [WiX-users] How should I approach modularization?
Two other options.
1. in your wxs files with your component declarations, put your components
in <DirectoryRef> tags. Those tags will reference the Directory elements in
your hierarchy. You will need to reference something in your fragments from
the product so that they get included, however.
2. in your WiX v3 wxs files with your component declarations, add Directory
attributes to your components. Those attributes will reference the Directory
elements in your hierarchy. You will need to reference something in your
fragments from the product so that they get included, however.
The easiest way to reference your fragments is to include and populate one
or more <ComponentGroup> elements in your wxs files containing your
component declarations, and add <ComponentGroupRef> elements inside either
your <Product> element or one of your <Feature> elements.
-----Original Message-----
From: JK E-Lists [mailto:
[hidden email]]
Sent: Wednesday, October 28, 2009 6:28 AM
To:
[hidden email]
Subject: [WiX-users] How should I approach modularization?
I'm a total WiX noob, so please bear with me here. :)
I have a very large project that I'm writing an installer for. It has 2-3
scores of assemblies. The component list for the project is massive and
unwieldy. I want to break this up and group the component declarations
according to functionality.
How does one typically approach this? I can't see how to create fragments
with the component declarations because they apparently have to be in the
<Directory> hierarchy. The only thing I can figure out is to use include
files, such as
<Directory ...
<Directory ...
<?include "foo.wxi">
...
Is this an appropriate way to manage the components, or is there something
I'm not grokking?
Thanks a lot,
jk
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
