BUG: Referenced Project Causes "Failed to Reload the Project"

Last reviewed: February 24, 1998
Article ID: Q176351
The information in this article applies to:
  • Microsoft Visual SourceSafe, 32-bit, for Windows, version 5.0
  • Microsoft Visual Basic Control Creation, Learning, Professional, and Enterprise Editions for Windows, version 5.0

SYMPTOMS

When you have more than one project in a Visual Basic group and one of the projects references another, performing a get on the referenced project in Visual SourceSafe will cause the following error to occur:

   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.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a new Standard Visual Basic project and add it to Visual SourceSafe.

  2. Add an ActiveX DLL or ActiveX .exe project to the group and add it to Visual SourceSafe.

  3. In Visual Basic, select the first project in the Visual Basic Project List.

  4. From the Visual Basic Project menu, click References and then add a reference to the second project in the group. Click OK.

  5. In Visual SourceSafe, go to the SourceSafe menu and click "Get Latest Version" to try to perform a get on the second project. The error occurs.
Keywords          : ssusage ssvb
Version           : WINDOWS:5.0; WINNT:97
Platform          : WINDOWS winnt
Issue type        : kbbug


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 24, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.