This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM. Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 4 years and 11 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
*** 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. ***
There is only one button, very simple.
EXE execution without any screen
Snipaste_2019-04-25_15-24-54.png (10.94 KiB) Viewed 2946 times
Alexander Riedel wrote: ↑Thu Apr 25, 2019 6:58 am
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 (16.43 KiB) Viewed 2914 times
If you can't use the text directly, then this should be a big bug!
I have tried this version before. PowerShell Studio 2018 v5.5.152 has no problems.
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 seeing.
We are compensating and fixing it in the next service build.
There is however absolutely no harm in using Unicode files to begin with.
Alexander Riedel wrote: ↑Thu Apr 25, 2019 7:26 am
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 seeing.
We are compensating and fixing it in the next service build.
There is however absolutely no harm in using Unicode files to begin with.
How do I know the code I am using now?
I can't find the conversion code in the status column.
Snipaste_2019-04-25_22-34-44.png (74.45 KiB) Viewed 2908 times
Snipaste_2019-04-25_22-36-14.png (31.72 KiB) Viewed 2908 times
This topic is 4 years and 11 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.