Powershell's "native executable" story (running things which aren't cmdlets) has never been simple or graceful [1], which means that posh scripters might call e

Powershell's "native executable" story (running things which aren't cmdlets) has never been simple or graceful [1], which means that posh scripters might call exes like curl more explicitly and avoid the alias altogether. After months of varaible-expansion-frustration I have alnded on the form "& foo.exe par1 par2", spelling out the .exe and avoiding the alias. [1](https://web.archive.org/web/20110726162028/http://huddledmasses.org/the-problem-with-calling-legacy-or-native-apps-from-powershell/ https://web.archive.org/web/20110726162028/http://huddledmas...)