Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

So just to make sure, the current behavior is kind of by design and currently there is no way how to not get ARP entry if .NET prereqba succeeds? It needs to be implemented as a new feature to Burn? -- View this message in context:

Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

I believe that there 'may' be a bug in the existing implementation along the lines that Colin described or and related to the comment Burn should keep registration in ARP when the first non-permanent package is installed (aka: there is something Burn would do).. In the scenarios where I had

Re: [WiX-users] .NET Prerequisite, Burn, and the ARP

Yes. There are very good reasons why Burn behaves the way it does today and handling this case requires additional (non-trivial) code (not fixing existing code). ___ FireGiant | Dedicated support for the WiX toolset |

[WiX-users] Why Does Bundle Prompt For Source During Uninstall?

I have a bundle that I have successfully installed. When I try to uninstall I get the following: [0E54:03D0][2015-07-13T15:34:03]i300: Apply begin [07F0:0814][2015-07-13T15:34:03]i360: Creating a system restore point. [07F0:0814][2015-07-13T15:34:10]i361: Created a system restore point.

Re: [WiX-users] Why Does Bundle Prompt For Source During Uninstall?

The attached container is stripped (to save [often signification] disk space). Look higher in the log to see what package is requesting to be cached during uninstall. Probably an ExePackage. ___ FireGiant | Dedicated support for the