Vault, VS2005 & edit-merge-commit

JonEdwards · Post by **JonEdwards** » Fri Jan 06, 2006 9:04 am

Hi all,

We're staring a new project and are going with Vault over VSS, based largely on the recommendation of one of our consultants. So far it looks like a fantastic SCM tool and we already prefer it to VSS.

In starting this new project, we'd like to give edit-merge-commit a try.

How many people out there are using this style of source control along with VS2005 (or even VS2003)?

Will I need to completely disconnect VS's source control and let the Vault client handle everything?

Jon

lbauer · Post by **lbauer** » Fri Jan 06, 2006 9:17 am

Visual Studio expects the VSS-style checkout-edit-checkin. Use VSS style if you plan to integrate VS.NET or VS 2005 with Vault for source control.

Use Vault as a stand-alone app for source control functions and do your development in Visual Studio if you wish to use CVS style.

More info here about IDE vs GUI Client:

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

JonEdwards · Post by **JonEdwards** » Fri Jan 06, 2006 9:34 am

Thanks Linda,

My team is fairly new to VS, coming from another development environment where SCM and IDE are completely unrelated. So, not using the IDE will seem natural to them. However, I have a question that didn't seem to be in that KB article.

If we opt for the client over the IDE, is there some way to make sure that the Vault client ignores changes to "bin" and "obj" folders but will pay attention to other subfolders changes (add/rename/delete) in a project? This is winform, not web, development fwiw.

Jon

Marc · Post by **Marc** » Fri Jan 06, 2006 11:08 am

That will not be a problem because Vault will only control the files that you add to it. So long as you don't add them, Vault will not even know they are there.

There is an added layer to this as well in that Vault seems to know which files/directories it typically should ignore and when you add a directory it will not select those files by default.

lbauer · Post by **lbauer** » Fri Jan 06, 2006 11:30 am

Marc is correct -- Unlike Visual Studio, Vault itself does not make any decisions about what goes into source control.

The Vault Admin tool has configurable file and folder exclusion lists in Repository Options, so that certain file/folder types don't automatically get added, like the bin or debug folders.

Also, you can choose what gets checked out, unless you're doing a recursive checkout on a folder.

JonEdwards · Post by **JonEdwards** » Fri Jan 06, 2006 12:36 pm

Linda and Marc,

Thanks for your help. So far we couldn't be happier with Vault. The fact that we're no longer using VSS just makes it that much sweeter.

Thanks again,

Jon

ismangil · Post by **ismangil** » Thu Jan 12, 2006 6:21 am

JonEdwards wrote:Linda and Marc,

Thanks for your help. So far we couldn't be happier with Vault. The fact that we're no longer using VSS just makes it that much sweeter.

Thanks again,

Jon

And wait until you discover the Client API and the server plugins API... your team will dream up many integration scenarios with your build system, issues log, etc etc!