Cached changes

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Ralf
Posts: 19
Joined: Wed Dec 30, 2009 1:27 am

Cached changes

Post by Ralf » Mon Mar 08, 2010 7:23 am

Using Vault 5.0.3 (18802) on Vista 32bit (migrated from 4 to 5 last week).

I renamed some project files from Visual Studio within on solution. Pending changes contain modifications and renames (like it should).
After some time they get the status "Namespace conflict". I saw this before and decide to revert everything.
I want exactly the server version, so I delete the local folder for that solution and perform get latest from the vault client to get the files.
However, the local files now have the new name (from the renaming above) but i don't have pending changes anymore!
In Vault client I also see the new names, in the webclient I see the old names.

When I disconnect and reconnect again, everything seems to be fine.

I'm almost 100% sure I did not have this behaviour with the previous version (4).
Is this how the software should react?

Earlier today I saw a shared folder in the vault client (with the blue arrows sign), right clicked on it and viewed the shared links tab. This had a message that the folder was not shared.
Reconnecting solved this also.

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Cached changes

Post by lbauer » Mon Mar 08, 2010 11:03 am

I'm trying to reprodice this, but could use more info.

What version of Visual Studio are you using? I assume you're using Enhanced Client for integration?
so I delete the local folder for that solution and perform get latest from the vault client to get the files.
Did you close Visual Studio first, or just close the solution?

When you did a Get Latest from the Vault Client, were the renames still in the pending changes set of the client?
Linda Bauer
SourceGear
Technical Support Manager

Ralf
Posts: 19
Joined: Wed Dec 30, 2009 1:27 am

Re: Cached changes

Post by Ralf » Mon Mar 08, 2010 2:29 pm

Pending changeset is empty (that's the strange part).
I closed Visual Studio (not only the solution).
Visual Studio 2008 SP1 with enhanced client.

Ralf
Posts: 19
Joined: Wed Dec 30, 2009 1:27 am

Re: Cached changes

Post by Ralf » Mon Mar 22, 2010 2:15 am

Any ideas?

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Cached changes

Post by lbauer » Mon Mar 22, 2010 1:24 pm

It sounds like there are problems with the client-side cache or with the server cache, because one or both are reporting incorrect information.

Are you still experiencing this type of behavior?

Here's what I would suggest:

You can reset the cache with the following steps Find the path
C:\Users\username\AppData\Local\Sourcegear\Vault_1
and rename the entire Vault_1 folder. Restart IIS with an "iisreset" command.

Next, reset working folders and perform a Get Latest with Do Not Overwrite/MergeLater to re-establish baselines, rebuild the cache files and reset file status.
Linda Bauer
SourceGear
Technical Support Manager

Ralf
Posts: 19
Joined: Wed Dec 30, 2009 1:27 am

Re: Cached changes

Post by Ralf » Tue Mar 23, 2010 2:23 am

Tried the above (remove the local cache folder and reset IIS), but that doesn't help.
To make sure the problem is clear:
- Open a solution with Visual Studio that contains multiple projects.
- Rename one project in the solution tree
- Save All
- Pending changes contains : the solution file is modified, projects that reference the renamed project are modified, the renamed project has status renamed.
- Close Visual Studio
- Remove the complete folder that holds the solution and all projects.
- In Vault client pending changes : all changes are gone from pending changes except the rename action!
- Use Vault client to retrieve the folder again from Vault (any setting in get latest dialog).
- Still all changes are gone from pending changes except the rename action!

Can you reproduce this?

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Cached changes

Post by lbauer » Tue Mar 30, 2010 9:45 am

I think I reproduced this enough to understand what you are seeing.

The pending change set shows files that are checked out in the working folder and also lists operations that have not yet been committed.

When you removed the files from the working folder, they no longer were being tracked in the pending change set.

However the rename stayed in the pending change set because a rename operation is not dependant on having the file in the working folder.

You can undo the rename by selecting that line in the pending change set, right-click and choose Undo . . .
Linda Bauer
SourceGear
Technical Support Manager

Post Reply