The information in this article applies to:
SYMPTOMSSome Microsoft Visual InterDev files in a project that have been placed under source control may show increments to their version number when no changes have actually taken place. This occurs when recalculate links is run, or if the file is checked out and back in, although no changes are made to the file. The comment below is added in SourceSafe: Page changed because one of its dependencies changed. CAUSEThe cause is a bug in Visual SourceSafe version 5.0. Visual SourceSafe increments a file's version every time a file containing Visual SourceSafe keywords is checked in. This behavior occurs even though the SourceSafe option for "Check in Unchanged Files" is set to "Undo Check out". RESOLUTIONThere is currently no workaround from Visual InterDev that allows the use of keywords and prevents the version from being incremented. STATUSMicrosoft has confirmed this to be a bug in Microsoft Visual SourceSafe version 5.0. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATION
The Recalculate Links command causes the incrementing behavior to occur
because it checks out and checks in each file in the Web project. This can
dramatically increase the number of erroneous versions of a file.
Other keywords, such as $Author: $ increments only the version when the
information they reference is changed. Other keywords include:
Steps to Reproduce Behavior
REFERENCESFor additional information please see the following article in the Microsoft Knowledge Base: Q168247 BUG: Keywords Cause New Version When "Undo Check Out" Set Additional query words:
Keywords : kbSSafe kbVisID |
Last Reviewed: January 9, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |