Condition Level="0" is tricky. There's a warning about this buried in the MSDN documentation for the Condition Table <http://msdn.microsoft.com/library/aa368014.aspx> : "Conditions should be carefully chosen so that a feature is not enabled on install and then disabled on uninstall. This will orphan the feature and the product will not be able to be uninstalled."
I.e., you need the condition for Level 0 to be NOT "condition for enabling the feature" AND NOT "feature is already installed". I usually deal with this by adding a registry value to the feature (HKLM/HKCR/HKMU as appropriate), reading it to a property via RegistrySearch, and adding the property to the Level 0 Condition: As for the cleanup, unfortunately there's not much you can do about a version that's already shipped. But this should at least make an improvement for your next release. Hope this helps, Mike -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-Condition-Level-0-results-in-files-being-left-behind-after-upgrade-then-uninstall-tp7583950p7584017.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
