Resync whole solution after unbinding and rebinding it?

dravidian · Post by **dravidian** » Fri May 23, 2008 8:34 pm

Hi there,

This is regarding vault 4.1.1 and VS2005 (team developer) on Vista

If I unbind a solution from vault 4.1.1, then make changes / adds / deletes to it, is there an easy way to automatically synch all the solution files when I rebind it? Right now when i rebind it, I have to go through and manually add, delete or merge the changed files.

Here's why i'm doing this whole bind/rebind thing - I use 4.1.1 at home for personal projects. My work computer has vault 3.something. So if i try to open a solution bound to v 4.1.1 on a machine with client 3.x, I get an error about missing SCC provider. So I have to unbind the solution in order to be able to open it up on the work computer. It doesnt give me the option to open in offline mode because i get an error unless i unbind it.

Is there an easier way to rebind all solution files back? Right now i just keep creating a new folder each time i need to rebind the solution back into 4.1.1 - but that means i lose the version history.

I can't upgrade the vault client version at work since the rest of the team uses the 3.x version and I dont really have a say in upgrading it.

lbauer · Post by **lbauer** » Tue May 27, 2008 8:47 am

There may be a workaround. Are you working on projects from work when you are at home?

When you work in Vault 4.x are you using the enhanced or classic client?

dravidian · Post by **dravidian** » Fri May 30, 2008 10:08 am

Nope, i just work on personal stuff at home.

Not sure which 4.x client I'm using but its the one thats integrated into VS 2005. How do i check if thats classic or enhanced?

Thanks

lbauer · Post by **lbauer** » Fri May 30, 2008 10:28 am

Open a project, then in Visual Studio, look under Tools->Options->Source Control->Plugin.

dravidian · Post by **dravidian** » Thu Jun 12, 2008 9:21 pm

Its the enhanced client.

lbauer · Post by **lbauer** » Fri Jun 13, 2008 5:34 pm

Vault 3.5.x uses a different integration client -- it's essentially the Classic Client, and it's the only option.

We really haven't tested using two different versions of Vault and two different plugins for the same projects. This might work if you unbind the project from the 4.1 repository/server, then rebind it to 3.5.x, then after you're done, unbind it from 3.5 and rebind it to 4.1 again. That's a lot of steps.

You'd probably be better of working on your 3.5.x projects using a Vault 3.5.x client and its integration.

It is possible to run two different versions of the Vault client on the same client machine, though it's a little tricky.

First, install the Vault 3.5.x client, if it's not already on the machine. Then copy the files in the Vault client 3.5.x directory and put them into a folder somewhere else on your drive. Then install Vault 4.1.x. You should be able to use each client from its own directory.

The tricky part is IDE integration. If you are using the new Visual Studio enhanced client, integration with Vault 4.0.x, that should work with no problem.

Here's more information on the new options for IDE integration:

http://support.sourcegear.com/viewtopic.php?t=8535

However if you are using the Visual Studio classic client for integration (MCCSSI) with Vault 3.5.x and Vault 4.1.x, you will need to change your registry settings for source control provider depending on which version of the Vault client you are using.

The path to the integration DLL is in the registry under this key:

HKEY_LOCAL_MACHINE\SOFTWARE\SourceGear\Vault Client

You will need to change this path to the proper client directory, depending on which client you are using for your IDE integration.

If you use Vault 3.5 with Classic integration and Vault 4.x with Enhanced, you won't have to do this registry switching, as each has a different spot in the registry.

dravidian · Post by **dravidian** » Mon Jun 16, 2008 10:06 am

Thanks Linda.

My issue is not that i want to use different versions of clients.

I am more than happy to unbind the solution completely and work offline in order to open it on a machine with an older client (or even without vault installed at all).

My problem is that when I unbind the project, make changes, and rebind it to an existing vault project, I have to manually reconcile new/modified/deleted files back to the vault project.

Isn't there a way for vault to automatically do this?

The solution file contains the list of project files, so vault should be able to figure out what is new, what is unused, and what files need to be checked out + modified automatically.

I'm pretty certain VSS did this after working offline.

lbauer · Post by **lbauer** » Wed Jun 18, 2008 7:46 am

You are right, Vault does not automatically do those operations, which were done off-line, when you rebind.

I will add a feature request for this functionality.