Somesh Chandra

Trying to explain the problem by an example:
1. I set working folder folder as C:\Sourcecode
2. Now, idea is to have a copy of the source code as backup in different folder. So I copy the code from C:\Sourcecode to C:\Sourcecode_BAK
3. Now I go to C:\Sourcecode_BAK and open the solution. Unbind the solution from VSS and try to edit some code.
4. Now open VSS, you will find that working folder changes from C:\Sourcecode to C:\Sourcecode_BAK. As this is not consistent, you might not be able to reproduce. so try 2-3 times.

I want to prevent this.
though there are manual ways. I mean once copy is done remove all vss related files from the root folder and subfolders. Remove readonly attribute on rootfolder. Remove vss related entry from .sln and .csproj files. Oh.......too much of work.

CAN WE AUTOMATE THIS

Thanks

Somesh




Re: Visual Studio Source Control and SourceSafe Working folder changes after moving the code to other location

Steve Culver - MSFT

Hi Somesh,

Correct me if I'm wrong, but It sounds like you want to branch your new code from existing sources Making an exact copy of a directory (including VSS files) would most likely cause the working folder to change, due to the VSS contents being identical. Take a look at this link: http://support.microsoft.com/kb/132921 and let me know if you have any other questions.

Thanks,

Steve





Re: Visual Studio Source Control and SourceSafe Working folder changes after moving the code to other location

Somesh Chandra

Hi Steve,

Thanks for your reply

I exactly want to create a copy of source code in some directory location, which should not have any relationship with VSS.

I performed the steps as provided on the link provided by you. It creates a new project in vss which has all the files shared. I didn't find the option "Separate after share" checkbox.

Thanks,

Somesh






Re: Visual Studio Source Control and SourceSafe Working folder changes after moving the code to other location

Steve Culver - MSFT

Hi Somesh,

Is the backup of your files just for archival purposes or is it related to your configuration management procedure   If you want to concurrently work on features with the same baseline of code, I think you should be using the branching and labeling feature of VSS.  I accidentally provided you with an older VSS link, here is a newer one on how to Maintain Multiple Versions of a Project.  I hope this points you in the right direction, but let me know if you have any issues.

Thanks,

Steve