VS working directory, output directory

By default, the "Output directory" and "Output file" two properties corresponding to the directory is the same, it is convenient (of course, the output file value in the output directory based on the value of the EXE file name is also included). If two are different, the intermediate generated linker is in the output directory, such as Xx.ilk and xx.pdb files, and the resulting Xx.exe file is in the directory where the output file property is set.
The set of working directories in VS is for debugging, that is, after you start debugging, start a new process, automatically set the working directory of the new process to the working directory in the VS project properties, and then start the corresponding EXE program. However, if you do not use vs Debug startup EXE, but directly double-click the exe file to start a new process, the working directory of the new process will be automatically set to the directory where the EXE file, which is different from the VS startup debugging. So if you do not copy the contents of the working directory in the directory of the EXE, you will run an error, because the working directory is no longer set in VS, but the directory where the exe file resides. Finally, to say that, the default VC + + project's working Directory Project value is empty, representing the default is the directory of the VS project is the directory where the. vcproj file is located

Click to open link