Changing the path for a custom build step
I inherited a visual studio 2003 project that uses some custom build steps. I am having problems with the path to the tool. Where does visual studio get its PATH? I followed the% PATH% step in the custom build step and has no resemblance to the system path. I found the value in the registry
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ VisualStudio \ 7.1 \ VC \ VC_OBJECTS_PLATFORM_INFO \ Win32 \ Directories
Path Dirs, which looked like it was the path used by visual C, but removing it doesn't seem to change the path in VC. Any ideas?
source to share
Visual Studio has the annoying habit of "playing" with your path, which results in what you saw.
The easiest way to get around it if you want to change the environment inside VS (which will change it for all your projects) is to go to Tools> Options> Projects> VC ++ Directories and add the required directories for the appropriate setting - in your case it should be "Executable files".
Another method I use if I don't want to change the overall environment is to create a batch file that first calls vsvars32.bat for the appropriate compiler version, then manipulates the PATH variable and finally runs "devenv". I really prefer this approach, but it means your disk is littered with small batch files that you will only use to launch Visual Studio ...
source to share