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: Problem with SOURCEDIR when Upgrading Installshield project to IS 2008.
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
‎May 22, 2008
12:07 PM
Problem with SOURCEDIR when Upgrading Installshield project to IS 2008.
Hello Everyone!
I have tried to upgrade an InstallShield project created on IS 11.5 to install Shield 2008. I have some install shield custom actions.
When i run this part of script on the first custom action i get the real values
SprintfBox (INFORMATION, "New Source Folder","New Source:%s",SRCDIR);
SprintfBox (INFORMATION, "New Source Folder","New Source:%s",SUPPORTDIR);
SprintfBox (INFORMATION, "New Source Folder","New Source:%s",SETUPEXEDIR);
SprintfBox (INFORMATION, "New Source Folder","New Source:%s",SUPPORTDIR);
But when i run the above script on another custom action the value is blank.
I need to have the path of the source.
Tau
I have tried to upgrade an InstallShield project created on IS 11.5 to install Shield 2008. I have some install shield custom actions.
When i run this part of script on the first custom action i get the real values
SprintfBox (INFORMATION, "New Source Folder","New Source:%s",SRCDIR);
SprintfBox (INFORMATION, "New Source Folder","New Source:%s",SUPPORTDIR);
SprintfBox (INFORMATION, "New Source Folder","New Source:%s",SETUPEXEDIR);
SprintfBox (INFORMATION, "New Source Folder","New Source:%s",SUPPORTDIR);
But when i run the above script on another custom action the value is blank.
I need to have the path of the source.
Tau
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
05:53 PM
Perhaps try calling MsiGetProperty to get the value of, say, SETUPEXEDIR?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2008
06:25 PM
The script i use to get the path is:
MsiGetProperty(ISMSI_HANDLE, "SourceDir", szSourceDir, nvBufferSize);
MessageBox ("SourceDir is:=" + SourceDir, INFORMATION);
MsiGetProperty(ISMSI_HANDLE, "SETUPEXEDIR", szSETUPEXEDIR, nvBufferSize);
MessageBox ("SETUPEXEDIR is:=" + szSETUPEXEDIR, INFORMATION);
The output is the same.
If I use this script on the first custom action I get the right path. Otherwise the values of szSourceDir and szSETUPEXEDIR are blank.
Tau
MsiGetProperty(ISMSI_HANDLE, "SourceDir", szSourceDir, nvBufferSize);
MessageBox ("SourceDir is:=" + SourceDir, INFORMATION);
MsiGetProperty(ISMSI_HANDLE, "SETUPEXEDIR", szSETUPEXEDIR, nvBufferSize);
MessageBox ("SETUPEXEDIR is:=" + szSETUPEXEDIR, INFORMATION);
The output is the same.
If I use this script on the first custom action I get the right path. Otherwise the values of szSourceDir and szSETUPEXEDIR are blank.
Tau
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 23, 2008
09:06 AM
When/where in the sequences are you calling this code? As a sanity check, are you setting nvBufferSize to a large value before each call to MsiGetProperty?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 23, 2008
10:07 AM
Everything work fine on IS 11.5. But after the upgrade to IS 2008 those part of code do not work same as IS 11.5.
I think is part of the way how IS 2008 works with global variables, and how IS 2008 works with many custom action.
Tau
I think is part of the way how IS 2008 works with global variables, and how IS 2008 works with many custom action.
Tau
RobertDickau wrote:
When/where in the sequences are you calling this code? As a sanity check, are you setting nvBufferSize to a large value before each call to MsiGetProperty?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 23, 2008
10:20 AM
Correct, the InstallScript-in-MSI architecture changed in InstallShield 12; please see the sticky posts at the top of this forum for links to further details.
![](/skins/images/3B39CE851FDD5528C393F146EB70A2D0/responsive_peak/images/icon_anonymous_message.png)