[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
Re: [WiX-users] heat question
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
Re: [WiX-users] heat question
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.comwrote: 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
[WiX-users] Heat question
Hi, I would like to add the following within the Product tag of the .wxs file. Property Id=WIXUI_INSTALLDIR Value=TARGETDIR / UIRef Id=WixUI_InstallDir / How can this be done automatically using heat. Thanks Satyaprakash J -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat question
On 10-08-30 2:54 AM, Satyaprakash J wrote: Hi, I would like to add the following within theProduct tag of the .wxs file. Property Id=WIXUI_INSTALLDIR Value=TARGETDIR / UIRef Id=WixUI_InstallDir / How can this be done automatically using heat. Generally, it is recommended to use the heat output as a starting point but you can use a scripting language for this too. -- Sohail Somani -- iBlog : http://uint32t.blogspot.com iTweet: http://twitter.com/somanisoftware iCode : http://bitbucket.org/cheez -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Heat question
Eva, Mark E (ESL Lab-Boise) wrote: I am a new user of Heat.exe. I would like to exclude a directory or files with specific extensions from Heat. An example would be, exclude directory .svn from Heat selection. An example of a file extension .log. Is it possible to do this from the commandline or is this being considered as a future enhancement. It isn't currently supported but there are feature requests open for it. Nobody is currently contributing to Heat, so if you're interested, it'll get done faster if people contribute fixes and features. -- sig://boB http://joyofsetup.com/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Heat question
I am a new user of Heat.exe. I would like to exclude a directory or files with specific extensions from Heat. An example would be, exclude directory .svn from Heat selection. An example of a file extension .log. Is it possible to do this from the commandline or is this being considered as a future enhancement. Mark E. Eva - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
