export feature in Powershell Studio

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
User avatar
Carpe_diem
Posts: 22
Joined: Thu Jan 10, 2013 8:35 am

export feature in Powershell Studio

Post by Carpe_diem »

Where could I read more about this function?
I am building some .exe files for end-users (HR , etc) and they run fine on my machine but fail on theirs

they use
Windows 7
and I packaged the .exe as a 32 bit form using PS V3 running in STA mode since I don’t want them to see anything until the textbox completed appears . Do I need to use PS V2?
Thanks for your help
Carpe Diem

User avatar
Alexander Riedel
Posts: 7507
Joined: Tue May 29, 2007 4:43 pm

Re: export feature in Powershell Studio

Post by Alexander Riedel »

Can you define "fail"?

Also, we don't know if you only have V2 on your target machines. Whether V2 will suffice depends on what you are doing in your script.

Most commonly packaged executable fail because the wrong platform is selected or the exe would need elevation but the manifest does not require that.

I believe the manual has a chapter specific to packaging.
Alexander Riedel
SAPIEN Technologies, Inc.

User avatar
Carpe_diem
Posts: 22
Joined: Thu Jan 10, 2013 8:35 am

Re: export feature in Powershell Studio

Post by Carpe_diem »

just setting it to V2 seemed to do the trick

thanks for the hint
Carpe Diem