This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: WINSYSDIR & LaunchAppAndWait Calls NOT Working upon Migration from InstallShield 10.5
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 13, 2008
04:47 AM
WINSYSDIR & LaunchAppAndWait Calls NOT Working upon Migration from InstallShield 10.5
Hi,
We are currently using InstallShield 10.5 for our Packages. Our Project Type is Basic MSI.
We Migrated Our Projects as per the Guidelines.
But, Basic InstallShield APIs like LaunchAppAndWait is NOT Working with the migrated project. Also, WINSYSDIR Property is displaying NULL Value.
I built a New Package in InstallShield 2008 and this package is executing both LaunchAppAndWait and WINSYSDIR Perfectly Well.
Can you suggest what can be done to resolve this issue?
Thanks,
Shivashankar
We are currently using InstallShield 10.5 for our Packages. Our Project Type is Basic MSI.
We Migrated Our Projects as per the Guidelines.
But, Basic InstallShield APIs like LaunchAppAndWait is NOT Working with the migrated project. Also, WINSYSDIR Property is displaying NULL Value.
I built a New Package in InstallShield 2008 and this package is executing both LaunchAppAndWait and WINSYSDIR Perfectly Well.
Can you suggest what can be done to resolve this issue?
Thanks,
Shivashankar
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 13, 2008
10:52 AM
I think you're getting this behavior due to the changes in the engine for between IS11.5 and IS12 related to deferred custom actions - in particular variables like WINSYSDIR are no longer safe to use in deferred custom actions. You might be able to confirm this by adding a message box to show the path you are about to launch. This would have worked in a sample if you put the code in an event or in a non-deferred custom action instead. Please see the migration articles referenced in the sticky notes in this and the IS12 community.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)