Execution

Author(s)

• Manuel

Tags

Execution Self-Elevation Stub PowerShell Windows

Functions

Clear-TempDirectories ConvertTo-SplatHashtable Exit-AndWaitOnUI Format-SplatHashtable Get-QuotedPath Invoke-NativeCommand Invoke-StubScript Invoke-WhenFileChanged Remove-ItemSafe Remove-NativeProgressNoise Restart-SelfElevated Set-PSScriptID

PSEditions

Desktop Core

Dependencies

This module has no dependencies.

Release Notes

Execution v5.3.2+sha.18d2a46

## [v5.3.2] - 2026-05-11

### Fixed

- `Invoke-NativeCommand` (default mode): pipe-to-cmdlet usages like
 `Invoke-NativeCommand vswhere.exe -format json | ConvertFrom-Json`
 no longer fail with "The input object cannot be bound to any
 parameters for the command". The function used to emit the captured
 stdout as a single `[string[]]` object (`return ,$snapshot.Output`),
 which the comma operator wrapped in an outer array so PowerShell's
 pipeline-unrolling only stripped the wrap and left the
 inner array as one pipeline element. Cmdlets whose pipeline-input
 parameter is typed `[string]` (`ConvertFrom-Json`,
 `Select-String -InputObject`, ...) rejected the bind because a
 `string[]` cannot satisfy a `[string]` `ValueFromPipeline` slot.
 The wrap is now dropped; the captured lines stream one
 `[string]` per pipeline element, restoring the same shape the bare
 `&` operator produces. Assignment callers
 (`$out = Invoke-NativeCommand ...`) see the standard PowerShell
 scalar-or-array shape (scalar for a single line, `string[]` for
 multiple); no caller in this repo relied on the always-array form.
 `-PassThru` `.Output` is unaffected (still returned whole).
- `build.ps1`: pin `ModuleBuilder` below `3.2.0`. ModuleBuilder
 3.2.0 (published 2026-05-11) ships PowerShell 7-only syntax
 (`?:` ternary, pipe-leading whitespace) inside its own `.psm1`
 and therefore fails to import on Windows PowerShell 5.1
 outright. On PowerShell 7 it additionally fails the build with
 `Get-Metadata: Can't find 'AliasesToExport'` because it now
 expects that key to be present in the source manifest, where
 ours keeps it commented out. Both CI legs go red on every push
 until this is pinned. `Install-Module ModuleBuilder` now
 passes `-MaximumVersion 3.1.9`, and the matching
 `Import-Module` likewise restricts to `< 3.2.0` so an already
 installed 3.2.0 on a developer machine does not get picked up
 ahead of the older version. To revisit when ModuleBuilder
 releases a fix.