Re:Microsoft’s PowerShell Core Offers Cross-Platform Automation
by Arnavion on Monday January 22, 2018 @07:18PM
(#16209555)
>That's not quite correct (and neither is that StackOverflow answer).
The SO answer isn't wrong. The EXE there has a space in the path. The answer uses a string literal for it and thus needs &. It could of course escape the spaces with ` instead; then it wouldn't need a string literal and thus not need &.
If you want to execute the EXE stored in a variable or whatnot, then yes, you need `&`, which I think is borrowed from Perl. But otherwise, the rules in PowerShell are the same as a Unix shell: if it's in the PATH, just type the command name (with or without the .exe); otherwise, use the full path.