Product: PowerShell Studio 2021 (64 Bit)
Build: v5.8.196
OS: Windows 10 Enterprise (64 Bit)
Build: v10.0.19043.0
When I attempt to build the attached package, PSS hangs. The cause is the SETTINGS BUILD COMMAND (cnwpackage.exe, script attached). If I remove this then the PSF package process completes. Of course my cnwpackage scripts processes are required so not using it is not desirable.
Could this please be looked at with some urgency.
Thanks
After upgrading to 5.8.196 unable to build package psf
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.
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.
After upgrading to 5.8.196 unable to build package psf
- Attachments
-
- cnwpackage.ps1
- (7.15 KiB) Downloaded 151 times
-
- Mainform.psf
- Windows Forms PS script
- (74.34 KiB) Downloaded 148 times
Re: After upgrading to 5.8.196 unable to build package psf
Can you please upload the corresponding psbuild file here:
https://www.sapien.com/support/upload
Can you please elaborate on what you mean by 'SETTINGS BUILD COMMAND'?
Does it also hang if you build through the SAPIEN Script Packager (Deploy->Packager->Settings)?
https://www.sapien.com/support/upload
Can you please elaborate on what you mean by 'SETTINGS BUILD COMMAND'?
Does it also hang if you build through the SAPIEN Script Packager (Deploy->Packager->Settings)?
Brittney
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.
Re: After upgrading to 5.8.196 unable to build package psf
Have uploaded zip as requested,
settings build command below
settings build command below
Re: After upgrading to 5.8.196 unable to build package psf
I can't reproduce the issue in our test environment.
I was able to package MainForm (with setting for the Post-build command) with no issue.
Packaging completed ok, but I got error while executing crwpackage.exe
------ Build started: Mainform, Configuration: x64 ------
Packaging with SAPIEN PowerShell V5 Host (Windows Forms) x64
Adding C:\123_newFolder\Mainform\Mainform.Package.ps1
Writing scripts to bin\x64\Mainform.exe
Embedding default manifest...
Package completed
cnwpackage v1.0.0.6
Exception: Unable to obtain package name
0 error(s), 0 warning(s)
Could you please provide more details for that issue (attached zip file with only one Mainform file in it)
- what is crwpackage.exe? have you tried to run it alone before packaging?
- how did you create that file?
- please attach .psbuild files
I was able to package MainForm (with setting for the Post-build command) with no issue.
Packaging completed ok, but I got error while executing crwpackage.exe
------ Build started: Mainform, Configuration: x64 ------
Packaging with SAPIEN PowerShell V5 Host (Windows Forms) x64
Adding C:\123_newFolder\Mainform\Mainform.Package.ps1
Writing scripts to bin\x64\Mainform.exe
Embedding default manifest...
Package completed
cnwpackage v1.0.0.6
Exception: Unable to obtain package name
0 error(s), 0 warning(s)
Could you please provide more details for that issue (attached zip file with only one Mainform file in it)
- what is crwpackage.exe? have you tried to run it alone before packaging?
- how did you create that file?
- please attach .psbuild files
Re: After upgrading to 5.8.196 unable to build package psf
Ahhhh, just figured out it was an issue signing the executable where it looks like I was using an old cert. I have no idea how that happened but after I went back into the certificate settings and reselected the certificate, everything starting working again.
Sorry to have caused unnecessary work from your end.
BTW the cnwpackage moves files into our software file server repository and also encrypts the source so I would not expect this to work anywhere other than our environment.
Sorry to have caused unnecessary work from your end.
BTW the cnwpackage moves files into our software file server repository and also encrypts the source so I would not expect this to work anywhere other than our environment.