After some thought, I think the other way (i.e. make each patch bundle visible) is the way forward...
Not sure why ACKH (http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-patch-bundle-limitations-td7585779.html) think's that there isn't a problem. >From my testing, neither scenario works as expected. Have you managed to fix the original bug? (i.e. in the code as opposed to removing the patch supersedence)? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/fixing-a-bug-superseded-patches-are-not-removed-by-bundle-tp7586911p7587472.html Sent from the wix-devs mailing list archive at Nabble.com. ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ WiX-devs mailing list WiX-devs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-devs
