Diff is incorrect on pinned files

Xavier · Post by **Xavier** » Fri May 11, 2007 8:59 am

Hello,

on a pinned file, if you call show diff, the diff is based on the current file version, not the pinned version. You need to go to the history dialog and select the pinned line to have the diff work on the correct version.

Best regads

Xavier PICAT

Beth · Post by **Beth** » Fri May 11, 2007 1:01 pm

What version of Vault are you using?

Xavier · Post by **Xavier** » Mon May 14, 2007 2:09 am

Hello,

I'm not using Vault but SourceOffsite.
The client and server use version 4.2

Beth · Post by **Beth** » Fri May 18, 2007 1:49 pm

I ran a test with what I have here. It appears that the VSS API may be sending the wrong thing to the SOS server, but I used an older VSS API. I will need to compare that to the others yet.

Can you tell me what Version of the ssapi.dll you are using? Details on making sure you have the right file that's registered can be found here: http://support.sourcegear.com/viewtopic.php?t=1510

Xavier · Post by **Xavier** » Mon May 21, 2007 2:20 am

Hello the version is

6.0.92.38

Xavier

lbauer · Post by **lbauer** » Mon May 21, 2007 6:23 am

Could you describe the steps to reproduce this? Are you just right clicking on the pinned file and doing a show differences? Are you comparing the pinned version against a different version in your working directory?

Xavier · Post by **Xavier** » Mon May 21, 2007 6:59 am

select a pinned file that has been modified after the pinned version
GLV on that file (let's say latest version si 100)
->At this point it's the good version that is on disk (so the ssapi.dll works)

Then select the file, clic the showdiff icon. On the right side you have %temp%/version_100<file>.cpp(latest version has been extracted, not the pinned one) and on the right the pinned version on disk.

According to me everything is OK, but Sourcegear doesn't ask for the right version of file. GLV is OK, but when showing diff, it asks for the latest version not the pinned version

lbauer · Post by **lbauer** » Tue May 22, 2007 8:34 pm

I was able to reproduce this with the SOS server using the Microsoft hot -fix version (6.0.96.40) of the VSS automation component.

The diff worked properly when I was using the VSS 2005 automation component with the SOS server.

Most of SOS behavior is determined by the version of the automation component, as that is how the SOS server communicates with the VSS database. If there's a problem with the automation component, there's not much that we can do about it, since this is a VSS issue.

However, you can change the version of VSS that is being used by the SOS server.

Xavier · Post by **Xavier** » Wed May 23, 2007 7:03 am

OK,

it works with Visual Source Safe 2005. Thanks