The approach in that blog post is essentially the same as what I tried with the REMOVE condition. I'm disabling the feature and using "AND NOT REMOVE" in the condition, whereas the blog post talks about enabling the feature with "OR REMOVE" in the condition. I tried the latter approach, but it still only works if there's no UI (e.g. uninstall via ARP). If I re-run the installer in maintenance mode and choose the 'Remove' option, then the files get left behind.
I might try setting the property REMOVE to ALL on that last dialog and seeing if it has any affect on costing in the install execute sequence. Rob Bob Arnson wrote: > Rob Hamflett wrote: >> <Condition Level="0"><![CDATA[FOUND_VC80DIR = "UNKNOWN"]]></Condition> >> >> I'm trying to work out how to get my product to uninstall after the user has >> removed Visual Studio. >> > > http://www.joyofsetup.com/2008/05/16/make-sure-features-are-always-enabled-so-they-can-be-removed/ > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
