PRB: Unable to Add Project Error in Visual Basic IntegrationLast reviewed: June 2, 1997Article ID: Q155390 |
The information in this article applies to:
SYMPTOMSWhen you add a new project to Visual SourceSafe using the Visual Basic 4.0 integration, you may receive the error message:
"Unable to add the project to source code control"When you add an existing project, the error will read:
"Add failed - Files were not added to source code control" WORKAROUNDClear the "Remove local copy after Add or Check In" checkbox as described below when adding projects to Visual SourceSafe.
STATUSMicrosoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONThe above error will occur when the "Remove local copy after Add or Check In" checkbox is checked in the Advanced settings dialog box for Visual Basic/Visual SourceSafe integration. With Visual SourceSafe versions 4.x, this checkbox may be found by clicking Visual SourceSafe on the Add Ins menu and clicking the Options sub-menu. Next, click Advanced Command to bring up the Advanced dialog box and click the Local Files tab. In version 5.0, this checkbox is disabled. The setting is inherited from the current Visual SourceSafe setting that is located on the Local Files tab on the Tools menu under Options in the Visual SourceSafe Explorer. In both cases, although the working directory may be incorrect, the project is actually added to Visual SourceSafe. The underlying problem is that Visual SourceSafe has deleted the files from the hard drive but Visual Basic is still trying to use them. The error messages are misleading.
Steps To Reproduce BehaviorAssuming that "Remove local copy after Add or Check In" is checked:
"Unable to add the project to source code control"However, when you run Visual SourceSafe, you will see that the project has been created.
|
Additional reference words: buglist
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |