Invokes PipeScript or PowerShell ScriptBlocks, commands, and syntax.

Runs PipeScript.

Invoke-PipeScript can run any PowerShell or PipeScript ScriptBlock or Command.

Invoke-PipeScript can accept any -InputObject, -Parameter(s), and -ArgumentList.

These will be passed down to the underlying command.

Invoke-PipeScript can also use a number of Abstract Syntax Tree elements as command input:

• Use-PipeScript

• Update-PipeScript

PipeScript is a superset of PowerShell. So a hello world in PipeScript is the same as a "Hello World" in PowerShell:

Invoke-PipeScript { "hello world" } # Should -Be "Hello World"

Invoke-PipeScript will invoke a command, ScriptBlock, file, or AST element as PipeScript.

Invoke-PipeScript { all functions } # Should -BeOfType ([Management.Automation.FunctionInfo])

The input object. This will be piped into the underlying command. If no -Command is provided and -InputObject is a [ScriptBlock]

The Command that will be run.

A collection of named parameters. These will be directly passed to the underlying script.

A list of positional arguments. These will be directly passed to the underlying script or command.

The OutputPath. If no -OutputPath is provided and a template file is invoked, an -OutputPath will be automatically determined. This currently has no effect if not invoking a template file.

If this is not set, when a transpiler's parameters do not take a [ScriptBlock], ScriptBlock values will be evaluated. This can be a very useful capability, because it can enable dynamic transpilation. If this is set, will make ScriptBlockAst values will be run within data language, which significantly limits their capabilities.

Invoke-PipeScript [-InputObject <PSObject>] [[-Command] <PSObject>] [-Parameter <IDictionary>] [-ArgumentList <PSObject[]>] [-OutputPath <String>] [-SafeScriptBlockAttributeEvaluation] [<CommonParameters>]