Get-Command's System.Management.Automation.AliasInfo object should return an 'IntroducedIn' Property
Votes from Connect: 5
Original Date Submitted: 10/29/2014 11:53:04 PM
Handle: Stephen Owen
Site Name: PowerShell
Feedback ID: 1014669
Frequency: Always Happens
Regression: Yes, this happens in all previous versions
Currently there is no easy method to determine which version of PowerShell a particular cmdlet will work within.
Take the example of New-PSDrive. This command was introduced in PowerShell version 2.0, but the current Version property displayed when I run 'Get-Command New-PSDrive | Format-List' displays the value of 3.1.
While this cmdlet was included in 3.0 and 4.0, it is misleading that the version of 3.1 is displayed, when the cmdlet will function perfectly within PowerShell version 2.0.
In a lively discussion on the matter today on Twitter with a number of PowerShell MVPs, we were unable to find a conclusive command or one-liner to run to obtain the base version of a cmdlet, or the version in which it was introduced.
While adding this data to all existing cmdlets would be quite a workload, I think this is valuable information which helps provide teachable moments and added information to the PowerShell Command Line Interface experience.
Product Studio item created by Connect Synchronizer due to creation of feedback ID 1014669 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1014669).
Get-Command New-PSDrive | Select Version
Get-Command New-PSDrive | Select Version,IntroducedIn
Internal BugId: 13074