> I have an automated build that does something like this
> devenv mysolution.sln /build Debug >output.log 2>&1
>
> I want to be able to monitor output.log to observe the build
> in progress.
To what end?
I can't think of many /useful/ things that you could do as part of a
such an exercise. A build is a build; a unit of work that either
works or doesn't, so you might as well wait for it to finish.
Regards,
Phill W.
> I have an automated build that does something like this
>
[quoted text clipped - 3 lines]
> However, nothing appears in this log file until the build is completely
> done.
There is likely buffering of the stdout of devenv.exe, I don't think
there's much you can do about that. Also, the cmd.exe redirections don't
always seem to share nicely with other processes.
I've had better luck using cygwin's "tail", where output.log has already
been created and the tail is started first.
You might try truncating output.log, starting "tail -f output.log", and
then starting devenv with redirecting with append redirection
>>output.log 2>&1
You could also call CreateProcess and have devenv inherit pipe handles
that you read from (not simple).
Good luck,

Signature
Marsh J. Ray
Senior Software Developer
ScriptPro
m|r|a|y|@|s|c|r|i|p|t|p|r|o|.|c|o|m