Changes just getting "lost"...
Moderator: SourceGear
Dino, You said the problem seems to happen with shared files. We'd like to take a closer look so we can determin what's going on. We could do a remote assist session to see how your project is set up, including shares, etc.
Another thing that might help is to keep a Vault Client open for reference, just to see what it's reporting about file status, etc. and diffing as you go along to make sure Visual Studio is modifying the correct files, etc., at least until we can determine what the problem is.
Another thing that might help is to keep a Vault Client open for reference, just to see what it's reporting about file status, etc. and diffing as you go along to make sure Visual Studio is modifying the correct files, etc., at least until we can determine what the problem is.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
We could try a remote support session, but I can't guarantee it will fail. It sometimes fails, mostly works. So you might see nothing, although it may be worth looking at the images I sent to Beth - I edited one shared file, however when selecting "Check In" from the menu for the solution, it tried to check it in from 2 different solutions at first. I cancelled and restated VS, and then it wanted to check it in from all 4 locations - but it had only been changed in the one solution obviously. That did concern me - why would it try to check in all 4? Could it perhaps be trying to check in one of the unmodified ones, deciding it's unchanged and rolling back?