The information in this article applies to:
SYMPTOMSWhen you Get a source-controlled Visual Basic project from Visual SourceSafe Explorer, the Mssccprj.scc file does not contain SCC_Aux_Path information. STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. This problem has been corrected in Visual SourceSafe 6.0. MORE INFORMATIONIf you add a Visual Basic project to Visual Sourcesafe, Visual SourceSafe creates a Mssccprj.scc file in the project folder. The .scc file will have the following information:
SCC_Project_Name is the path to the Visual SourceSafe project the Visual
Basic project is associated with and TJAAAAAA is its physical file name.SCC_Aux_Path is the path to the Visual SourceSafe database the Visual Basic project associated with. However, if you perform a Get Latest Version on the Visual Basic project from the Visual SourceSafe Explorer, SCC_Aux_Path information is not written in the Mssccprj.scc file. Steps to Reproduce Behavior
REFERENCESFor additional information, please see the following article in the Microsoft Knowledge Base: Q147585 INFO: The Mssccprj.scc File and How Is It Used Additional query words:
Keywords : kbinterop kbSSafe500bug kbSSafe600fix kbVBp |
Last Reviewed: August 17, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |