Problem with frx files checking in when keep checked out on

gbrookshaw · Post by **gbrookshaw** » Wed Jun 22, 2005 7:29 am

Hi,

We're having problems using Vault with VB. Most forms have an associated frx file. When we check out the form the frx comes with it. Fine.

When we check in and choose keep checked out it sometimes checks in the frx as it is unchanged. How do we make it stay checked out?

Thanks

dan · Post by **dan** » Wed Jun 22, 2005 8:50 am

Which version of Vault and Visual Studio are you using?

gbrookshaw · Post by **gbrookshaw** » Wed Jun 22, 2005 10:34 am

VS 6 SP6 and Vault 3.0.7 (2863)

The funny thing is when we try to reproduce it we can't! It is happening though and not just to one person!

Don't you just love software!

Does the 'Check in unchanged files' option affect this?

Thanks

dan · Post by **dan** » Wed Jun 22, 2005 1:03 pm

Yes, the "Checkin Unchanged File" would affect this in 3.0. Our 3.1 beta has a fix for this (see http://support.sourcegear.com/viewtopic.php?t=3921), so you may consider upgrading to it. We have a Beta 2 coming out hopefully this week, maybe next, and a final should be coming this summer.

Guest · Post by **Guest** » Wed Jun 22, 2005 11:09 pm

So if I change this option from 'undo checkout' to 'check in' the problem goes away? Or would the file check in still?

Thanks

gbrookshaw · Post by **gbrookshaw** » Thu Jun 23, 2005 2:29 am

Incidentally, I can now reproduce the problem in the Vault client (not on a frx file - just a vbg). The release notes imply this problem only affects IDE integration.

Let me know if you want me to send you steps to reproduce.

Thanks

dan · Post by **dan** » Thu Jun 23, 2005 9:26 am

If you change the option to "checkin", it will check the file in (creating a new version), even though it didn't change. The bug was that if the file is not modified and the option was to undo the checkout, it would undo the checkout, but then not redo the checkout (because the second option asks for the file to be checked out again).

This shouldn't happen in the GUI client in 3.0.7. If you have steps to reproduce it, definitely let us know.

Thanks,

gbrookshaw · Post by **gbrookshaw** » Fri Jun 24, 2005 1:28 am

Hi Dan,

Here are the steps to reproduce in 3.0.7

1. Create a simple text file with 2 lines in it. 1st line 'a', 2nd line 'b'.
2. Set the option to be 'undo check out'
3. Add file to project
4. Check it out
5. Open text file in Notepad, reverse lines so that 1st is b and 2nd is a
6. Save it
7. The pending change set reports 'size unchanged'
8. Change text file back so that 1st is a and 2nd is b
9. Save it
10. The pending change set still reports 'size unchanged'
11. Choose 'Commit All' AND 'keep checked out'
12. The file gets checked in when it shouldn't....

If I had done the commit all after step 6 it would have worked. It's only when the file has been modified and then modified back to it's original state.

Hope this helps.

Great product by the way - what a joy to use after 10 years of SourceSafe!

dan · Post by **dan** » Fri Jun 24, 2005 8:48 am

Ok, yes, I'm seeing this now. Actually what I'm seeing is that the file correctly does not get checked in, but incorrectly does not get checked out automatically again either.

I'll add this as a bug - thanks for the report.

dan · Post by **dan** » Fri Jun 24, 2005 8:59 am

FYI, one work around for this scenario is to use CRCs to determine whether a file has changed (in Tools->Options->Local Files). Then it correctly identifies the file as not really having been modified, which prevents the bug from happening.