Visual Studio plugin won't change to Vault Client

[rda]

Good morning,

So here's the problem - I have a project under source control in Vault which works fine for 90% of my team members. However, I have two people who are having problems with the Visual Studio plug-in for Vault Classic Client. Each time they load up Visual Studio (2005 version), the source control plug-in automatically switches to Microsoft Visual Source Safe (which we used on previous projects). If we try to change the plug-in, we get a message that says the project is under source control from a different plug-in and will close if we change plug-ins. So the end result is that we can't use the Vault plug-in from within Visual Studio on these computers. In terms of the source control bindings in the files, they are all correct - I use the exact same files and project on my computer and it works fine, and most of the team members have had no problems. The problem occurs even when we delete the entire project and get latest from Vault from scratch (which has all the Vault bindings and none of the Visual Source Safe bindings).

So I can't help but feel like there are some sort of temporary files somewhere that are controlling this behavior - I tried deleting everything in the Docs and Settings/Username/Local Settings/Temp folder, but the problem persists...

Any solutions?
Thanks!

[Beth]

Do those users have entries for the Vault clients listed in their VS Tools - Options - Source Control?

What type of project is this? Is it website?

[rda]

It is a C++ project, just a regular desktop application.

The Vault client is listed for them under the Source Control options in Visual Studio, but when we pick it, the project is forcibly close with the "This project is controlled by a different source control provider" message. The strange thing, as I mentioned, is that the same project works correctly on most of our machines (i.e. it correctly loads up the project with Vault Classic Client as the plug-in, and allows us to log into Vault from within Visual Studio).

I don't understand where the tie-in is between the plug-in selected in Visual Studio and the plug-in that Visual Studio claims is "controlling" the project, since I have all the relevant *.vcproj and *.sln files set up to use Vault.

[Beth]

Let's try the following.

1) Remove the current copy from the users computer.
2) Have the user create a new blank folder that will be used for this project. Do not reuse the previous folder.
3) Close any open instances of VS, then just open on VS instance, but with no project being opened.
4) Go to Tools - Options - Source Control and set it to use the Vault Classic Client.
5) Go to File - Source Control - Open from Source Control.
6) In the window that opens, select the folder that holds the .sln file, and specify the new blank folder that was made for this solution.
7) Click OK and let me know your results.

If it gives the same errors again, then I will provide a different set of instructions.

[rda]

I could have sworn I tried that before but I did it again according to your instructions and now it works. Maybe I had left some hidden files in there the first time, since I didn't actually remove the folder and create a new one. Anyway, problem solved, thanks!

[Beth]

Thanks for the update. I'm happy to hear you're working.