Re: [WiX-users] Burn using an old copy of an embedded msi

2011-07-13 Thread Bob Arnson
On 13-Jul-11 11:18, Roy Chastain wrote: > Currently I have the InstallCondition for the .MSI set to "1" to > always force it to run regardless of whether Burn thinks it is > installed or not. I guess another way to ask the question is, "what > would make Burn realize that a file, msi, exe etc -

Re: [WiX-users] Burn using an old copy of an embedded msi

2011-07-13 Thread Roy Chastain
> Hmm, sounds like Burn did not fully rollback the Bundle when your MSI > failed. In that case, you might want to uninstall the previous Bundle before > trying the new one. Also, the Burn log file should show you (during Detect) > whether a package was already cached or not. Yes, the log indicates

Re: [WiX-users] Burn using an old copy of an embedded msi

2011-07-12 Thread Rob Mensching
Hmm, sounds like Burn did not fully rollback the Bundle when your MSI failed. In that case, you might want to uninstall the previous Bundle before trying the new one. Also, the Burn log file should show you (during Detect) whether a package was already cached or not. The Package @Compress and @Cac

[WiX-users] Burn using an old copy of an embedded msi

2011-07-12 Thread Roy Chastain
I have a Burn package with a MSI that is marked as Compressed="yes". The Cache attribute was left off the MsiPackage element. I run that copy of Burn and my MSI failed to install (due to errors in the MSI). The bootstrapper application shows as installed. I rebuild the Burn package with a new MS