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
- :
- TEMP env variable wrong in IS2011
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
‎Feb 01, 2011
02:06 PM
TEMP env variable wrong in IS2011
I recently converted a project from IS2010 to IS2011 and notice that the administrator's TEMP environment variable changes once in Deferred Execution. In Immediate Execution, it is located in C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1, where I expect it to be. However, once in Deferred Execution, it changes to C:\Windows\Temp.
Any idea why it changes?
I opened up the IS2010 version of the project and confirmed that it remains pointed to C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1 throughout the install. The custom action VBScript code is contained in an external file, so I am using the same CA code in both versions of the install.
I'd rather not have to begin to account for this switch in all my projects that I intend to upgrade to IS2011, so some information about this would be much appreciated.
Any idea why it changes?
I opened up the IS2010 version of the project and confirmed that it remains pointed to C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1 throughout the install. The custom action VBScript code is contained in an external file, so I am using the same CA code in both versions of the install.
I'd rather not have to begin to account for this switch in all my projects that I intend to upgrade to IS2011, so some information about this would be much appreciated.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 02, 2011
09:32 AM
Start using the "TempFolder" property like I told you yesterday. Jeez.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 02, 2011
05:50 PM
Are you using the InstallShield built-in SQL scripts support in your installation? If so, apply the hotfix posted in this thread, and see if it fixes your issue.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 10, 2011
11:57 AM
I'm seeing the same behavior with IS 2011, that TempFolder ends with \2 in immediate execution, and without the \2 in deferred execution.
David
David
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)