Geek Answers Handbook

Why is compiling VCC.sln running in the background without stdout?

I am trying to compile a project from the command line, for example:

devenv.exe myproj.sln /build release

It looks like the code compiles well, but not all I need:

I want to be able to capture output (e.g. warnings, errors) from the compiler as they arise. Unfortunately, as soon as I issue the above command, I return to the command line.

When I look at process-explorer or taskmgr.exe, I see that the devenv.exe process (and several other subprocesses) are working. If I look in the output folder, I see that all my files gradually appear.

Is there a way to get VCC to work a bit more like GCC - when I issue a build command or make a project using the Makefile, I get a message flow and console blocks until the process completes.

Update: Thank you, two great solutions. I can confirm that it works.

+3
source share
2 answers

devenv uses this interesting dispatcher that switches between command line mode and windowed mode. Actually, devenv.com is in addition to devenv.exe, and since * .com takes precedence over * .exe, it starts up first. devenv.com analyzes the command line and decides what to invoke.

In other words, change your command line to:

devenv myproj.sln /build release

And you should be fine.

+9
source

use devenv.com instead of devenv.exe and you will get what you want.

You can also use MSBuild.exe for additional parameters.

+9

More articles:


All Articles