Vista - getting arguments from pipe

Why my program is not getting arguments from the pipe?

When I invoke it like this:
ls | ./myprog.exe

The arguments passed to my program are empty.

luntain wrote:myprog.exe is not a PowerShell cmdlet or script, therefore it would not
understand .NET objects that are being passed to it via the pipeline.

Marco

--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp

PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com

Marco,

I'm not sure this is the case. This works fine on cmd.exe but returns error
in PowerShell:

PS > ipconfig /all | find /i "ip"
FIND: Parameter format not correct

I tried to "strip" the objects from get-childitem to force strings on the
pipe, it doesn't wotk either

PS > get-childitem | foreach {$_.name} | find /i "ps1"
FIND: Parameter format not correct

PS > get-childitem | out-string | find /i ".ps1"
FIND: Parameter format not correct



-----
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com

Shay Levi wrote:This will work:
ipconfig /all | find /i `"ip`"

OK, perhaps we need to understand what myprog.exe actually does and
whether it works from DOS when doing something like a regular 'dir'.

Marco

Thanks, figured out that I needed to preserve the quote for find.exe, this
will work too:

ipconfig /all | find /i """ip"""



-----
Shay Levi
$cript Fanatic
http://scriptolog.blogspot.com

"luntain" <kamil.dworakowski@xxxxxx> wrote in message
news:84bd09e6-f3ae-45f6-957c-ed0654f448c4@xxxxxxI think you mean stdin since you haven't specified any arguments to
myprog.exe. Does your myprog.exe read from stdin?

--
Keith

"Marco Shaw [MVP]"
Perhaps Microsoft's data parser,
Log Parser 2.2, "understand .NET
objects that are being passed to it
via the pipeline".

Either e-book or paperback book.
Syngress Publishing - Microsoft Log Parser Toolkit
http://www.syngress.com/catalog/?pid=3110

The below is one long line on
the PowerShell command line.

PS> ls | LogParser.exe "SELECT Field6
AS FileName FROM STDIN
WHERE Field6 LIKE '%.ps1' " -i:tsv
-headerRowff -nSkipLines:8 -nFields:6
-iSeparator:"spaces" -statsff
FileName
----------------
aTestScript1.ps1
PS>

Mmm it seems Log Parser "understands"!
DOS?????

Logparser Forums
http://forums.iis.net/default.aspx?GroupID=51

Skip through the forums and write one's
data parsing once into a Log Parser text
query file (that uses params), that can be
called by almost any Windows language!

Just another "command line shell" way!