Invoke-Script command should support arguments

[michaellwest]

Use case: Pass data to script for execution.

$props = @{
    Path = "License Expiration\Tasks\License Expiration Notification"
    Arguments = $to,$from,$subject,$body
}
Invoke-Script @props

Content of the script:

param(
    [string[]]$To,
    [string]$From,
    [string]$Subject,
    [string]$Body
)

Send-MailMessage @PSBoundParameters

[AdamNaj]

Implemented. Used -ArgumentList like you did in the new remoting module instead of -Arguments like suggested above for consistency.

Now if I save the script like:

param(
    [string[]]$To,
    [string]$From,
    [string]$Subject,
    [string]$Body
)
Write-Host "Sending email from:$from to:$to"

to master:\system\Modules\PowerShell\Script Library\Test\Functions\Mail
I can do the following:

Invoke-Script `
    -Path "master:\system\Modules\PowerShell\Script Library\Test\Functions\Mail" `
    -ArgumentList "to", "from", "subject", "body"

And here's the result:

[michaellwest]

Just to add to your reasoning, there are many more commands using ArgumentList than Arguments. Here's a sample.

Arguments with hashtable

• Set-WmiInstance

ArgumentList with Object[]

• New-Object
• Invoke-Command
• ForEach-Object