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

Please add PowerShell supported version to cmdlet help #1105

Closed
f0rt opened this issue Mar 20, 2017 · 7 comments
Closed

Please add PowerShell supported version to cmdlet help #1105

f0rt opened this issue Mar 20, 2017 · 7 comments

Comments

@f0rt
Copy link

@f0rt f0rt commented Mar 20, 2017

Team,

Please add to cmdlet help which PowerShell version it was released wtih. We have internal build system VMs with PS 3.0. Every time we're using a cmdlet we had to check if the cmdlet exist on PS 3.0. This is a pain because our local workstations are with PS 5.1.

Thanks,
Nedko

@zjalexander

This comment has been minimized.

Copy link
Contributor

@zjalexander zjalexander commented Apr 27, 2017

Also raised as a UserVoice item, crosslinking: https://windowsserver.uservoice.com/forums/301869/suggestions/19073182

@ghost ghost added the reference label May 23, 2017
@mklement0

This comment has been minimized.

Copy link
Contributor

@mklement0 mklement0 commented Sep 13, 2017

That would certainly be a very helpful complement to the existing practice of noting when a new parameter was introduced.

@PolarBearGod

This comment has been minimized.

Copy link

@PolarBearGod PolarBearGod commented May 31, 2018

Has there been any further update to this issue?

@joeyaiello

This comment has been minimized.

Copy link
Collaborator

@joeyaiello joeyaiello commented Oct 4, 2018

We will be doing this for versions going forward, but this will not be done all up and backfilled for old versions. Sorry....

@joeyaiello joeyaiello closed this Oct 4, 2018
@kubilayelmas

This comment has been minimized.

Copy link

@kubilayelmas kubilayelmas commented Nov 16, 2018

having this feature would be really useful. It's very time consuming and frustrating to find out that half of your cmdlets are not working in your script, on some older systems. Looking forward to have this feature. I'm sure that the get-command cmdlet can have a parameter to display that information.

@mklement0

This comment has been minimized.

Copy link
Contributor

@mklement0 mklement0 commented Nov 16, 2018

@kubilayelmas:

Agreed. In the meantime, try this (which has limitations).

@alfredmyers

This comment has been minimized.

Copy link
Contributor

@alfredmyers alfredmyers commented Jan 17, 2019

Having to switch the version combo to find the version of PowerShell where a cmdlet was introduced is cumbersome.
At least, indicate what is the version of PowerShell a given cmdlet was introduced.
The folks over the .NET API Browser have resolved it adding an Applies to section where all versions of the .NET Framework a given type or member are supported are listed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.