I have been using PowerShell 5.1 ISE at work.
Is there a way to use an Integrated Scripting Environment for PowerShell Core? I would like to continue working on the script that I maintain for work, using PowerShell Core 6. The ISE allows me to work on a large script, debug it and test it
Use Visual Studio Code , as described here
Thank you so very much for the prompt response.
@lstatie I use VSCode it for 5.1 too. Far superior to ISE in almost every way.
Good to know thezim, I will keep that advice in mind. Thank you.
Another question:
I am using VS Code v1.27.0 with Powershell extension 1.8.4. When the script is running and shows errors in the output, There seems to be no way to stop the run so I can fix the issue.
I see a turning circle next to the word "PowerShell" and I can find no way to stop the script from running.
Is there a way to stop the script so I can edit the script and run it again?
The PowerShell ISE allows me to stop running scripts, but debugging there is quite lacking.
Debugging is covered here. The key is finding debug bar (marked C) in the first image on the page. I prefer the keyboard shortcuts myself as they are common with ISE and Visual Studio. Keyboard binding are here. If you are having issues debugging you should file issues in
https://github.com/PowerShell/vscode-powershell. VS Code can be bit overwhelming at first coming from ISE but if you stick with it you will eventually never look back or when your forced to use ISE you will feel like your back using flip phone.
Another question:
I am using VS Code v1.27.0 with Powershell extension 1.8.4. When the script is running and shows errors in the output, There seems to be no way to stop the run so I can fix the issue.
I see a turning circle next to the word "PowerShell" and I can find no way to stop the script from running.
Is there a way to stop the script so I can edit the script and run it again?
The PowerShell ISE allows me to stop running scripts, but debugging there is quite lacking.
For some reason, rebooting my PC fixed the issue I was asking about in the previous post.
Things are working correctly now.
Most helpful comment
Use Visual Studio Code , as described here