Re: Don't see any output to stdout from commands

[Nicholas Duane]

Don't worry, you're not mocking me.  I'm the one that wants to move away 
from Visual Studio and use make files which execute cl and link as opposed 
to devenv.  It's the others in the group that have become comfortable with 
using the IDE so they don't want to move to makefiles.

And you may find this interesting, I just recently left Microsoft after 11 
years.  I was a dev lead in the Outlook group before moving to the east 
coast and working in the field (as a MCS (Microsoft Consulting Services) 
consultant).  Back in Redmond we never used Visual Studio (not sure which 
version we may have been at back in '94,'95,&'96.  Everything was built with 
makefiles which ran the compiler and linker.  And a lot of people are 
surprised to find out that we didn't use some of the tools that we marketed 
to others.  For instance, for source control we used slm (pronounced slime). 
 Not sure where that came from.  I believe they are using SourceDepot now 
which I hear is a port of Perforce.

Thanks,
Nick

> From: Krzysztof Nosek <address@hidden>
> To: address@hidden, address@hidden
> CC: address@hidden
> Subject: Re: Don't see any output to stdout from commands
> Date: Fri, 08 Sep 2006 10:34:46 +0200
>
> > Why does one need to use devenv, anyway?  Why not invoke cl.exe
> > directly?
>
> Eli,
>
> of course calling cl.exe, link.exe and all the stuff directly _is_ an 
> option.
> But, sometimes, when you use such tool as Visual Studio, you want to have
> projects (.vcproj) and solution files (.sln) configured so that you can
> build-on-request during development from inside the VS's IDE (or your boss
> wants, or your fellow developer does, ...).
>
> So, these VS files contain (mostly) all information concerning build issues 
> of
> given solution. But it's only devenv who knows how to deal with it. Writing
> the build process from the scratch means repeating everything once more and
> equals redundancy for request. Or it means to resign from VS IDE and its
> tools, which  globally _might_ be in favour of the whole process, but would 
> be
> tough decision in any larger team or company.
>
> BTW, Previous versions of VS used to have feature of generating makefile
> (nmakish one) given solution file. But that feature disappeared many years 
> ago...
>
> Nick, I didn't mean mock at anybody using VS; my makefiles got to invoke
> devenv many times every single day (gathering output via named pipes and so
> on...) and I see all misery of it far too well. Perhaps somebody who reads
> this list knows better way of batch building projects, given Microsoft 
> Visual
> Studio solution/project files; please drop us a line.
>
> Regards,
> Chriss

_________________________________________________________________
Windows Live Spaces is here! It’s easy to create your own personal Web site. 
 http://spaces.live.com/signup.aspx