Using SOS 4.0 client and server. Often times when I check-in a file that has SourceSafe inserted comments turned on, I'll get a merge error. The error results in my local copy not having the generated comments added and I usually end up having to get the latest from SS again, this time overwriting my local copy. This in turn will change the time stamp on my local file which leads to more re-compiles. Is this a known issue?
Thanks,
Paul
Check-in problem with generated comments
Moderator: SourceGear
I don't think we've had this reported. Is this some thing you can reproduce? If so could you post the steps so we can reproduce it in-house? Also let us know what version of VSS is installed on the SOS Server machine. We've found some differences in behavior in SOS depending on the version of the SourceSafe API it's using.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Steps to reproduce are simple: enable keyword expansion, add a keyword to your sourcefile in a comment block (I used $Log $), check in the file, add a check in comment, you should receive a merger error.
We've decided to simply turn off keyword expansion in VSS since it provides no value to us (not sure why it was ever on), so it's not a high priority for us.
We're using VSS 6.0c with SOS 4.0 clients and server.
-Paul
We've decided to simply turn off keyword expansion in VSS since it provides no value to us (not sure why it was ever on), so it's not a high priority for us.
We're using VSS 6.0c with SOS 4.0 clients and server.
-Paul