VS150COMNTOOLS variable for Visual Studio 2017

zosrothko's Avatar


16 Mar, 2017 01:55 PM

It seems that the environment does not contain the VS150COMNTOOLS variable pointing at the VS2017 tools

VS100COMNTOOLS=c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools\
VS110COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\
VS120COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools\
VS140COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\
VS90COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\Tools\

Did I miss something?

  1. 1 Posted by zosrothko on 17 Mar, 2017 09:39 AM

    zosrothko's Avatar

    Can you add this setup to the worker environement

    set VS150COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\
  2. Support Staff 2 Posted by Feodor Fitsner on 17 Mar, 2017 06:17 PM

    Feodor Fitsner's Avatar

    It looks like starting from VS 2017 this variable is not set by default any more and looks like a preferable way going forward is running VS 2017 Command Line script during the build, like this:

    - "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\VsDevCmd.bat"

    After running this batch I've got VS150COMNTOOLS environment variable set as expected: https://ci.appveyor.com/project/FeodorFitsner/simple-console/build/...

    Hope that helps.

  3. 3 Posted by zosrothko on 22 Mar, 2017 01:25 PM

    zosrothko's Avatar

    Can you give back the DOS 8.3 path of

    C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\Tools\VsDevCmd.bat
    on a Visual Studio 2017 image


  4. zosrothko closed this discussion on 17 May, 2018 09:06 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac