Vsvars32.bat in Visual Studio 2017

Question

Since the Visual Studio installer is new to Visual Studio 2017, I cannot find the Visual C ++ component explained here .

How do I go to vsvars32.bat in VS2017?

Answer 1

VS2017 suffers from very serious damage to the installation location of the installation path. Most of the damn stupid things they did was make the title of the publication (Professional, Enterprise, possibly Community) part of the way. This makes it difficult to reliably search tools from one machine to another.

There is one environment variable that, I think, can solve the problem, the VSAPPIDDIR variable stores the path to the folder where the IDE is installed (devenv.exe). Therefore, if you want to run vcvars32.bat from the build event, you should use

  call "%vsappiddir%..\..\VC\Auxiliary\Build\vcvars32.bat" x86 

Note that vc, not vs, vsvars32.bat no longer exists. You could support the "Developer Command Line:

  call "%vsappiddir%..\tools\vsdevcmd.bat" 

But judging by your link, you really want to run the editbin.exe utility:

  "%vsappiddir%..\..\VC\Tools\MSVC\14.10.25017\bin\HostX86\x86\editbin.exe" args... 

Version number 14.10.25017 is also not a joy, there is no real understanding of how this will change from one update to another. It will probably be.

Answer 2

Just change "vsvars32.bat" to "vsdevcmd.bat". This is compatible, at least with VS2015.

 call "$(DevEnvDir)..\tools\vsdevcmd.bat" editbin /largeaddressaware "$(TargetPath)" 

Answer 3

None of the solutions mentioned worked for me. After my head warmed up with the error "vsvars32.bat missing", I went through each line and there was too much "svcutil.exe".

I thought about it and it worked. I got the following path on my machine for SvcUtil.exe:

C: \ Program Files (x86) \ Microsoft SDK \ Windows \ v7.0A \ Bin

I set the path in the System Environment Variable and restarted my Visual Studio just in case, and it worked.

Hope this helps someone!

Edit: Very Strange - works when I have "lightweight solution loading" enabled. As soon as I turn off the “Easy Download Solution” - it starts giving me the same error!