Client not sycing

[mturner]

Client machine:
Win 7 Pro x64
Visual Studio 2010 (C# Windows Application solution)
Sourcegear Vault Standard 9.1.0 (584)

Visual Studio Souce Control Options:
Source control plug-in: Sourcegear Vault Standard Classic Client
Environment Settings: "Get everything when opening a solution or project" is only checked item;
Checkout Automatically on Save and Edit.
No Advanced options changed.

Server:
Win Server 2012 R2 x64
SQL Server 2014 Standard
Sourcegear Vault Standard 9.1

We have only been using Vault for a few months months and are having some teething trouble.
(We purchased one year of support, but our server guys took so long setting up the new servers that it ran out before we got to use it, oh well ):).

I have branched a new version of a C# Windows application solution in the repository, from the trunk.

The developer opened Visual Studio and selected File / Source Control / Open from Source Control... from the main menu.
Entered Vault login and selected the branch from the repository and selected a local folder.

So far so good.

The developer edits a project file and it checks out the file, as you would expect.
The developer makes required changes and checks them back in.
The client machine does everything as expected to make it look like the changes are saved back to repository.
If he does a compare it even says his local copy is identical to the server copy.

But it is all a lie!

The repository has not changed.
When he opens the Vault client and looks at the branch, the files he has updated have a status of Renegade.
Viewing History of edited files shows no changes.

Everything seems to be pointing to the right places: The vault client has the correct Working Folder; the Visual Studio Source Control Properties say it is bound to the correct Vault server location.

So what's going on?
And how do we make it right?

[Beth]

It's possible your Vault client and your Visual Studio had their working folders set separately, but either to different locations or in a different manner.

Here's what to do.
1) Close the Vault client.

2) With your solution open in Visual Studio, go to File - Vault Source Control - Change Bindings. (or Source Control - Change Source Control if on Classic Client)

3) Unbind all the lines.

4) Click OK. This step is absolutely necessary to effect any change.

5) Return to File - Vault Source Control - Change Bindings. (or Source Control - Change Source Control if on Classic Client).

6) Select all the lines and click Bind. If you can't select all, then select each line that is not the solution and bind each one.

7) Check that the status says Valid, and then click OK.

VS may offer to check out files. That's fine. You will then check in any changes it made to bindings.

Then try to work and see your results.

[mturner]

That seems to have fixed it.
Thanks.

[Beth]

Thanks for the update.