-
Notifications
You must be signed in to change notification settings - Fork 32
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
Migrate to cross-platform PowerShell Core 6.0 #88
Comments
I think that we better add PowerShell Core support while keeping compatibility with PowerShell 5.1 (because it's still the only pre-installed PowerShell option on supported Windows' versions). |
Also, modules created for Windows Powershell (5.1 and prior) may not be compatible (as-is) with Powershell Core. https://docs.microsoft.com/en-us/powershell/gallery/concepts/module-psedition-support |
any news on this? Maybe a "clone/fork" project could be created for powershell-core, to not "break" the old one? |
I doubt Windows Powershell (.NET Framework) is disappearing any time soon. Ideally, it would be supported alongside Core as long as anyone cares, but I'm not sure that's feasible or possible in a single library. Maybe it would make more sense to migrate all PS support to their own packages:
|
Alternatively (and I'm not a current user, so take this with a grain of salt) - move to powershell core only. This project is OSS and community-maintained, and maintaining legacy support is expensive. If a company needs that support, they should either sponsor its development by the maintainers financially or assign developers to maintain it in this project. |
PowerShell Core 6.0 is a new edition of PowerShell that is cross-platform (Windows, macOS, and Linux), open-source, and built for heterogeneous environments and the hybrid cloud.
The text was updated successfully, but these errors were encountered: