FIX: Non-SourceSafe Visual Test Files Show Up as Checked Out

 Last reviewed: August 25, 1997
Article ID: Q142463
The information in this article applies to:
  • Microsoft Visual SourceSafe for Windows, versions 4.0, 5.0
  • Microsoft Visual Test for Windows, versions 4.0, 5.0

SYMPTOMS

At the close of a project, the Check In dialog box shows that files that aren't under Source Code Control (SCC) but are in a Visual Test (VT) project workspace are checked out.

STATUS

Microsoft has confirmed this to be a problem in the Visual SourceSafe Integration portion of Visual Test version 4.00 for Windows.

This problem has been fixed in Visual SourceSafe 5.0.

MORE INFORMATION

Steps to Reproduce Problem

  1. Set up a Project Workspace 1 containing two folders Dir1 and Dir2.

  2. In Dir1, place the files under SCC, and check them out.

  3. In Dir2, ensure that the files are not under SCC.

  4. On the Tools menu, click Options, click the Source Control tab, select the "Check in files when closing the workspace" option, and click OK.

  5. On the File menu, click New, click Project Workspace, and click OK.

  6. Click Yes to "Some files in the workspace are not checked in. Do you want to check them in now?"

At this point, the expected behavior is that the files in Dir2 would not be listed in "Check in files" window. But in fact, the Dir2 files are listed (but they not checked or selected). 
Keywords          : SourceSafe SSVT vbwin kbinterop fixlist5.00 kbbuglist kbfixlist
Version           : 4.0 5.0
Platform          : NT WINDOWS
Issue type        : kbbug
Solution Type     : kbfix

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

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: August 25, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.