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
- :
- Thanks
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
‎Jun 28, 2010
07:00 AM
Unable to execute support files
Hi!
I've upgraded InstallShield X project (Basic MSI) to InstallShield 2010 using IsCmdBld.exe with key -u. But the problem of executing support files occurred. In InstallShield X projects InstallScript system variable SUPPORTDIR initialized correctly and I used it in my several custom actions. After upgrading I discovered that my custom actions did not do its jobs, I found out that the SUPPORTDIR was mapped to %TEMP%\, but this directory contains only some InstallShield files missing my Support files.
It should be noticed that upgrade tool transferred ISSetupFilesExtract and ISSetupFilesCleanup custom actions correctly, nothing changed!
So where are those Support files copied, and how can I access them?
Regards, Ruslan.
I've upgraded InstallShield X project (Basic MSI) to InstallShield 2010 using IsCmdBld.exe with key -u. But the problem of executing support files occurred. In InstallShield X projects InstallScript system variable SUPPORTDIR initialized correctly and I used it in my several custom actions. After upgrading I discovered that my custom actions did not do its jobs, I found out that the SUPPORTDIR was mapped to %TEMP%\
It should be noticed that upgrade tool transferred ISSetupFilesExtract and ISSetupFilesCleanup custom actions correctly, nothing changed!
So where are those Support files copied, and how can I access them?
Regards, Ruslan.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 28, 2010
08:27 AM
This may be a side effect of some improvements and InstallScript engine architecture changes that were made in InstallShield 12. The following help topic explains some changes that you may need to need to your project:
Upgrading InstallShield 11.5 or Earlier Basic MSI Projects that Have InstallScript Custom Actions
I hope that helps.
Upgrading InstallShield 11.5 or Earlier Basic MSI Projects that Have InstallScript Custom Actions
I hope that helps.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 29, 2010
03:33 AM
This info was very helpful. I had added "Set property" custom action to initialize property which contains the path to support files and used this property to execute them.