SAPIEN Technologies

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.

I've been able to reproduce this behavior and have filed a bug report for the development team. I'll update you when I have more information.

Please try build 5.8.219 and let me know if this issue persists.

Are your files ClassZ.ps1 and EnumA.ps1 Build setting set to 'Include' or 'Content'?

From your previous upload, I'm not able to reproduce this behavior when the project files Build setting is set to 'Include':

Please try updating to the latest build and let me know if you are still experiencing this behavior.

Were you experiencing this prior to build 5.8.213?