You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reasoning is that running a powershell script in sandbox is very handy for testing scripts, and while testing you really want to see everything that powershell outputs in the console.
It would take just a little tweak to the powershell command line in RunInSandbox.ps1:
From: powershell.exe -sta -WindowStyle Hidden -NoProfile -ExecutionPolicy Unrestricted -File
To: powershell.exe -sta -NoProfile -ExecutionPolicy Unrestricted -Command `"start powershell {-NoLogo -NoExit -File
(plus of course a closing brace after a file name and any params)
P.S. powershell is already running hidden, no need for -WindowStyle Hidden. I have to add that I did my tests on Windows 11.
The text was updated successfully, but these errors were encountered:
The reasoning is that running a powershell script in sandbox is very handy for testing scripts, and while testing you really want to see everything that powershell outputs in the console.
It would take just a little tweak to the powershell command line in RunInSandbox.ps1:
From:
powershell.exe -sta -WindowStyle Hidden -NoProfile -ExecutionPolicy Unrestricted -File
To:
powershell.exe -sta -NoProfile -ExecutionPolicy Unrestricted -Command `"start powershell {-NoLogo -NoExit -File
(plus of course a closing brace after a file name and any params)
P.S. powershell is already running hidden, no need for -WindowStyle Hidden. I have to add that I did my tests on Windows 11.
The text was updated successfully, but these errors were encountered: