We get an increasing number of inquiries asking what the future for ISESteroids is, and whether we plan to move to VSCode. Here is some background, and some answers! Disclaimer: the infos we summarized here on PowerShell and related technologies represent our conclusions. They could be wrong. If so, please drop us a message. Future of Windows PowerShell In May this year, PowerShell inventor Jeffrey Snover explained at psconf.eu that Windows PowerShell is “done”. It will continue to be part of current and future versions of Windows, and continue to ship out of the box. Based on full .NET Framework, it supports almost everything a Windows Admin needs to control. Windows PowerShell will not evolve anymore, though. According to Jeffrey, all future investments go into PowerShell Core (aka PowerShell 6). The name “PowerShell 6” is to a tiny bit misleading as PowerShell Core is not the technical continuation of Windows PowerShell. Instead, it is a different breed, based on .NET Core which is basically a subset of the full .NET Framework. Windows PowerShell vs. PowerShell Core PowerShell Core by design cannot target all the things Windows PowerShell can, and many existing modules won’t currently run in PowerShell Core. For example, neither the ActiveDirectory module nor Exchange are currently supported in PowerShell Core. Graphical user interfaces based on WinForms or WPF won’t run, either. PowerShell Core’s unique selling point at this point is its cross-platform reach: the smaller .NET Core can run not just on Windows but also on Linux and MacOS. This is…