I agree with you, there is no benefit in using SourceSafe, but unfortunately
we cannot deliver as a tarball, we "have" to check in the code on the
repository they created.
One of the problems we find is that when we check out the code from
SourceSafe, some files (.csproj and .sln) have embedded metadata related to
SourceSafe. One of the solutions we would like to try is to "comment" or
"remove" the metadata before creating our SVN repository. This would imply
more work, because we would have to "uncomment" the metadata when we have a
deliverable to check in on the SourceSafe repository.
I don't know if this is a good idea, but as I said in my first message, I'll
rather use SVN much more than SourceSafe.
Thank you for your answer,
On 9/26/06, Eric Hanchrow <email@example.com> wrote:
> Since you seem to be willing to manage revision control yourself (by
> using Subversion) I don't see that there's any benefit at all to using
> SourceSafe. I'd try to talk them into letting you simply deliver the
> code periodically -- presumably by making a tag, which you then
> "export" and deliver as a tarball.
> Imagination means having odd ideas, and it's hard to have odd
> ideas about technology without also having odd ideas about
> -- Paul Graham
Received on Wed Sep 27 17:14:37 2006