Major Vault 4.0x VS2005 client issues

[isg]

Hi.

I am having major issues with the Vault 4.0.x VS2005 clients! Sometimes when working in parallel and two developers works on the same file changes are lost! This happens when developer one checks in the file, and deveveloper two gets latest, then the changes from developer two is not merged into developer twos file!

Could this be caused when running vault commands when a file is changed in memory but not on disk?

Also when will the need to do multiple get latest /refresh cycles to update file status in VS2005 be resolved?

[GregM]

Could this be caused when running vault commands when a file is changed in memory but not on disk?

Yes, I've done this myself. I thought I had saved all my changes in the IDE before starting the get/merge, and ended up having to overwrite the changes I just merged in to not lose what I had in the editor.

[isg]

Is it possible to make the Vault Visual Studio save all changes before making any operations? This way we will no longer loose changes when somebody forgets to save the files before updating!

Also the problem with having to do multiple Get Latest from VS2005 before the file is actually updated. When will this be fixed?

One last thing. Would it be possible to have the Show history command show folder history by version in a tree like structure and have expand buttons if you want to see the individual update items? Like:

[+] Some commit string...
[-] Some older commit string...
|- File 1
|- File xxx
[+] Some even older commit string...
|- Some File
.
.
.

[ian_sg]

I am having major issues with the Vault 4.0.x VS2005 clients! Sometimes when working in parallel and two developers works on the same file changes are lost! This happens when developer one checks in the file, and deveveloper two gets latest, then the changes from developer two is not merged into developer twos file!

I responded to this one on your other thread.

Could this be caused when running vault commands when a file is changed in memory but not on disk?

It shouldn't be. Open files are always saved before a checkin/commit or a get latest.

Also when will the need to do multiple get latest /refresh cycles to update file status in VS2005 be resolved?

We've put a lot of work into this, and look forward to including it in the next maintenance release.

[ian_sg]

Is it possible to make the Vault Visual Studio save all changes before making any operations? This way we will no longer loose changes when somebody forgets to save the files before updating!

This should be happening. If you're seeing different behavior, I'd like to know.

One last thing. Would it be possible to have the Show history command show folder history by version in a tree like structure and have expand buttons if you want to see the individual update items? Like:

[+] Some commit string...
[-] Some older commit string...
|- File 1
|- File xxx
[+] Some even older commit string...
|- Some File
.
.
.

An interesting idea. I've logged it for consideration in the future.

[ian_sg]

Yes, I've done this myself. I thought I had saved all my changes in the IDE before starting the get/merge, and ended up having to overwrite the changes I just merged in to not lose what I had in the editor.

For clarification, I think I remember you saying that you don't use IDE integration, Greg. Which would mean this was your fault. Is that right?

[GregM]

Yes, I don't use the IDE integration, and this was entirely my own fault. Sorry if I didn't make that clear enough.