Question

I was wondering why Visual Studio won't do what it's been told as I recognized, that Visual Studio just uses the standard Windows Command Prompt and not its own VS Cmd Prompt.

This results in an

'csc' is not recognized as an internal or external command

error message in the build output window.

So.. is there a way to tell VS to use its own command line tool where csc is usable or do I really have to set additional system variables to get this run?

Was it helpful?

Solution

The easiest way is probably just call out to the thing the normal VSXXXX command prompt uses:

Ex:

CALL ""%ProgramFiles(x86)%\Microsoft Visual Studio 10.0\VC\vcvarsall.bat"" x86

(edit: updated as per Hans's comment)

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top