Trouble "building" EXE from PowerShell Script

[Tzadok85]

Product, version and build: PrimalScript 2016 // 7.2.92.0
32 or 64 bit version of product: x64
Operating system: Windows 10 Enterprise
32 or 64 bit OS: x64

Hello - I've written a script that runs perfectly on it's own - I'm attempting to use the "Build" feature within PrimalScript to convert it to an EXE.
This feature/app works just fine on other scripts I've written on this same system.

When building, I get 0 warnings & 0 errors - it produces the EXE just fine.

When I build using the "SAPIEN PowerShell V5 Host (Windows) x64" Engine, it results in a number of "odd popups" & errors that continue until I "End Task" on the EXE... (see screenshots)

04.png (2.98 KiB) Viewed 4482 times

05.png (2.96 KiB) Viewed 4482 times

06.png (2.59 KiB) Viewed 4482 times

Additionally, if I building using another engine type (e.g. a the "Command Line" variant of the same V5 engine), it can result in a powershell window that shows some variant of the following text:

./3506EFD6.PS1 : The term './3506EFD6.PS1' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1


Hopefully this is enough info to provide some insight...
Thanks much!

[DevinL]

Would you mind uploading the script that you attempted to package into an executable?

If you don't wish for it to be public you can upload it to https://sapien.com/support/upload and we can take a look at the cause of this.

[Alexander Riedel]

Looks like the powershell engine cannot understand the encoding of your script file.
Check in PrimalScript what the encoding of your file is. You can see that at the status bar.
Powershell cannot comprehend a few common encoding types even if a BOM (Byte Order Mark) is present.

[Tzadok85]

Thanks! Sorry for my delayed response - assumed I would receive a notification of any posts/replies...

I just uploaded two PS1 files that net similar results (via the URL you provided).

[Tzadok85]

For what it's worth - based on what PrimalScript shows:

The original file that I posed about was "ASCII"
The second example (included in the upload) is "UNICODE LE"...

Thanks!

[Alexander Riedel]

Unfortunately I cannot not run your code here, for obvious reasons. I will try to make some generic samples.
I see nothing unusual in these files though (other than using a WScript popup )
Can you post what actual packager settings you use on those files and what the issue is on the second file?

[Tzadok85]

Yeah, absolutely. Here are the build settings:

Build Settings.jpg (243.32 KiB) Viewed 4436 times

additionally, I have a few more screenshots that show the results of a few different engine types (for the second file):

01 - File 2 - Sapien PS V5 Host (Command Line) x64.jpg (35.52 KiB) Viewed 4433 times

03 - Windows PS (Command Line) x64.jpg (29.07 KiB) Viewed 4431 times

[Tzadok85]

04 - Windows PS (Command Line) Native.jpg (46.46 KiB) Viewed 4430 times

[Alexander Riedel]

Make your extension .ps1 instead of .PS1 and see if that helps.

[Tzadok85]

Innnnnnteresting! so far, this corrected the issue(s) with the second one. I'm assuming (based on these results) that it will likely correct the initial issue too! Well played!

Any idea why this may be?

Thanks a million!