How do you feel about SourceGear Vault?

Question

I am considering buying Sourcegear Vault for mydev team as an alternative to Subversion / TFS. Cost is not an option / question here, and I want something more modern than SVN.

How do you rate its use in a team? What do you like about him? What do you dislike about this? Hate? annoyed? Good? Poorly? Is it worth it to get?

Answer 1

We are currently using SourceGear Vault 3.5, integrated with Visual Studio 2003-2010.

Using SourceGear Vault in a team environment can upset weak merge features.

SourceGear Visual Studio. . , TortoiseSVN . , .

, SourceGear Vault SVN, - , , , , SVN .

. , TortoiseSVN TFS Vault. Vault , TFS .

Answer 2

( 2 5 , projct), Vault 3.0 VSS 2005 . , , , VSS, , , TFS.

Answer 3

. , VS , , , , 60%, ...

svn... , :) ... svn , 5 ( 4 vs 2010), - , , , ... , , ... , dev prod, , dev... : (

Answer 4

SourceGear Vault Professional ( ) . , . , Visual Studio . . Vault : Edit-Merge-Commit (CVS Model) Checkout-edit-Checkin.

Source Control Management, SCM. , SourceGear, " HOWTO" post , , SCM , Vault, .

All that said, we play with the idea of ​​switching to TFS. Our team is growing, and TFS provides a much richer suite of ALM features than Vault Professional (Fortress) and Axosoft OnTime, a product with which Vault Pro integrates.

John, if you've already purchased SourceGear, I'm curious about your experience.