I was testing a bootstrapper package this afternoon and when I happened to look at the Add/Remove programs, I found about 8 copies of the bootstrapper installed. What was more surprising was that I could run uninstall on each one.
This seems like very strange behavior. This implies that the bootstrapper is creating its own MSI with a unique product code and upgrade code each time it is built. Is that the case? Is that changeable? In each case my actual MSI failed to install and the prerequisites did not install because they were not needed, so Burn should have been a giant no-op. I also noticed that something keeps track of the prerequisites downloaded files. They were only asked about the first time. Once I removed all copies of the installed bootstrapper, it again asked about the downloads of the prerequisites. Given that the prerequisites are required and cannot be uninstalled, I have marked them as vital="yes" and permanent="yes". I put them and the MSI in the same chain and marked it as DisableRollback="yes". Is there some way that I can author this package so that, if my MSI fails, the bootstrapper application itself would not be "installed". I am trying to understand the big picture with Burn, but I am struggling. ---------------------------------------------------------------------- Roy Chastain ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
