Over the past week, some of our users have encountered a known bug in the visual Studio 2008 debug working directory. This issue occurs due to many factors. We will discuss this below.
By default, when a person does this, the executable is extracted, and the working directory is any directory containing the Visual C++ program ( .vcxproj ). This is, of course, the directory that will serve as the current directory for your entire executable when run with Visual Studio.
I have a C++ VS2008 solution for several projects. This solution contains the computer data files required for execution, the type of which is loaded according to the purpose of the solution index (for example,
"Testing/data/" + "dataN.bin"). p >
For this solution to work, I need to set the working directory in someone’s projects to be in the solution’s directory (for example,
Configuration Properties >> Debug >> Working directory is $ ). (SolutionDir) ). This doesn’t work well when I’m debugging on my organization’s PC. However, if a user downloads my solution multiple times, this property may not be set correctly in their projects.
I have mapped this setting so that it is not in the report project (
PROJECT.vcproj) but in the currently created user file (
PROJECT it.vcproj.DOMAIN. USER. user< /code>).
I love the way to keep this for ALL users without having to manually configure the product over and over again.
I haven't found a way to do both.
Visual Studio 2008 디버그 작업 디렉터리
Visual Studio 2008 Debug Arbeitsverzeichnis
Directory Di Lavoro Di Debug Di Visual Studio 2008
Directorio De Trabajo De Depuracion De Visual Studio 2008
Repertoire De Travail De Debogage De Visual Studio 2008
Visual Studio 2008 Katalog Roboczy Debugowania
Diretorio De Trabalho De Depuracao Do Visual Studio 2008
Rabochij Katalog Otladki Visual Studio 2008
Visual Studio 2008 Felsoka Arbetskatalogen
Visual Studio 2008 Debug Werkmap