The information in this article applies to:
SYMPTOMSSubprojects are not inheriting the working folder setting from the parent project as expected. CAUSEYou have overridden the normal behavior by explicitly setting the working folder for subproject(s). This results in a Dir= variable being set under the subproject section header in your Ss.ini file. RESOLUTION
To restore the working folder inheritance, you need to edit the user's
..Vss\Users\<username>\Ss.ini file and completely remove the Dir variable
under the appropriate subproject section header.
Default working folder propagation works again only after the "Dir(PC)" lines under each subproject section header are completely removed and the Ss.ini file saved. STATUSThis behavior is by design. MORE INFORMATION
When setting the working folder of a top-level Visual SourceSafe (VSS)
project, by default all subprojects assume a working folder based on a
mirror of the project's directory structure on disk.
Setting the working folder for $/Project1 to C:\Project1 implicitly sets the working folder of the subprojects to C:\Project1\Sub1, C:\Project1\Sub1\SubofSub1 and C:\Project1\Sub1\Sub2, respectively. If you explicitly set the working folder of a subproject, you are essentially telling VSS, "Don't assume a working folder for this subproject", which in some cases may be desired. VSS accomplishes this by adding the Dir variable under the subproject's header section in the Ss.ini file. Steps to Reproduce Problem
REFERENCESVisual SourceSafe Help, search on: "Working Folder", Topic: "Setting the Working Folder for SS.INI" Additional query words: propagate
Keywords : kbSSafe400bug kbSSafe500bug kbSSafe600bug |
Last Reviewed: October 21, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |