Start here: http://robmensching.com/blog/posts/2010/4/28/Change-of-plans-for-WiX-v3.5
<http://robmensching.com/blog/posts/2010/4/28/Change-of-plans-for-WiX-v3.5>Then here: http://robmensching.com/blog/posts/2009/7/14/Lets-talk-about-Burn and http://robmensching.com/blog/posts/2009/7/22/Burn-packages-payloads-and-containers On Sat, Jun 12, 2010 at 4:27 PM, <gree...@cox.net> wrote: > I should have had this in my previous message. Where is the Burn > documentation? It is not in the Wix 3.5 package, at least I can't find it > after doing an Administrative install if Wix3.5.msi (DON"T FORGET TO SET > TARGETDIR HERE). > > Is Burn ready for primetime? My client is currently on the stable 3.0 > release. Can Burn be obtained and used alongside Wix 3.0? Also, we need to > bundle the .MSI, MST, and cabinet into a single EXE self extractor. We want > to be able to download and install these as single files. Can burn package > files into a self-extracting exe? > > Maybe this is not doable. Some of the .MSI's are large and I would had to > have to extract to a temp or program data folder and leave the big package > lying around for the slim change the user might goof up their installation > and trigger a "detect and repair". > > ---- gree...@cox.net wrote: > > Thanks, I will need to learn about Burn, I see the name of of the utility > alot. I now need to learn what it actuall dows. I am however using Wix 3.0 > and will need to see if Burn is a 3.5 utility. > > > > Regards, > > Aris > > > > ---- Rob Mensching <r...@robmensching.com> wrote: > > > Yeah, don't do that. In Burn we do a lot of work to make sure the MSI > is > > > cached in a consistent location so that repair, patching, etc. all work > > > correctly. > > > > > > On Sat, Jun 12, 2010 at 8:48 AM, <gree...@cox.net> wrote: > > > > > > > I created an MSI package, MST (transfor), and .cab file using WIX > 3.0. I > > > > bundle all three up in a NullSoft self extracting exe that when > called by a > > > > bootstrapper, extracts the files to a directory on disk and calls the > msi > > > > using msiexec and setting the TRANSFORMS property to the .MST file. > > > > > > > > Question is, after the product is installed, what will happing during > a > > > > normal "Detect and Repair" if the user deletes a key file and then > launches > > > > the app using the application short cut? The ResourceSource action, > I know, > > > > will look for the SourceDir value containing the original MSI. These > files > > > > are gone after the NullSoft executable runs the install and cleans > up. > > > > > > > > I understand InstallShield using the SETUPEXEDIR property for dealing > with > > > > this, but you do other vendors that wrap their MSI's in a setup.exe > type > > > > file. Also, my NullSoft exe is not named "setup.exe", its is the MSI > file > > > > name replaced with an EXE extention. > > > > > > > > Any help would be greatly appreciated. > ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
