It’s kinda true, but not really at all. What do I mean with that? First, let’s get your documentation question out of the way. The following is from paragraph §3.13 of the PowerShell version 3.0 Language Specification: If a command writes a single object, its successor receives that object and then terminates after writing its … Read more
The syntax is way off. A few issues: I’m not sure what $($.19981016) was intended to produce, but $( ) evaluates the expression in the parentheses and interpolates the result into the string, and you’re getting the error because $.19981016is not a valid expression. The error would be repeated for each .jpg file in the … Read more
OK, I’m not going to code the whole thing for you (what’s the fun in that?) but I’ll get you started. First, there are two ways to do the content comparison. The lazy/mostly right way, which is comparing the length of the files; and the accurate but more involved way, which is comparing a hash … Read more
.Length and .Count are aliases of one another and are so-called intrinsic members (properties) that PowerShell adds to most objects, in the interest of unified treatment of scalars and collections (see this answer for background). The exception are objects of types that PowerShell treats as collections, i.e. objects that it automatically enumerates in the pipeline, … Read more
To complement zett42’s helpful answer: If you’re running PowerShell (Core) 7+, you can pass the file path that represents the terminal (console) to the (positionally implied) -FilePath parameter (in Windows PowerShell, this causes an error, unfortunately – see bottom section): # PowerShell 7+ only # Windows Get-Content data.txt | Tee-Object \\.\CON | data_processor.exe # Unix-like … Read more
tl;dr: When PowerShell pipes a string to an external program: It encodes it using the character encoding stored in the $OutputEncoding preference variable It invariably appends a trailing (platform-appropriate) newline. Therefore, the key is to avoid PowerShell’s pipeline in favor of the native shell’s, so as to prevent implicit addition of a trailing newline: If … Read more
Here is a solution from Using-Object: PowerShell version of C#’s “using” statement which works by calling .Dispose() in a finally block: function Using-Object { [CmdletBinding()] param ( [Parameter(Mandatory = $true)] [AllowEmptyString()] [AllowEmptyCollection()] [AllowNull()] [Object] $InputObject, [Parameter(Mandatory = $true)] [scriptblock] $ScriptBlock ) try { . $ScriptBlock } finally { if ($null -ne $InputObject -and $InputObject -is … Read more
A few months ago, I submitted a proposal for including a Join-Object cmdlet to the standard PowerShell equipment #14994. Besides complexer joins based on a related property, the idea is to also be able to do a side-by-side join (by omiting the -On parameter). Taken this Paste command in Linux as an example: $State=”Arunachal Pradesh”, … Read more
Note: On 15 Nov 2021 a bug was fixed in the code below in order to make it work properly with advanced scripts – see this answer for details. The closest you can get to a robust, cross-platform self-elevating script solution that supports: both positional (unnamed) and named arguments while preserving type fidelity within the … Read more
If an object you export as CSV with Export-Csv or ConvertTo-Csv has property values that contain a collection (array) of values, these values are stringified via their .ToString() method, which results in an unhelpful representation, as in the case of your array-valued .IPV4Addresses property. To demonstrate this with the ConvertTo-Csv cmdlet (which works analogously to … Read more