SAPIEN Technologies

The best way to do this is to tell the packager not to use the temp folder.
That way you can be sure your script runs in the same fodler as the exe.

Moving topic to the appropriate forum.

Please also do not post PrimalScript questions in the Free Tools section.
Use the proper technical support forum.

It really depends what packaging options you use, but
WScript.Path
should work like in any other VBScript.
Or am I missing something?

Alex

Yeah, it seems the Powershell engine chokes on unfinished strings and it depends on their length if it reports an error or blows up.

What type of script are you packaging?

PrimalScript has never participated in the Microsoft Just-In-Time debugging scheme, since it breaks far too easily.
Just load your VBScript into PrimalScript and choose "Debug" -> "Go" or press F5.

It's odd it would crash in that dll. I was able to replicate the issue with PowerShell V2. The crash occurs when PowerShell is asked to syntax check any block of script. As PowerShell V2 is not released, or even officially in beta, we cannot really support this. In the next service build we will mak...

Yes, please send the key. I'll try to find out what caused this.
Alex

The location of the files depends on your OS and your configuration. We needed to move the folder to conform with Vista and Windows 7 requirements. You can always determine (or change) the actual location by going toTools - Options - Environment - Directories and look where the "Snippets folder...