SAPIEN Technologies

Thank you for reporting. We are looking into this and will get back to you soon.

Any packaged exe will instantiate the currently installed PowerShell version. Generally, you should always package for the version installed on a system. As you can see from the error, the package does not actually work on a system that is not matching the packaged version. This is because .NET does...

Thank you for reporting. We are aware of the issue when packaging with PowerShell 7.4.6. A fix will roll out with the next service release. I do not have an ETA at this time.

If you are packaging with a PowerShell 7.4.6 engine, there is a known issue with PowerShell 7.4.6: viewtopic.php?p=86580#p86580
A fix will roll out with the next service release. I do not have an ETA at this time.

Since you are initially declaring the variable in the MainForm, its best to use the $script: scope when you reference/change that variable. This would mean updating the variable in the child form to the $script: scope.

Yes, the trial pop-up will be removed once the packaged script is rebuilt with a licensed version of PowerShell Studio.

I have an update regarding this issue. After some digging, we have discovered that this is related to a Microsoft packaging issue between .NET 8, .NET 9, and PowerShell 7. An assembly that is being referenced was not included in PowerShell 7/.NET 8. This is causing code needed to load the ProgressBa...

Check out our blog:
https://www.sapien.com/blog/2024/12/02/ ... tarts-now/

You may find the following helpful:
https://info.sapien.com/index.php/guis/ ... jects-work

[Topic moved to PowerShell GUIs by moderator]