FIX: File Added with No Extension is Handled Incorrectly

 Last reviewed: August 25, 1997
Article ID: Q129193
The information in this article applies to:
  • SourceSafe for MS-DOS, versions 3.04, 3.1
  • SourceSafe for Windows, versions 3.04, 3.1

SYMPTOM

A file added to SourceSafe with no extension and a period (.) character is handled incorrectly.

STATUS

Microsoft has confirmed this to be a bug in Microsoft SourceSafe versions 3.04 and 3.1. This problem has been corrected in Microsoft Visual SourceSafe version 4.0.

MORE INFORMATION

Steps to Reproduce Problem

  1. From the command line, add a file to SourceSafe with no extension: 

          SS ADD makefile.     << make sure you add the period.

  2. Issue an SS DIR command. You will see the file listed.

  3. Issue an SS GET makefile command. The error, "makefile is not an existing name or project" will occur.

  4. Issue an SS GET makefile.* command. This will get the file.

  5. From the command line, add the file with no period: 

          SS ADD makefile

  6. You will see the file listed twice when you use the SS DIR command.

  7. You can remove the makefile that has no period, but you cannot now remove the one with a period (makefile.). 
Keywords          : SourceSafe SRCSAFE SS ss3 vbwin kbusage kbbuglist
Version           : 3.04 3.10 | 3.04 3.10
Platform          : MS-DOS 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.