Import-Csv LiteralPath ValueFromPipelineByPropertyName - by PetSerAl

Status : 


Sign in
to vote
ID 771015 Comments
Status Active Workarounds
Type Bug Repros 4
Opened 11/14/2012 1:25:27 AM
Access Restriction Public


Although LiteralPath marked as ValueFromPipelineByPropertyName, actualy it is not possible to send something to it from pipeline, becouse Path parameter exists in same parameter sets and marked as ValueFromPipeline, so it always get value from pipeline, and setting both parameters is error.

Sign in to post a comment.
Posted by Kirk Munro on 9/4/2013 at 7:53 AM
This is a really annoying bug, and a regression in PowerShell 3.0. In PowerShell 2.0, this works just fine:

gci *.csv | ipcsv