It is interesting to compare these uses of"*" * 35PS C:> "*" * 35***********************************PS C:> 35 * "*"The '*' operator failed: Cannot convert value "*" to type"System.Int32". ...(string's * operator is not commutative)PS C:> write-output "*" * 35**35PS C:> write-output ("*" * 35)***********************************(using Write-Output is tricky)For someone coming across this later.
Because asterisk is a special character in Powershell, you must use the escape character before it if you want it to be interpreted literally by Powershell:
"`*"*35
BPK
Absolutely not true in any way. Where did you get such a silly idea?
'*' * 35
Works as expected.
Because of precedence by order the expression must place the string first. Placing a number first causes the parser to try an dconvert the string into a number first.
Basic PowerShell.
\_(ツ)_/