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 9 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.
Product: PowerShell Studio 2019 (64 Bit)
Build: v5.6.165
OS: Windows 10 Pro (64 Bit)
Build: v10.0.17134.0
I have a script that I have been building into an exe with Powershell Studio 2017
The script runs without errors and the exe that was build runs without errors
When I upgraded to 2019, the exe gets built from the same ps1 without errors BUT when I run the exe it now errors out. Below is the error I get form the command prompt while executing.
jeffrey.sikorski@compucom.com wrote: ↑Fri Jul 05, 2019 5:55 am
It looks like changing the encoding to UTF-8-BOM fixed the issue.
Actually, it did not fix the issue. I still get the same error. I think I got a false positive by running the wrong exe. But it is a couple of days later and no matter what encoding I choose or build options I keep getting the same error as before.
It's caused the code injection to set $PSScriptRoot correctly in packaged code.
It will be fixed in the next service build.
You can leave out the Cmletbinding statement, if possible, and it will package correctly.
This topic is 4 years and 9 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.