5.6.162 and executable failing, works on 5.6.159

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.
  • Print view
    • User avatar
    albourne
    Posts: 4
    Last visit: Fri Dec 09, 2022 2:25 am

    5.6.162 and executable failing, works on 5.6.159

    Post by albourne »

    Our script is not running on W7 any more on this version of Powershell Studio.
    Used to work flawlessly on v2 forms packager settings for years and now it won't.
    Since this is a Form application, I packaged it as Command Line to see the output.

    Output is below:
    .\program2.3.1.exe
    Line 1790: Missing closing ')' in expression.

    The same executable will run on Windows 10 only if accompanied with the .config file generated, something that wasn't the case in the past.
    We just used the same Forms PSv2 packager settings and it ran on both W10 and W7 without any issues.

    Product, version and build: Powershell Studio
    32 or 64 bit version of product: 64bit
    Operating system: Windows 7 x64
    32 or 64 bit OS: 64

    Works without issues on 5.6.159.


    Thanks,
    Alex
    Top
    User avatar
    davidc
    Posts: 5913
    Last visit: Mon Jul 08, 2019 8:55 am
    Been upvoted: 2 times

    Re: 5.6.162 and executable failing, works on 5.6.159

    Post by davidc »

    Thank you for reporting the issue. I have some quick questions for you:

    1. What is the file's encoding? UTF-8? (PowerShell Studio displays the encoding in bottom right of the status bar).
    2. Does the file contain any unicode characters?
    David
    SAPIEN Technologies, Inc.
    Top
    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.
  • Print view

    • Return to “PowerShell Studio”