Home Dashboard Directory Help
Search

Import-Csv LiteralPath ValueFromPipelineByPropertyName by PetSerAl


Status: 

Active


4
0
Sign in
to vote
Type: Bug
ID: 771015
Opened: 11/14/2012 1:25:27 AM
Access Restriction: Public
0
Workaround(s)
view
3
User(s) can reproduce this bug

Description

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.

[PSCustomObject]@{LiteralPath='Test.csv'}|Import-Csv
Details
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
Sign in to post a workaround.