vault plugin not recognizing directories in vault

[ghinks]

I am currently using visual studio 2010 (VS) with the vault plugin for the standard client. I encountered an error '80004005' after which I lost some data. I was able to add back in the files that were missing but now the plugin with VS no longer sees those solutions as part of vault. They are in the vault source control system as I can check them in/out using the standard vault client. But the plugin no longer recognizes this meaning I have to use the client outside of the Visual Studio environment.

This is what I see in the vault client 5.1.1

vaultClient.png (83.92 KiB) Viewed 3637 times

This is what I see in visual studio using the plugin

plugin.png (119.68 KiB) Viewed 3637 times

Previously I had nice little padlocks on all the solutions

I am pretty sure this was the result of the error but after a great deal of time spent on this I have been unable to resolve this issue.

Any pointers would be greatly appreciated

[lbauer]

Since data was lost, binding information may have been lost as well. Bindings are the associations between projects/files on disk and the project/files in the repository. Vault integration writes connection information into solution and project files if they are using the Enhanced Client integration, or in the MSSCCPRJ.SCC file if they are using Classic Client integration.

I would first recommend that you unbind and rebind this project.

Here's information for unbinding and rebinding:

First, open your solution. If you are using the Vault Enhanced Client integration, use the menu item "Change Vault Bindings" in Visual Studio under File->Source Control. This will give you an Unbind dialog where you can remove the bindings. After you unbind, "save all" to save your unbound solution and project files.

Next, click "Change Vault bindings" again. In the bindings dialog, click bind, and you'll get a login to Vault. Connect to the Vault server, locate the project in the repository tree, and then click bind. "Save all" again, and check in your changes.

If several people are using the same project, one person can change the bindings, and check them in, and the rest of the team can do a Get Latest on the project to get the new project bindings. This works if they have the same working folder structure as the person who created the bindings.

If you are using the Classic Client integration, look under File->Source Control->Change Source Control in Visual Studio to get the bindings dialog.

Let me know if this does not resolve the problem.

[ghinks]

Many thanks . Rebinding resolved the problem.

I think that I now understand the client is not bound but the plugin to visual studio obviously binds.

Glenn Hinks

[lbauer]

Thanks for the update. That's good news. : )

Let me know if we can be of assistance in the future.