On 09-Aug-12 09:02, Henning Krause wrote: > I have investigated the issue further and come to the conclusion that it > happens during an upgrade of an existing installation. It tries to do > something to the existing pacakage and looks up the package in the current > bundle using its id. When it does not find it, it fails with the access > violation. Upgrading was the key. This is now fixed for the next build. For posterity, here's the comment I added when I resolved the bug:
At the end of an upgrade, the new bundle tells the old bundle to go away, like a post-InstallFinalize major upgrade. That's the GUID package id. The new bundle doesn't have a record of the old bundle id, so it blows up when it's not found. -- sig://boB http://joyofsetup.com/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
