Update from 5.6.160 to 5.6.161 compiled .exe does not run anymore

[Benjamin]

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 delayed as we will be forced to ask you for this information. ***

Product, version and build:
32 or 64 bit version of product: 5.6.160 / 5.6.161
Operating system: Windows 10
32 or 64 bit OS: x64

*** Please add details and screenshots as needed below. ***

Hi Support,

i was working on a PowerShell Forms script today. Saw that there is an update to version 5.6.161. So i did the update (Had version 5.6.160 before on my notebook).

After that, i noticed that when i create an .exe file out of my forms project, the .exe does not start. No errors in event log or somewhere else. debugging in Powershell Studio works fine.
I can open other forms projects and create a .exe file, that works. But not that project i was working on as i did the update to 5.6.161.

I have a second installation of PowerShell Studio which is still o 5.6.160.
Copied the project from my notebook to that machine and compiled an .exe file. this file works as expected.

I know this sounds weird, but it is like i said.
What further information do you need to investigate? could send a video from this behaviour or just screensharing and i can show you.

BR,

Ben

[davidc]

Hello Ben,

Thank you for reporting the issue. I ran a quick test here and I was able to get a GUI to work in a packaged executable. Maybe there is a settings difference between us.

1. Is this a single psf file or a project containing a psf file?
2. What engine / platform are you selecting?
2. If possible, can you zip and upload the file(s) along with the accompanying psbuild file here:

https://www.sapien.com/auth/other/support/upload

[Benjamin]

1. Its a single psf file
2. SAPIEN PowerShell V5 Host (Windows Forms)
3. im not allowed to upload that file

Compiling other psf files work fine. It seems that it is only this single file....
I now just uninstalled powershell studio and reinstaled 5.6.160 with installer from my download folder.
Now it works again for me.
Later this day i try updating to 5.6.161, lets see if i get the same issue again.

BR,

Ben

[davidc]

Package the script using a Command Line engine and see if it outputs any error messages. The Windows Form engine suppresses all output and it is easy to miss an error.

[davidc]

The v5.6.162 service build is now available. Please try this build and let us know if it works for you.