More simply: it's just a .wxs file. You compile and link the .wxs file like you do any other .wxs files. The burn.exe is in a "strange" place because it's just an implementation detail. Building your Bundle is just like building your MSI or your MSP or your MSM...
On Thu, May 30, 2013 at 4:00 PM, Hoover, Jacob <jacob.hoo...@greenheck.com>wrote: > You use candle and light to compile the burn bundle as well. > > Sent from my iPhone > > On May 30, 2013, at 5:26 PM, "Alain Forget" <afor...@cmu.edu> wrote: > > > Unfortunately, I'm not using Visual Studio, so I don't think that's an > option. > > > > So what I'm currently trying to do is use candle/light to make > MyMSIProductPackage.msi (which works great on its own), and then use > burn.exe to package it up with the Java Runtime Environment 7 exe > installer, to make sure Java is on the target machine before > MyMSIProductPackage.msi is unloaded. > > > > Am I doing things incorrectly? > > > > Alain > > > > -----Original Message----- > > From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com] > > Sent: May 30, 2013 18:21 > > To: afor...@cmu.edu; General discussion for Windows Installer XML > toolset. > > Subject: RE: [WiX-users] How to use Burn > > > > If you have Visual Studio, the Votive/integration that Wix provides > hides most of this for you and it just works. You don't use burn to build > the bundle, use candle/light to build it. > > > > From a rough point of view, the burn exe is the starting point for your > bundle and some "magic" happens to cab up your BA and any embedded payloads > and then it's stuck into the exe at the end of the file. The exe knows to > read this extra info, extract it, and execute the BA. > > > > -----Original Message----- > > From: Alain Forget [mailto:afor...@cmu.edu] > > Sent: Thursday, May 30, 2013 5:10 PM > > To: wix-users@lists.sourceforge.net > > Subject: [WiX-users] How to use Burn > > > > It's time for me to step on the Burn noob school bus. :-) > > > > So I have the following file named MyBundle.wxs: > > > > <?xml version='1.0' encoding='windows-1252'?> <Wix xmlns=' > http://schemas.microsoft.com/wix/2006/wi' xmlns:util=" > http://schemas.microsoft.com/wix/UtilExtension";> > > > > <Bundle UpgradeCode="MY-GUID" Version="1.0.0"> > > <BootstrapperApplicationRef > Id="WixStandardBootstrapperApplication.RtfLicense" /> > > <WixVariable Id="WixStdbaLicenseRtf" Value="License.rtf" /> > > <Chain> > > <PackageGroupRef Id="pkgJRE7"> > > <MsiPackage > > Id="pkgMyMSI" > > DisplayName="My MSI" > > Cache="no" > > Compressed="yes" > > Permanent="yes" > > SourceFile="MyMSIProductPackage.msi" > > Visible="yes" > > Vital="yes" > > ></MsiPackage> > > </Chain> > > </Bundle> > > </Wix> > > > > The file containing the Package "pkgJRE7" and MyMSIProductPackage.msi > are in the same folder as MyBundle.wxs. When I run "burn.exe MyBundle.wxs", > nothing happens. No error, no new files, nothing. I followed the examples > here (http://wix.sourceforge.net/manual-wix3/authoring_bundle_intro.htm) > as closely as I could, but clearly I'm doin' it wrong. > > > > For example, how does burn know where to find pkgJRE7? The second > example here ( > http://wix.sourceforge.net/manual-wix3/bundle_author_chain.htm) doesn't > have a reference to a file where MyPackage is located, so...I'm guessing it > somehow magically finds it? > > > > > > > > Another thing I find confusing is the burn.exe is located in a separate > (sub)folder "x86" from all the other WiX tools. I'm not sure if that's > normal or not (i.e. it makes me wonder if it's the right program), but it > seems strange to me. > > > > Anyway, any help at all would be appreciated, and thanks to everyone who > provided advice to get this far. > > > > Alain > > > > *************************************** > > Alain Forget, Ph.D. > > Postdoctoral Researcher > > CyLab, Carnegie Mellon University > > afor...@cmu.edu > > http://cups.cs.cmu.edu/~aforget/ > > *************************************** > > > > > > > > > > > ------------------------------------------------------------------------------ > > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET > Get 100% visibility into your production application - at no cost. > > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > > http://p.sf.net/sfu/appdyn_d2d_ap1 > > _______________________________________________ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > ------------------------------------------------------------------------------ > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET > Get 100% visibility into your production application - at no cost. > Code-level diagnostics for performance bottlenecks with <2% overhead > Download for free and get started troubleshooting in minutes. > http://p.sf.net/sfu/appdyn_d2d_ap1 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
