-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Question: Is PowerShell ISE actually no longer in developement? #5138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Is PowerShell ISE actually no longer in developement? #5138
Comments
From https://docs.microsoft.com/en-us/powershell/scripting/components/ise/introducing-the-windows-powershell-ise#support (emphasis added): " The ISE was first introduced with Windows PowerShell V2 and was re-designed with PowerShell V3. The ISE is supported in all supported versions of Windows PowerShell up to and including Windows PowerShell V5.1. |
Thank you very much. |
The PowerShell ISE is no longer in active feature development, but as a shipping component of Windows, it will continue to be officially supported for security and high-priority servicing fixes. We currently have no plans to remove the ISE from Windows. |
Thanks for the response, @mklement0! I hit "Comment" before I saw your update. @sdwheeler still wants to make sure we document this in the docs, so I'm reopening here. |
Thanks again. Glad the official status of ISE is still OK. |
Hello, I see it being said on a lot of blogs, which tend to favor VSCode, example:
https://adamtheautomator.com/how-to-make-visual-studio-code-look-and-behave-like-the-powershell-ise/
But I'm struggling to find any official statement to back this. Are you able to confirm whether or not the ISE is no longer being worked on?
The reason I ask is that the debugging and integrated console experiences are still night and day better with ISE. I do like VS Code, but the PowerShell extension pales in comparison to ISE for stability and performance, but most notably with debugging and the integrated console. VS Code wins in other areas such as PSScriptAnalyzer, for example, but where there is overlap, PowerShell ISE seems to win.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: