Posted By: tgraupmann | Mar 31st @ 10:49 AM
page 1 of 1
Comments: 5 | Views: 984
tgraupmann
tgraupmann
tgraupmann
In a VS C# 2008 project, I've found a problem with piping console output to a file.

For example, in the project settings, debug tab, start options, and command line arguments:

If I try to pipe to a file like this:

ExamineSTPErrorLogs > report.txt

which is something that worked in VS 2005, the "> report.txt" is showing as a parameter to the console application.

But the expected behavior is that this should be piped to a file.

If I would have used:

ExamineSTPErrorLogs ">" report.txt


I would expect ">" and "report" to be used as command line parameters.

Is there some kind of hack so this can be made to work correctly?

Otherwise I'll have to downgrade. Upmh!
evildictaitor
evildictaitor
How could you use the adjective "indescribable" truthfully?
Is there a good reason why you can't use the output window? If your program is writing to Console.Out rather than a parameterised stream you should consider some code changes to rectify it.
RichardRudek
RichardRudek
So what do you expect for nothin'... :P
have you tried escaping the '>' (stream redirection) character ?

eg  ^>   or   %> 
RichardRudek
RichardRudek
So what do you expect for nothin'... :P
You might need to use a batch file then.

PS: I don't have VS2008, so I can't experiment...
page 1 of 1
Comments: 5 | Views: 984