PowerShell ISE (Integrated Scripting Environment) Basics
Video Statistics and Information
Channel: skunklabz
Views: 7,131
Rating: 4.9139786 out of 5
Keywords: SkunkLabz, Episode 13, PowerShell, PowerShell ISE, Scripting, Windows, IDE
Id: pJh2xlDMEcQ
Channel Id: undefined
Length: 21min 46sec (1306 seconds)
Published: Mon Aug 24 2020
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.
If you're just learning the basics, you'd be better off starting on Code which is MS's recommended platform now that ISE is retired.
Yeppers, ISE not going anywhere. It's part of the OS, therefor always at hand. Unlike VSCode.
It still, my primary goto for daily work. I have it heavily customized, and many of my customizations don't work in VSCode or are more work to use). Lastly, especially when I am customer sites that will not install other stuff, period.
Major PS projects are Sapiens PS, VSCode (mostly because of cross-platform use cases and training others), and Visual Studio Ent.
Dev should be using VSCode, which was it main target on release, and until MS ships VSCode in the box (and they should to not only replace the ISE but notepad as well), it will not be on any enterprise-level server and not in data centers. Well, not with any customer I've supported to date. So, anyone, discouraging the use of ISE is just not prudent at all. Except in the personal standalone use case or developer.
Only since MS has been pushing VSCode has the normal admin been seeing it come up. Well, that many of the PS MVP and other presenters using it and also key for any PSCore stuff cross-platform.
ISE and Powershell 5.1 still come with Windows 10, so they're hardly obsolete. I still use the ISE sometimes when I want to copy and paste unicode characters. Although my editor is usually Emacs.
ISE is much simpler to use then VS code. Maybe if code got a better toolbar.