http://blogs.technet.com/b/heyscriptingguy/archive/2012/10/05/build-your-own-powershell-cmdlet-part-7-of-9.aspxMicrosoft Windows PowerShell MVP, Sean Kearney, continues a series of guest blogs detailing building your own cmdlet.en-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/heyscriptingguy/archive/2012/10/05/build-your-own-powershell-cmdlet-part-7-of-9.aspx#3526243Tue, 16 Oct 2012 07:04:56 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3526243rjcox<p>&gt; simply alter each passed parameter in the Process block with a [0] to reflect this.</p> <p>This means if the parameters are specified on the command line (not using the pipeline) the second etc. elements of those arrays will be ignored silently. Not good.</p> <p>The mistake is making the three parameters &nbsp;($Folder, $Preface, and $Extension) arrays in the first place. For pipeline input they don&#39;t need to be (compare Where-Object&#39;s -InputValue: the parameter that receives Where-Object&#39;s pipeline input is /not/ an array). As they all need to match up (what would happen if there were two prefaces but three folders and four extensions?) easier to avoid the arrays.</p> <p>(If using without the pipeline then the caller would need to do the looping over multiple sets of values, but that isn&#39;t much of a loss.)</p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3526243" width="1" height="1">