ansaurus

Question

Must PowerShell scripts be called using only a single line?

Answer 1

+11 A:

PowerShell thinks the command is complete at the end of the line unless it sees certain characters like a pipe, open paren or open curly. Just put a line continuation character ` at the end of each line but make sure there are no spaces after that continuation character:

myScript.ps1 `
  -completePathToFile "C:\...\...\...\file.txt" `
  -completePathForOutput "C:\...\...\...\output.log" `
  -recipients (
    "[email protected]", `
    "[email protected]" `
   )

If you're on PowerShell 2.0 you can also put those parameters in a hashtable and use splatting e.g:

$parms = @{
    CompletePathToFile   = 'C:\...\...\...\file.txt'
    CompletPathForOutput = 'C:\...\...\...\output.log'
    Recipients           = '[email protected]','[email protected]'
}
myScript.ps1 @parms

Keith Hill 2010-01-13 15:14:13

I've found that the comma operator is enough to make Powershell continue to the next line, SO LONG AS it's actually parsing it as an operator and not a string parameter that ends in ','

Richard Berg 2010-01-14 01:15:10

Thanks. I'm sure there other characters indicate to PowerShell there's more. Not sure there is a documented list of these.

Keith Hill 2010-01-14 01:23:51

Keith, thanks for remininding me there is a splatting in Posh. I read it and then forget. Now I see that it brings a lot of possibilities of how to work with script/function parameters.

stej 2010-01-14 05:14:12

ansaurus

tags:

views:

answers:

Must PowerShell scripts be called using only a single line?

related questions