Page 1 of 1

Packaged VBScripts working directory

Posted: Wed Sep 23, 2015 8:18 am
by shocko
Hi guys. When I package a vbscript it defaults to a working directory of c:\temp\ rather than the working directory from the calling cmd.exe. If I run a vbscript from cmd.exe it defaults to the working directory of cmd.exe. This is causing me headaches with my hundreds of scripts I was planning on packaging. Why does it use c:\temp\ ? Does the .exe run natively or does it simply a zip file of the script and extracts its contents and runs?

Packaged VBScripts working directory

Posted: Wed Sep 23, 2015 8:18 am
by SAPIEN Support Forums
This is an automated post. A real person will respond soon.

Thank you for posting, shocko.

Did you remember to include the following?
  • 1. Product, version and build (e.g. Product: PrimalScript 2014, Version & Build: 7.0.46. Version and build information can be found in the product's About box accessed by clicking the blue icon with the 'i' in the upper right hand corner of the ribbon.)
    2. Specify if you are running a 32 or 64 bit version
    3. Specify your operating system and if it is 32 or 64 bit.
    4. Attach a screenshot if your issue can be seen on the screen
    5. Attach a zip file if you have multiple files (crash reports, log entries, etc.) related to your issue.
If not, please take a moment to edit your original post or reply to this one.

*** Make sure you do not post any licensing information ***

Re: Packaged VBScripts working directory

Posted: Wed Sep 23, 2015 11:31 am
by Alexander Riedel
What packager options are you using?
Specifically what engine type?

Re: Packaged VBScripts working directory

Posted: Tue Sep 29, 2015 12:34 am
by shocko
Apologies. I'm using PrimalScript 2012 and I haven't changed any packager options. I simply hit the 'Package' option on the Run tab

Re: Packaged VBScripts working directory

Posted: Tue Sep 29, 2015 6:28 am
by Alexander Riedel
That C:\Temp is a remnant from the old days where scripts had to be unpacked into temporary files. Try to add this code to the top of your script:
VBScript Code
Double-click the code block to select all.
Set oShell = CreateObject(”WScript.Shell”)
Set oFSO = CreateObject(”Scripting.FileSystemObject”)
oShell.CurrentDirectory = oFSO.GetParentFolderName(WScript.ScriptFullName)

Re: Packaged VBScripts working directory

Posted: Wed Sep 30, 2015 5:16 am
by shocko
Thanks I can try that ;). Can you tell me if this is fixed in the 2015 release of primal script/packager?