Changes just getting "lost"...

[Dino]

I modified a file in a web project, and then did a "get latest" of all old files from Vault - this included the web project, so VS asked me if I wanted to reload the web project - I said yes, and then there was a warning about files I had checked out - I didn't read it to be honest , and just clicked continue.

I checked everything in, carried on, and my changes to other files were lost.

I checked them out again, made the changes again (just to be sure I wasn't imagining things) checked them in, and then... they were lost again!

Vault said these files hadn't been changed for 6 months! I *KNOW* I made the changes, because I had to do them twice. And this isn't the first time - occasionally I've checked out a shared file that has the version for the solution, changed it, clicked save, checked it in, and NOTHING in vault is old. Open the file again - and it's not changed.

This is very disconcerting, because I've lost confidence in the checkin procedure, and never know what work will be lost. This has happened well more than once, so it's not just me dreaming either. Version 3.1.9.

Any comments?

[Beth]

I see two things going on here that are different from each other. One is the check in and the other is overwriting when performing a get latest.

Are you performing these actions from Visual Studio? How are you opening the file?

When you have a file on your disk that you've modified and you perform a GetLatest before checking in, you are pulling the previous code from before you checked it out from Vault again. You don't want to perform a GetLatest over changes you have made that are sitting on your computer.

[Dino]

No - there was no overwriting. I have seen this happen over the past few months. There's 2 things that happen:

1. I edit a shared file in VS.Net.
2. I click save, or close and save it.
3. I right click the solution and Check In everything.
4. I go to Vault, and *nothing* is old (other copies of that shared file should be).
5. I open the file, and the changes are gone.

or

1. I edit a file in VS.Net
2. I click save, or close and save it.
3. I right click the solution and Check In everything.
4. I try to compile, and the properties I just added are gone from that file.

Now, the exact pattern of either saving, or closing and saving etc I can't be sure of, but this is what I think I need to watch for a while. But there is no get latest of overwriting at all - it is simply losing changes.

[Beth]

Are you checking out the files before editing? I don't believe VS will support the CVS style of editing which will check in changes on disk without the item having been checked out. Try once that way instead.

It also could be a binding issue. Even when a project isn't properly bound, VS will allow working disconnected. I would suggest unbinding the project and performing a fresh open from source control. Any changes you have sitting in your working folder you will probably want to save a copy of those somewhere and I can tell you how to get those in once the project is properly bound.

[Dino]

I am checking them out - or at least, VS.Net/Vault should be once I start editing them correct?

I edit about 100 files a day, and it's only happening once or twice and I'm not doing anything different.

And no - I don't believe it's a binding issue for the same reason.

[Beth]

Vault and VS will not auto check something out unless they I set I believe. From inside the IDE check your Tools - Options - Environment. You will see a drop down called On Edit and that should be set to Check Out Automatically.

[Dino]

They auto check out 100's of files per day, and have done since I installed Vault, so I am pretty sure that option is checked.

[Dino]

But forget about it. Clearly it's a user issue and not something you should concern yourself with, so I won't waste any more of my time here...

[Beth]

If you wish, you can send an email to support at sourcegear.com and we can dig into this further if you wish. Some screenshots and logs may help provide more information.

[Dino]

It's just happened again. I had made changes, run the app, published a new build, and then right clicked on the Solution and selected Check In, and checked in all files - one of the files lost it's changes, and now the whole thing fails to build.

I know the bindings are all fine, because I went to the file, started editing it which VS/Vault automatically checked it out, made the changes again (thankfully very simple) and then right clicked on the file and selected Check In and it didn't lose the changes this time.

I have to say I'm almost frightened of Vault now - I have no idea of what changes it keeps and what it drops. I know for certain it's not a one off, because it's happened about a dozen times that I am aware of, and maybe some more where I don't know my changes were lost. I'd be safer not using source control at all, because then at least my changes wouldn't get over-written!

[Dino]

Just realised something else that might be important in this issue - all the files I have had this problem with have been shared files. If that's the reason, at least I have confidence that most of my code is safe, but I am still a bit bemused at these losses.

[Beth]

Again, I think we need to go off-line so I can look more closely, maybe connect to each other so I can see. Vault doesn't just magically not put something into the database. Can you send an email to support at sourcegear.com (attn: Beth) and include a Vault Server Log that covers one or more of your problem check-ins?

[Dino]

Nothing I can post, because logging was set to Quiet, so all you can see is me logging on and off. Will send a log next time it happens.

[ileonard]

We have documented 6 times now in which changes were lost over the last 6 months. We're not talking about isolated incidents. Things like the aspx file was updated but Vault lost the aspx.cs code-behind file changes. Files that were there are now gone. And the like.

This is with 3 developers and Version 3.5.0.4741. We're now investigating a migration back to SourceSafe.

What good is a Vault when there is a screen door at the back end?

[Dino]

I've completely rebuilt my machine (meaning all bindings are totally refreshed as I had to get everything from Vault again) and it's still happening.

I've sent my logs to support, but really heard nothing back. I'm still on 3.1 Vault I think, but can't see any point in upgrading at this stage based on your report.