Hello,
Currently we are using VSS. We want to use VAULT for the new projects but still use the VSS for our existing projects. So can I install VAULT on the same server which has VSS Admin installed?
Thanks
rudrvij
Vault on the same VSS Server
Moderator: SourceGear
This was the most recent article on this topic - so thought I'd add my supplementary question here....
Is there a way to painlessly change from VSS client to the Vault client from within either Visual Studio 2003 and/or Visual Studio 2005 assuming you have cause to use both on the same developer workstation? (I'd heard at one point one was exclusive of the other where Visual Studio 2003 is concerned....)
Is there a way to painlessly change from VSS client to the Vault client from within either Visual Studio 2003 and/or Visual Studio 2005 assuming you have cause to use both on the same developer workstation? (I'd heard at one point one was exclusive of the other where Visual Studio 2003 is concerned....)
Yeah it's an "eithe/or" situation. We're not talking about blended solutions with VSS & Vault projects or anything funky like that. 
However, there is a need where I'm working presently for using both Vault and VSS on the same workstation for completely different projects. And this condition may arise again in the future. If it does, at least, I'd like to know whether the option to use Vault in tandem with VSS (as described above) exists.
Gratefully,
However, there is a need where I'm working presently for using both Vault and VSS on the same workstation for completely different projects. And this condition may arise again in the future. If it does, at least, I'd like to know whether the option to use Vault in tandem with VSS (as described above) exists.
Gratefully,
Yes, you can use VSS and Vault for source control on the same client machine. It works a little differently depending on if you are using VS 2005 or VS.NET 2003.
In VS 2005, if you have a solution bound to a particular source control provider, you can just open the project and VS 2005 will use the correct provider. When you create a new project and want to add it to a particular SCC provider, choose from the Plugin Selection in VS 2005 under Tools->Options->Plugin Settings.
When you open a project in VS.NET 2003, you have to make sure your default source control provider is the same as the provider the solution was bound to.
For example, if you're opening a project bound to VSS or want to add a new project to VSS, you need to make VSS your default SCC provider. One way to do this is by unchecking "make Vault your default SCC provider" in the Vault GUI Client under Tools->Options->General.
Or you can use a handy SCC switcher, which provides a little GUI that shows your installed SCC providers and allows you to switch between them:
http://www.sitedev.com/downloads.aspx
In VS 2005, if you have a solution bound to a particular source control provider, you can just open the project and VS 2005 will use the correct provider. When you create a new project and want to add it to a particular SCC provider, choose from the Plugin Selection in VS 2005 under Tools->Options->Plugin Settings.
When you open a project in VS.NET 2003, you have to make sure your default source control provider is the same as the provider the solution was bound to.
For example, if you're opening a project bound to VSS or want to add a new project to VSS, you need to make VSS your default SCC provider. One way to do this is by unchecking "make Vault your default SCC provider" in the Vault GUI Client under Tools->Options->General.
Or you can use a handy SCC switcher, which provides a little GUI that shows your installed SCC providers and allows you to switch between them:
http://www.sitedev.com/downloads.aspx
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
I second the motion ...
SCC Switcher is free and it works for other tools that have built in source code control capability, but none to switch the provider.
A major plus is that you can use SCC Switcher before you start VS 2003 and then you skip the exit/restart cycle.
A major plus is that you can use SCC Switcher before you start VS 2003 and then you skip the exit/restart cycle.