windows installer - Calling a powershell script from InstallShield project -
i'm having weird problem.
i have installshield project (which creates setup.exe) contains custom action item - calling powershell script.
all script install 3 adobe reader updates (1 exe file , 2 msp files) on top of installed adobe reader 11.0.0.
when i'm calling script self - works fine.
however, after setup.exe finishes, seems 1 update (the exe file) installed (the adobe reader version after install 11.00.10 result of running exe file..).
all 3 adobe updates sit in same folder , powershell script first sets location folder. when running updates manually after installation - works fine , updates 10.00.22 (what should be).
any ideas why happening?
here's powershell script:
set-location "c:\myproject\adobeupdates" start-process .\adberdr11010_en_us.exe -argumentlist '/q /norestart /spb /rs /msi' -windowstyle hidden -wait ping 1.1.1.1 -n 1 -w 10000 # tried add delay wasn't helpful start-process -filepath “adberdrupd11021.msp” -argumentlist '/qn' -wait start-process -filepath “adberdrupd11022_incr.msp” -argumentlist '/qn' -wait
thank much
solved it, working script:
set-location "c:\myproject\adobeupdates" start-process .\adberdr11010_en_us.exe -argumentlist '/q /norestart /spb /rs /msi' -windowstyle hidden -wait ping 1.1.1.1 -n 1 -w 10000 start-process .\adberdrupd11021.msp -argumentlist '/qn' -wait start-process .\adberdrupd11022_incr.msp -argumentlist '/qn' -wait
i'm not sure different , love explain anyway works fine now.
Comments
Post a Comment