Michael Klement comments

Results 1234 comments of


                                            Michael Klement

Potential gotcha with chaining Boolean pipes with 0 as input value

Doesn't the problem lie with the passing-the-input-value-through-conceptually-Boolean-pipes-if-true behavior rather than with the `choose` pipe? I agree that changing the `choose` pipe is not the way to go. Short of creating...

Potential gotcha with chaining Boolean pipes with 0 as input value

Good idea. Would be nice if the read-me mentioned: - the need to specify `strict` as an extra parameter when using `choose` after a Boolean pipe whose test succeeds with...

Select-Object: -ExpandProperty, unlike -Property, enforces the existence of the targeted property

@SteveL-MSFT, to me there is no more implied intent with respect to the existence of a targeted property with `-ExpandProperty` than with `-Property`. You can think of `$a | Select-Object...

Select-Object: -ExpandProperty, unlike -Property, enforces the existence of the targeted property

If the decision ends up in favor of keeping the existing behavior, the thing to document is: * With `-ExpandProperty`, if you want to _ignore_ those input objects that do...

Implement accommodations for Windows CLIs, notably batch files and misexec-style programs as part of experimental feature PSNativeCommandArgumentPassing

As it turns out, there's another accommodation worth making for _batch files_ with respect to _exit codes_ (now implemented in v1.3.1 of the `Native` module): * Direct invocation of batch...

Implement accommodations for Windows CLIs, notably batch files and misexec-style programs as part of experimental feature PSNativeCommandArgumentPassing

The following: * fleshes out the proposal above with **concrete examples** * contains a **list of bugs** as of PowerShell Core 7.2.0-preview.5 ### `PSNativeCommandArgumentPassing`: Missing-accommodations examples, current bugs: Setup: ```powershell...

Implement accommodations for Windows CLIs, notably batch files and misexec-style programs as part of experimental feature PSNativeCommandArgumentPassing

@SteveL-MSFT, on a meta note similar to the one in https://github.com/PowerShell/PowerShell/issues/14025#issuecomment-743354227: [Two separate requests to discuss the issue at hand](https://github.com/PowerShell/PowerShell-RFC/issues/282) in the April community call were made (one by @iSazonov,...

Implement accommodations for Windows CLIs, notably batch files and misexec-style programs as part of experimental feature PSNativeCommandArgumentPassing

Thanks for engaging, @JamesWTruher. Before we get into specifics: > change the way things are parsed when running a batch file vs an executable seems very improper to me It's...

Implement accommodations for Windows CLIs, notably batch files and misexec-style programs as part of experimental feature PSNativeCommandArgumentPassing

Quick update, @JamesWTruher: `PSNativeCommandArgumentPassing` breaks invocation of VBScripts with arguments: see #15289

Implement accommodations for Windows CLIs, notably batch files and misexec-style programs as part of experimental feature PSNativeCommandArgumentPassing

As for VBScript (WSH): VBScript's command-line argument parsing is provided by the WSH ([Windows Script Host](https://en.wikipedia.org/wiki/Windows_Script_Host)) CLIs, `cscript.exe` (console) and `wscript.exe` (GUI), so with direct invocation of script files the...