Hmm, I don't recall having to do anything special in the custom bootstrapper to handle what gets displayed in Add/Remove Programs. I mean, you have to implement handlers for the Detec, Plan, Apply events...but if you're successfully installing and uninstalling you must be doing that. I think the problem must lie somewhere in the XML markup. Can you send the snippet of the bootstrapper's log where it detects the previous install and sets it up for removal?
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Bootstrapper-is-not-removing-older-version-from-Control-Panel-Uninstall-Program-tp7593116p7593190.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
