I've got an issue with an old install on a system that we are upgrading. The issue is that one of the custom actions is depending on a property that is only available during a UI install and when an upgrade is performed the previous install is removed silently and the custom action fails because this value is not set.
It looks like the previous install should have had this custom action conditioned to not run during an uninstall or we should have made the property available. Should we write a custom action to find the cached msi in the %WINDIR%\installer folder and use some MSI methods to "Fix" the issue in the old install? Any ideas? Thanks, Dan ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
