About srivvt

srivvt · ‎Feb 21, 2021

Hello everyone When I was looking at DemoShield launch actions and found that one way to launch .exe is by selecting Launch Application type instead of Launch Application. But I was able to launch new InstallShield application only 2 out of 3 times successfully that too it was very slow to launch. Please note that as mentioned in my previous post, double clicking setup.exe is loading the application fine. Does anybody know why this behavior with DemoShield or InstallShield 2020? Migrating DemoShield project to InstallShield looks like a costly effort which I am not willing to do now. Any comments or inputs please provide.. Thanks.

srivvt · ‎Feb 18, 2021

Hello rguggisberg, thanks for the suggestion. You think the issue is with the DemoShield rather than newly generated setup.exe?

srivvt · ‎Feb 17, 2021

Hello everyone, I have an basic MSI file which was a InstallShield 2010 file. I migrated that to InstallShield 2020. Installer (setup.exe) is generating fine but when its launched as an Launch Application action via DemoShield (v8), setup.exe just exits by creating a alpha numeric folder in AppData/Temp/ with only '_ISMSIDEL.ini'. Double clicking the new setup.exe seems to install/upgrade but the AppData/Temp/ contents are not the same as the old setup.exe which was generated with InstallShield 2010. But I doubt if any other files were missing from the new setup.exe! Can anyone help me try to figure out how to resolve this issue? Thanks, Sriv

Online Status	Offline
Date Last Visited	‎Mar 02, 2021 03:05 AM

Re: Configuring 'Setup.ini' and '0x0409.ini' files in InstallShield 2020

Re: Configuring 'Setup.ini' and '0x0409.ini' files in InstallShield 2020

Configuring 'Setup.ini' and '0x0409.ini' files in InstallShield 2020

Re: Configuring 'Setup.ini' and '0x0409.ini' files in InstallShield 2020

Re: Configuring 'Setup.ini' and '0x0409.ini' files in InstallShield 2020

Configuring 'Setup.ini' and '0x0409.ini' files in InstallShield 2020