views:

236

answers:

1

I'm using Visual Studio 2005 Express Edition with SP1.

I have a Pre-Link Event which needs to invoke one program and send its output to another.

foo | bar

This command works as expected when invoked from a command line or batch file. The command fails when invoked from the Pre-Link Event (even if the Pre-Link Event invokes a separate batch file containing the command). 'foo' runs and produces output which appears in Visual Studio, but this output is not fed to 'bar', and in fact it appears 'bar' is never invoked at all. Even when the Pre-Link Event invokes CMD or NMAKE which in turn invokes the piped commands, only 'foo' runs.

Is Visual Studio broken and/or is there some arcane ritual I can perform to make this work?

A: 

This was answered here for the > operator. I suspect the same thing may be happening with pipes.

Ferruccio
It appears that answer applies to VS2008 only. One poster says the '>' operator works fine in VS2005.
Integer Poet