Skip to content
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

Open
sergey-tihon opened this issue Jan 12, 2018 · 5 comments
Open

Migrate to cross-platform PowerShell Core 6.0 #88

sergey-tihon opened this issue Jan 12, 2018 · 5 comments

Comments

@sergey-tihon
Copy link
Member

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.

@ForNeVeR
Copy link

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).

@jcmrva
Copy link

jcmrva commented May 30, 2018

@jkone27
Copy link

jkone27 commented Nov 8, 2021

any news on this?
would be great to have this provider in NET5/NET6 :) this is an awesome provider and support for powershell-core might be the only thing needed.

Maybe a "clone/fork" project could be created for powershell-core, to not "break" the old one?
like FSharp.Management.NetCore

@jcmrva
Copy link

jcmrva commented Apr 25, 2022

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:

  • FSharp.Management (rename to FSharp.Management.Windows?)
  • FSharp.PowerShell
  • FSharp.PowerShellCore

@baronfel
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants