SAPIEN Technologies

Based on the error message, you are missing an assembly.

Based on searching online, I found the following that may be helpful:
https://github.com/AutomatedLab/Automat ... ssues/1670
https://gist.github.com/jborean93/f6f27 ... 3e28f5f660

[Topic was moved by moderator to PowerShell Forum]

Please answer the following questions: - Do you get this error with other projects or just this one? - If you navigate to the install folder, can you open SAPIEN Script Packager from there? - Are you able to run (F5) the project? If possible, please try updating to a later build as there have been ...

The setting to disable this feature can be found under Options->Designer->Control Settings:

This issue has been resolved in the next service release. I do not have an ETA at this time.

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.