FIX: File Added with No Extension is Handled Incorrectly

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q129193

SYMPTOMS

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

Back to the top

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. Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Back to the top

MORE INFORMATION

Steps to Reproduce Problem

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

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

Issue an SS DIR command. You will see the file listed.
Issue an SS GET makefile command. The error, "makefile is not an existing name or project" will occur.
Issue an SS GET makefile.* command. This will get the file.
From the command line, add the file with no period:
SS ADD makefile
You will see the file listed twice when you use the SS DIR command.

You can remove the makefile that has no period, but you cannot now remove the one with a period (makefile.).

Back to the top

APPLIES TO

Microsoft SourceSafe

Back to the top

kbbug kbfix kbfix kbssafe400fix kbusage KB129193

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top