SAPIEN Technologies

To help you better we need some information from you. *** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be Product: PowerShell Studio 2019 (64 Bit) Build: v5.6.162 OS: Windows Server 2012 R2 Standard (64 Bit) Build: v6....

Sorry, I changed to UTF16-LE. Correctly executed. Curious why UTF-8 can't use the old version but it works.

Here: SPS Encoding.png Unicode is UTF-16 LE, in case you are not familiar with encodings My default is UTF-8. The same file I copied to the v5.5.152 version environment package EXE. It can be executed smoothly. Once again, I emphasized the problem I encountered. I just turned into an EXE file and t...

You can switch the encoding in PowerShell Studio on the status bar. The packager works internally with Unicode to add variable settings to your code for a recent feature request. The round trip conversion in Windows from UTF-8 to Unicode to UTF-8 should work, but does not. So that's the bug you are...

Please try switching your encoding to Unicode LE and see if that fixes the problem. I tested unicode and used notepad++ to modify the encoding. If it is unicode caused by why there is no error in the Run. Is there an error after the package is executed as an exe? Snipaste_2019-04-25_22-21-01.png If...

*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your Product: PowerShell Studio 2019 (64 Bit) Build: v5.6.162 OS: Windows Server 2012 R2 Standard (64 Bit) Build: v6.3.9600.0 *** Please add details and screenshots as needed below. *** ...

Hello, if you mean to modify the config file,look like this Snipaste_2019-04-23_09-24-53.png That problem will return to what I encountered at the beginning, and the package must be modified once. https://www.sapien.com/forums/viewtopic.php?f=12&t=13838#p73059 Snipaste_2019-04-23_09-30-48.png If...

Powershell execution is ok Execution is still wrong

Please update to the v162 service build. It will resolve the manifest issue as well as an encoding issue introduced in the v161 service build. The v162 build also includes a manifest template you can access via the File->New menu. The template (Custom Packager Manifest) is located under the Other c...

Your manifest create option is still set to "Embed a default manifest". Make sure you selected "Embed a custom manifest" before building the executable. Thank you for your help. I have chosen to customize according to your notification. Snipaste_2019-04-19_11-47-14.png But after...