Skip to content

Powershell version relation to .Net Standard, Core and/or framework versions #12215

@viralmodi

Description

@viralmodi

I have spend quite a lot of time looking for answer to this question but could not find it. While this might not be the correct forum for this type of question but I couldn't find any other forum to ask this. I really need some help here since I couldn't even find an answer on reading Microsoft Powershell docs.
I want to know the relation between Powershell versions (windows powershell and powershell core) and .Net Standard (Core and Framework) versions.
As a concrete example, If I have a powershell cmdlet built for target framework .Net Standard 2.0, how do I find which powershell versions (both windows powershell and powershell core), will it work on?
My understanding was as long as .Net Standard 2.0 or higher based implementation of .Net Core or .Net framework is installed on users machine, it doesn't matter which powershell version the user uses. The cmdlet should work. But then, users don't explicitly install these .NET versions on their machines. They are installed by default on Windows or as part of powershell core(?) on cross platform OSes. Can someone please help understand this relation and answer my question?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-Questionideally support can be provided via other mechanisms, but sometimes folks do open an issue to get aResolution-AnsweredThe question is answered.WG-DevEx-SDKhosting PowerShell as a runtime, PowerShell's APIs, PowerShell Standard, or development of modules

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions