SourceGear Support

There are some big problems with this approach. The merge branches wizard doesn’t let you select discontiguous ranges of transactions to merge. This means I would have to start with the oldest transactions, select the contiguous range that ends with the first merge transaction, resolve all the confl...

Thanks for the advice and yes, please add our vote for that feature.

Normally we develop our latest release in $/Project, and the branch never changes. When we release a version, we branch $/Project into $/Project-x.y and that becomes our maintenance branch. Changes from $/Project-x.y are easily merged back into $/Project. Recently we created a real development branc...

We upgraded from SourceOffSite/VSS to Vault about six months ago. Vault is easy to evaluate. The VSS import tool worked flawlessly and ran in less than 24 hours including all our build labels. There are some appealing aspects of the Vault server: The repository is in a SQL database, which makes it e...

Earlier today I deleted my C:\Vault4.0\Branch-x tree and started over, this time paying close attention to working folder assignment during the process. I got bunch of complaints about the out of hierarchy project references, but then when I did a Get Latest Version on the whole branch, VS 2005 seem...

Hi. After I closed VS 2005 I couldn't delete my working folder. I finally discovered that devenv.exe was still running (without any windows), and still had my project open.

Yes, I was using an existing folder, because that is what I believe most of our users will have to do. It was bound using the previous version of Vault, which is why I attempted http://support.sourcegear.com/viewtopic.php?t=7937 I changed my top-level working folder to C:\Vault4.0 and got the latest...

Hi. We've just postponed our upgrade from Vault 3.5.2 to Vault 4.0. I attempted a test upgrade on a backup copy of the repository and haven't been able to bind our build solution using the Vault 4.0 Visual Studio 2005 plug-in. Here is a list of problems I ran into in the order that I ran into them: ...

All of our web projects are web site projects. Does that mean Vault 4.0 keeps binding information in scc files for these and works the same as in 3.5?

DBScriptSafe is an open source project for integrating SQL Server changes into an SCC repository. It is designed to work with VSS. Has anyone taken a look at using it with Vault? It uses Microsoft.VisualStudio.SourceSafe.Interop (in microsoft.visualstudio.sourcesafe.interop.dll). Does Vault support ...

Thanks for your detailed reply. I think you've addressed 90% of what I needed to know and it sounds like Vault 4.0.1 is very close to the process we need. Getting rid of the vspscc-like files is a plus for us. Keeping the repository path out of the projects will make branching easier, and also make ...

Ian Olsen wrote: "The 2005 client no longer uses MSSCCI-style binding at all." Could you explain how binding in Vault 4.0/VS 2005 client works? Or point me to some documentation about it? I'm particularly interested in any changes in the behavior of the VS 2005 Change Source Control functi...

We don't have any experience with v4.0 yet, so this is all based on VS 2005 and Vault 3.5.2. We frequently see a Source Control dialog: A project or solution you are trying to bind contains items that are in the same folders as projects that are currently under source control. To resolve this issue,...

We're considering upgrading from Vault 3.5.2 to Vault 4.0.1. Is this advisable? One concern raised is whether new 4.0 features make the risks associated with a new major release worthwhile. We've had a lot of difficulty binding all the projects in a complex Visual Studio 2005 solution using the Vaul...

Hi, numerous users here at Carbonite, including myself experience frequent Vault client/server connection failures. This problem is so pervasive that several users have commented that they no longer leave the Vault client running. They close it after every transaction. Some users reported this probl...