This article was previously published under Q318298
This article has been archived. It is offered "as is" and will no longer be updated.
When the user creates a project, the user cannot add the project to source control and receives an error message that similar to the following:
"File F:\TEMP\a34\WindowsApplication1\~sakae4c77a101c14609.vbproj could not be mapped to the SourceSafe project $/. Copy the file to F:\TEMP\a34?"
NOTE: The file names differ in this error message according to the file names.
To resolve this problem, upgrade to the Visual SourceSafe version 6.0c. If you are an MSDN Universal subscriber, you can download this from the Subscriber Downloads section of the following MSDN Web site:
Create a Microsoft Visual C++ Active Template Library (ATL) project.
Right-click the solution, and then click Add Solution to Source Control to add the project to source control.
Add a Microsoft Visual Basic project in the subdirectory of the solution. When you are prompted, check out the solution. Notice that you receive the following warning message:
The Project that you are attempting to add to source control may cause other source control users to have difficulty opening this solution or getting newer versions of it. To avoid this problem, add the project from a location below the binding root (<path to the local solution>)of the other source controlled projects in the solution.
Additionally, this warning message includes an option not to show this dialog box again.
After this warning, you receive the error message that is listed in the "Symptoms" section.