This works, though it's a bit ugly: dir >_ && type _ && type _ >a.txt It's a little more flexible than some of the other solutions, in that it works statement-by-statement so you can use it to append as well. I use this quite a bit in batch files to log and display messages: ECHO Print line to screen and log to file. >_ && type _ && type _ >>logfile.txt Yes, you could just repeat the ECHO statement (once for the screen and the second time redirecting to the logfile), but that looks just as bad and is a bit of a maintenance issue. At least this way you don't have to make changes to messages in two places. Note that _ is just a short filename, so you'll need to make sure to delete it at the end of your batch file (if you're using a batch file). +1 This is how I've always done it. I believe this is the correct answer to the original question and should be marked as so.

I'm new to c. Is there any simple way to redirect all the console's output (printfs etc.) to a file using some general command line linkage parameter (without. How to output to the console in C++/Windows. Ask Question. Still you can redirect the output of your project to a file by using the console switch (>>). Serial Ebp Devis Et Facturation 2010.

The trick, as @MTS hints at, is that you actually write to two files: one that gets created per each command/line (hence a single '>' that overwrites each time), and then you type that line to the screen (type ), and finally, you type it again and redirect its output, all the long APPENDING, to your log file with '>>'. This is how I've done it for years, though I love the simple ' temp file. I've always done 'tmp.txt' or soemthing. Globul Connection Manager here. Yeah, delete it afterwards. – Jul 19 '13 at 8:07 •.

I’d like to expand a bit on Saxon Druce’s. As stated, you can redirect the output of an executable in the current directory like so: powershell '. Something.exe tee test.txt' However, this only logs stdout to test.txt. It doesn’t also log stderr.

The obvious solution would be to use something like this: powershell '. Something.exe 2>&1 tee test.txt' However, this won’t work for all something.exes. Some something.exes will interpret the 2>&1 as an argument and fail. The correct solution is to instead only have apostrophes around the something.exe and it’s switches and arguments, like so: powershell '. Something.exe --switch1 --switch2 arg1 arg2 ' 2>&1 tee test.txt.