SAPIEN Technologies

We are looking into this and will get back to you soon with any information/ideas we have.

Can you upload your script so I can better assist you? https://www.sapien.com/support/upload Please make sure all forms objects you are currently referencing are present from the Design tab and all events are registered to the objects. You may find the following article helpful: https://www.sapien.c...

For Code Recovery, please follow the steps detailed here:
https://www.sapien.com/blog/2021/11/22/ ... -what-now/

Under the Script tab, you should see all form objects from PrimalSense when you type '$' with the autocomplete functionality.

No, this was intentional. All form data is stored in the PSF as XML. Objects are serialized and de-serialized in XML. When you run or package a PSF, PowerShell Studio is generating the code from the XML alongside your code into a PS1. You can always export your PSF to a PS1 (Deploy->Export) and see ...

This issue has been resolved and the fix will be included in the next service release. There is no ETA for the release of the next service build yet.

I have confirmed this behavior and have filed a bug report for the development team. I'll update you if I have new information.

SAPIEN Script Packager is not a compiler. A compiler translates source code into machine code which is not easily reversible. C/C++ is a good example for that. C# is translated into ILASM and only compiled at the endpoint. Very easy to de-compile. The tool SAPIEN Script Packager, included in PowerSh...

The only Microsoft Visual C++ Redistributable runtime needed should be the 2015-2022 x64 version from here:
https://learn.microsoft.com/en-us/cpp/w ... w=msvc-170

We will look into this and get back to you soon.