You might try organizing your builds into .wixlibs. A .wixlib can integrate at more touch points than a Merge Module can.
On Wed, Feb 15, 2012 at 12:21 PM, Christopher Painter <chr...@iswix.com>wrote: > A merge module is reusable and doesn't know about INSTALLDIR or TARGETDIR. > It know's about ModuleRetargetableDir. When you consume the merge module > in an installer you will use a Merge, MergeRef and Directory element > combination to associate the ModuleRetar.. to INSTALLDIR or INSTALLLOCATION > or TARGETDIR or whatever else that installer calls it. > > > You should checkout iswix.codeplex.com as it's a tool you might find so > useful that you don't care to use Heat anymore. Also even if you don't use > the tool look at the source code to it to see how merge modules and product > installers come together as ISWIX uses ISWIX and WIX itself to author it's > various merge modules and product installer. > > ---------------------------------------- > > From: "Joel Budreau" <jbudr...@vmware.com> > > Sent: Wednesday, February 15, 2012 1:47 PM > > To: "WiX Users" <wix-users@lists.sourceforge.net> > > Subject: [WiX-users] heat question > > > Hi, > > > I'm using WiX 3.0 and utilizing heat.exe to harvest a directory in my build > tree. My goal is to generate a MSM using the resulting .wxs file. I have a > couple of MSIs that will use this MSM, and each MSI will want to install > the MSM files into a separate directory. Here's my problem: > > > - Build tree to harvest is located at ...\build\output\<files>... > > - I point heat.exe to ...\build\output > > - My MSM now has "output" as the root directory of all the files, do not > want :( What I want is to have INSTALLDIR set as the root path > (INSTALLDIR\<files>...) > > > I've also tried passing ...\build\output\. to heat to see if it would > recognize "." as the root directory instead of "output", but it had the > same result. > > > Thanks, > > Joel > > > > ---------------------------------------------------------------------------- > -- > > Virtualization & Cloud Management Using Capacity Planning > > Cloud computing makes use of virtualization - but cloud computing > > also focuses on allowing computing to be delivered as a service. > > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > > _______________________________________________ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > -- virtually, Rob Mensching - http://RobMensching.com LLC ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
