Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / General / June 2005

Tip: Looking for answers? Try searching our database.

How can I monitor the output of a compile?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Peter Steele - 19 Jun 2005 20:48 GMT
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.
However, nothing appears in this log file until the build is completely
done. I tried instead to use

devenv mysolution.sln /build Debug /out output.log

but when I try to look at output.log in this case I get an error because it
appears devenv puts an exclusive lock on this file.

I there another way I can accomplish this?
Phill.  W - 23 Jun 2005 11:58 GMT
> 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.
Marsh J. Ray - 26 Jun 2005 01:18 GMT
> 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


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.