There is no such thing as a 'Burn custom action' (and it would be overkill if it existed). I suggest that you try the built-in functionality of util:RegistrySearch and using the variable in the Install condition.
If it does not work for you, then post the relevant sections of code and a verbose log, so that others volunteers can advise you on how to get it to work. The pattern of doing a registry search and using the variable in an InstallCondition is very common and used by many, including the wix source. So figure out why it is not working for you. You can configure in the registry, verbose logging for MSIs, which also enables verbose logging for Burn. Then look in your temp folder for the log. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bundle-EXE-setting-property-tp7595178p7596201.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
