Skip to content

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

Closed
JeremyTBradshaw opened this issue Nov 21, 2019 — with docs.microsoft.com · 5 comments · Fixed by #5147
Closed

Question: Is PowerShell ISE actually no longer in developement? #5138

JeremyTBradshaw opened this issue Nov 21, 2019 — with docs.microsoft.com · 5 comments · Fixed by #5147
Assignees
Labels
area-ise Area - PowerShell ISE

Comments

Copy link
Contributor

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.

@sdwheeler sdwheeler added the area-ise Area - PowerShell ISE label Nov 21, 2019
@mklement0
Copy link
Contributor

From https://docs.microsoft.com/en-us/powershell/scripting/components/ise/introducing-the-windows-powershell-ise#support (emphasis added):

"
Support

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.
The ISE, however, is in maintenance mode and no new features are likely to be added.
Additionally, there is no support for the ISE with PowerShell v6 and beyond.
Users wanting a graphical tool with which to manage PowerShell scripts, etc, should consider Visual Studio Code.
"

@JeremyTBradshaw
Copy link
Contributor Author

Thank you very much.

@joeyaiello
Copy link
Contributor

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.

@joeyaiello joeyaiello reopened this Nov 22, 2019
@joeyaiello
Copy link
Contributor

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.

@sdwheeler sdwheeler assigned sdwheeler and unassigned joeyaiello Nov 22, 2019
sdwheeler added a commit that referenced this issue Nov 22, 2019
* Fixes #5138 - ISE support policy

* fix broken links and remove old docsets

* fix typo in ops config

* feedback fixes
@JeremyTBradshaw
Copy link
Contributor Author

Thanks again. Glad the official status of ISE is still OK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-ise Area - PowerShell ISE
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants