Try quoting the argument list: Start-Process -FilePath “C:\Program Files\MSBuild\test.exe” -ArgumentList “/genmsi/f $MySourceDirectory\src\Deployment\Installations.xml” You can also provide the argument list as an array (comma separated args) but using a string is usually easier.
I’m not sure this is the best, but: function A{ Param([scriptblock]$FunctionToCall) Write-Host “I’m calling $($FunctionToCall.Invoke(4))” } function B($x){ Write-Output “Function B with $x” } Function C{ Param($x) Write-Output “Function C with $x” } PS C:\WINDOWS\system32> A -FunctionToCall $function:B I’m calling Function B with 4 PS C:\WINDOWS\system32> A -FunctionToCall $function:C I’m calling Function C with 4 … Read more
The drive is provided by the WebAdministration module, so you need to install/import that module first. How you install the module depends on your actual system and whether you use GUI or PowerShell. On a Windows Server 2008 R2 for instance you’d install the module with the following PowerShell commands: Import-Module ServerManager Add-WindowsFeature Web-Scripting-Tools After … Read more
There is a function up on the PowerShell Team blog called Resolve-Error which will get you all kinds of details Note that $error is an array of all the errors you have encountered in your PSSession. This function will give you details on the last error you encountered. function Resolve-Error ($ErrorRecord=$Error[0]) { $ErrorRecord | Format-List … Read more
Pretty grid $colors = [enum]::GetValues([System.ConsoleColor]) Foreach ($bgcolor in $colors){ Foreach ($fgcolor in $colors) { Write-Host “$fgcolor|” -ForegroundColor $fgcolor -BackgroundColor $bgcolor -NoNewLine } Write-Host ” on $bgcolor” } Updated colours in newer powershell: https://gist.github.com/timabell/cc9ca76964b59b2a54e91bda3665499e
It returns true if the last command was successful, else false. However, there are a number of caveats and non-obvious behaviour (e.g. what exactly is meant by “success”). I strongly recommend reading this article for a fuller treatment. For example, consider calling Get-ChildItem. PS> Get-ChildItem PS> $? True $? will return True as the call … Read more
Unless you read the input file into memory in full, up front, you cannot safely read from and write back to the same file in a given pipeline. Specifically, a command such as Import-Csv file.csv | … | Export-Csv file.csv will erase the content of file.csv.[1] The simplest solution is to enclose the command that … Read more
tl;dr While Joel Coehoorn’s helpful answer provides an effective solution to your Start-Process problem (which stems from the bug detailed below), you can simplify your code to: foreach ($file in $myfiles) { # Note: | Out-Null is a trick that makes calling *GUI* applications # *synchronous* (makes PowerShell wait for them to exit). & $npp … Read more
If you construct a string such as -t foo and pass it via a variable to an external program, it is passed as a single, double-quoted argument (that is, donet will literally see “-t foo” on its command line) – and therefore won’t be recognized as parameter name-value combination. You must pass -t and foo … Read more
Note that [securestring] is not recommended for new code anymore. While on Windows secure strings offer limited protection – by storing the string encrypted in memory – via the DPAPI – and by shortening the window during which the plain-text representation is held in memory, no encryption at all is used on Unix-like platforms.[1] The … Read more