SAPIEN Technologies

There are a couple different factors that can attribute to this such as the complexity of the form and the script engine you are using to package. Verify that you are not creating any form objects that you are not using. You can view all your controls from the Select tab of the Toolbox pane or from ...

How are you checking for updates? Through the update tool (Help->Updates), in-product notifications (Top-Right corner of the application), or your Registered Product page?
Can you please provide a screenshot of what you are seeing?

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

Please upload your executable here and we will see what we can do:
https://www.sapien.com/support/code_rec ... 8/PremSupp

This link can also be found on your Registered Products page:

Please upload your project here:
https://www.sapien.com/support/upload

Does this also happen after running your script outside of PowerShell Studio or when running in console (Ctrl + F8)? I was not able to reproduce this behavior and without seeing the rest of you code, I can only make suggestions. Though I cannot see if this is the case, its generally a good rule to n...

This is correct. You should not be able to directly reference form controls from Globals.ps1 or Startup.pss and this is because of the scope of the controls. Yes, at the when a project runs or is exported, all project files with a Build settings of Include will be combined into one script, but forms...

You may find the following articles helpful:
https://www.sapien.com/blog/2019/08/19/ ... ositories/
https://docs.github.com/en/github/getti ... set-up-git

At this point in time, PowerShell Studio does not include any such similar functionality like Live Share.

This can be done with two custom actions: One to create the shortcut on install and one to delete the shortcut on delete. Though this blog is a little older, it has scripts for creating and removing a desktop shortcut: https://www.sapien.com/blog/2019/08/15/sapien-creating-an-msi-installer-for-a-pac...