Hi all,
I read Nillth's post about the Packager functionality not auto-incrementing, etc.
I'm also experiencing some issues with that functionality.
I put a value into the packager and it increments the build number and that's all. Subsequent "builds" give no change to the file. Whether or not the Packager dialog is open or not.
Let me know if the behavior has changed in the 2020 version of PowerShell Studio.
Thank you,
Packager behavior not working as expected
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE 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.
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE 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.
- SuperPlated
- Posts: 15
- Last visit: Thu Dec 15, 2022 8:45 am
- Alexander Riedel
- Posts: 8488
- Last visit: Tue Apr 16, 2024 8:42 am
- Been upvoted: 37 times
Re: Packager behavior not working as expected
Yes, its a bug. It happened when the functionality was extracted from PrimalScript and PowerShell Studio and put in the stand alone script packager app.
It will be fixed in the next service release.
Please understand that support is rendered in the individual support forums. You user ID has no product associated and is as such not eligible for support.
If you have a multi-user license, please make sure your user id is associated with the license: https://info.sapien.com/index.php/quick ... vation-key
If you have a single-user license that is managed by someone else but you are the user, please make sure your user id is associated with that license: https://info.sapien.com/index.php/quick ... ation-keys
It will be fixed in the next service release.
Please understand that support is rendered in the individual support forums. You user ID has no product associated and is as such not eligible for support.
If you have a multi-user license, please make sure your user id is associated with the license: https://info.sapien.com/index.php/quick ... vation-key
If you have a single-user license that is managed by someone else but you are the user, please make sure your user id is associated with that license: https://info.sapien.com/index.php/quick ... ation-keys
Alexander Riedel
SAPIEN Technologies, Inc.
SAPIEN Technologies, Inc.