The information in this article applies to:
SYMPTOMSWhen you add a project to Visual SourceSafe in the Visual C++ integrated development environment a dialog box appears that prompts you to specify a working directory. CAUSEThe Visual C++ project contains a file that is not in the Visual C++ project directory (the directory containing the .dsp file) or a subdirectory underneath it. RESOLUTION
To work around this problem, do one of the following:
STATUSThis behavior is by design. MORE INFORMATIONBy default, the Specify Working Directory dialog box suggests the Visual C++ project directory. After you click OK and choose to add all files in the Visual C++ project to Visual SourceSafe, another dialog box appears with the following message: You only have the option of copying the file to the Visual C++ project directory, which may not be the desired location if the Visual C++ project has a subdirectory structure with different subdirectories for source files, header files, and so forth. In this case, you need to copy or move the files into the appropriate directories using Windows Explorer and then add them to the Visual C++ project. The relative path in Visual C++ is listed in the "Persist as" field on the General tab of the Source File Properties dialog box. This is the path that Visual SourceSafe attempts to resolve relative to the .dsp file in its database. Steps to Reproduce Behavior
REFERENCESFor additional information, please see the following article in the Microsoft Knowledge Base: Q164684 PRB: VFP/VSS File Could Not Be Mapped to SourceSafe Project Additional query words:
Keywords : kbinterop kbSSafe600 kbVC600 |
Last Reviewed: August 18, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |