BUG: "Failed to Reload Project" Error When Checking In VB FileLast reviewed: December 2, 1997Article ID: Q177409 |
The information in this article applies to:
SYMPTOMSChecking in or undoing a check out of an existing Visual Basic project file (.vbp) in Visual SourceSafe causes the following error message:
Failed to Reload the Project. Please close the project from the file menu and re-open it to get the correct versions of all the files loaded into memory.Then, the source code status box opens and Visual Basic hangs. Similar problems might occur if you perform the same operations on other files within the project (for example, forms, modules, etc.).
CAUSE"Remove Local copy after Add or Check In" is selected.
RESOLUTIONDeselect the "Remove Local copy after Add or Check In" option. This can only be done through the Visual SourceSafe Explorer because the option is unavailable (grayed out) from the Visual Basic IDE Options dialog box. Furthermore, because the Visual Basic IDE inherits this option from Visual SourceSafe, changing there changes it in Visual Basic. In Visual SourceSafe:
STATUSMicrosoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONAfter checking in the .vbp, Visual Basic tries to reload the project, but because "Remove Local copy after Add or Check In" removes the local copy, the reload fails. Having this option selected can also cause a General Protection Fault to occur in Visual Basic when you add a new project to Visual SourceSafe from Visual Basic.
Steps to Reproduce Behavior
For more information related to this symptom, please see the following articles in the Microsoft Knowledge Base:
ARTICLE-ID: Q171803 TITLE : FIX: Problems Retrieving VB 5.0 Projects from Visual SourceSafe ARTICLE-ID: Q176351 TITLE : BUG: Referenced Project Causes "Failed to Reload the Project" |
Additional query words: remove
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |