Related: How can Powershell compares between string and double?
Summary of the new feature / enhancement
Currently an unquoted number with two or more dots casts to a $Null instead of leaving an expected ... is not recognized as a name of a cmdlet error.
$Version = 2.0.9
$Null -eq $Version
True
I would like to suggest to cast numbers with 3 or 4 dots (as 2.0.9 and 2.0.7.0) automatically to a version as a semantic PowerShell sugar.
Related: How can Powershell compares between string and double?
Summary of the new feature / enhancement
Currently an unquoted number with two or more dots casts to a
$Nullinstead of leaving an expected... is not recognized as a name of a cmdleterror.I would like to suggest to cast numbers with 3 or 4 dots (as
2.0.9and2.0.7.0) automatically to a version as a semantic PowerShell sugar.