Actually I prefer the current approach, i.e. newer patch bundles should remove older patch bundles instead of just hiding them in the ARP. To me this approach seems more intuitive as I was quite surprised that an older .msp becomes visible again after I removed a .msp that superseded it.
While testing this it didn't work for me because I had used the wrong UpgradeCode and therefore ended up with multiple patch bundle entries in the ARP instead of entries that replace each other. This was purely a fault from my side, the behavior of Burn is correct and I did not find a bug there regarding this issue. Therefore I scratch #3 off this list. Regarding #1: The tricky part is really the elevation required to write the per machine keys. So far I haven't figured out an alternative. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-patch-bundle-limitations-tp7585779p7585820.html Sent from the wix-devs mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
