To help you better we need some information from you.
*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***
Product: PowerShell Studio 2023 (64 Bit)
Build: v5.8.234
OS: Windows 11.0.25997
PS Version(s): 5.1.25997.1000
*** Please add details and screenshots as needed below. ***
I was working on a project yesterday, and decided to check for updates to see if the new version had a script engine for PowerShell 7.4.0. Saw that it had been added so I installed it. I made a handful of changes, then created a new deployment, pushed it to a machine and tested it and noticed the changes I made weren't working. Well several hours later I realized that when it was building the MSI it was using the wrong version EXE. When I looked at where the packager was saving the exe it was a few subfolders deeper than before, even though I hadn't changed the output location. I tried changing to new folders entirely and whenever it tried to build the installer it would always say it couldn't find the folder location. I changed them back to the original locations, tried using clear output folders, added the "new" location despite the packager output location being identical to before, and it would then successfully package but now the EXE won't open.
Something seems off with this new update and i'm not sure what to do.
DO NOT POST LICENSES, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
*** Please fill in the fields below. If you leave fields empty or specify 'latest' rather than the actual version your answer will be delayed as we will be forced to ask you for this information. ***
Product: PowerShell Studio 2023 (64 Bit)
Build: v5.8.234
OS: Windows 11.0.25997
PS Version(s): 5.1.25997.1000
*** Please add details and screenshots as needed below. ***
I was working on a project yesterday, and decided to check for updates to see if the new version had a script engine for PowerShell 7.4.0. Saw that it had been added so I installed it. I made a handful of changes, then created a new deployment, pushed it to a machine and tested it and noticed the changes I made weren't working. Well several hours later I realized that when it was building the MSI it was using the wrong version EXE. When I looked at where the packager was saving the exe it was a few subfolders deeper than before, even though I hadn't changed the output location. I tried changing to new folders entirely and whenever it tried to build the installer it would always say it couldn't find the folder location. I changed them back to the original locations, tried using clear output folders, added the "new" location despite the packager output location being identical to before, and it would then successfully package but now the EXE won't open.
Something seems off with this new update and i'm not sure what to do.
DO NOT POST LICENSES, KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM
Statistics: Posted by widedata — Thu Nov 30, 2023 6:14 am — Replies 2 — Views 53
