I'm not sure there is a good way, but one way would be to use SVN Server Hooks to perform similar actions in Source Safe using the VSS command-line tools. I think this has been discussed before on the svn-user's mailing list. You could try searching the archives here.
1 +1 Brutal, but if a company is going to insist on using VisualSourceDestruct, then it will serve them right to find the letter of their law adhered to in this way. – grenade Sep 13 '10 at 13:41.
Poor you, I feel your pain. How about a nightly export of your code zipped up and stored in VSS? Most tools are for moving the other way so if you want this automated you will have to write something yourself.
Seems like a good idea to create a batch file that regularly checks the current sourcecode from SVN into sourcesafe. You could create a batch file that is run every night via a scheduled task. It would use sourcesafe command line utility to check out the entire codebase to the local filesystem.It would then do the same thing using the subversion command line client to do a get on the latest version into the same directory.
You can then check in using the sourcesafe command line util. The hard part would be detecting new files added to subversion and adding those to the sourcesafe database. You could, hypothetically, iterate through all the files and see which ones aren't marked readonly after the last checkin.
Another issue would be handling renames and deletes; I suppose it wouldn't much matter that deleted files remain in sourcesafe, since it sounds like nobody is actually using that codebase.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.