-
Notifications
You must be signed in to change notification settings - Fork 8.3k
powershell -version 2 should return error #4834
Copy link
Copy link
Closed
Labels
Issue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-Won't FixThe issue won't be fixed, possibly due to compatibility reason.The issue won't be fixed, possibly due to compatibility reason.WG-Interactive-Consolethe console experiencethe console experience
Metadata
Metadata
Assignees
Labels
Issue-Discussionthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifthe issue may not have a clear classification yet. The issue may generate an RFC or may be reclassifResolution-Won't FixThe issue won't be fixed, possibly due to compatibility reason.The issue won't be fixed, possibly due to compatibility reason.WG-Interactive-Consolethe console experiencethe console experience
As far as I know, PowerShell v2 was recently declared deprecated.
Thus, it normal to expect some kind of related errors in the latest v6.
The behaviour is strange, though. If I try to invoke something (anything
actually, including gibberish) with
-version 2then PowerShell succeeds(
$LASTEXITCODEis 0) and prints the same resultpowershell v6.0.0-beta.7.Steps to reproduce
Expected behavior
Non-zero
$LASTEXITCODEand a clear error message.Actual behavior
Zero
$LASTEXITCODEand some version-like text, the same regardless of a command.Environment data
PowerShell-6.0.0-beta.7-win-x64.zip