windows - InstallShield Custom Action failing because user installing in 64-bit Program Files directory? -


i have 32-bit legacy application allows users specify install path part of setup (pretty normal stuff...). have custom action defined runs silent background install of required bit of software after initial installation complete.

all when users install 32-bit program files (x86) directory.

where running problems when users specify 64-bit installation directory, windows automagically changes install path in background use (x86) program files folder, fine, except custom actions use same installdir property after initial install finished still think should 64-bit "program files" path - install fails when custom action can't find exe file it's looking for.

my program same 1 described here developer never resolved in forum: http://community.flexerasoftware.com/archive/index.php?t-216268.html

does have clue valid workaround is? seems pretty basic installer should not fail because users think should install "c:\program files\appname" instead of "c:\program files (x86)\appname".

i did peruse similar questions on here don't see else issue using custom actions.

in experience need change 64 bit template install program files. general information in tree > template summary > change x64;1033. @ least 1 file needs marked 64 bit in each directory. check box on component property. sure check custom actions still obey run conditions on major upgrades. having issues currently. major upgrades on mine set remove , runs custom actions no matter conditions on removal portion of script.


Comments

Popular posts from this blog

python - TypeError: start must be a integer -

c# - DevExpress RepositoryItemComboBox BackColor property ignored -

django - Creating multiple model instances in DRF3 -