suggested source control system for visual studio 2010
Hi there,
Just wondering if you guys had a suggestion as to which source control would be the easiest/best to use? I'm web developer and use visual studio and my primary tool, so something that integrates with that would be really nice. And i would prefer something that will lock files when someone starts to edit one to prevent two people from working on the same file at the same time.
any suggestions?
thanks
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Ken Robertson on 26 Jul, 2010 02:09 PM
On Windows, the most common source control system is definitely Subversion.
Git and Mercurial can have a steeper learning curve, and their GUI experience is weaker. They are more commonly used from the command line, especially on other platforms.
I would not suggest using exclusive file locks though. Those get to be an incredible headache, and source control systems have gotten more mature in their merging capabilities. Git and Mercurial are excellent at handling merges, and Subversion is still pretty good.
I used to use exclusive locks and they are a major pain. I've literally had to call people up and ask them to unlock a file because I need to make a change to it. You get people forgetting to release locks when they're done, or they go home for the night or away for the weekend with it locked.
Ken Robertson closed this discussion on 26 Jul, 2010 02:09 PM.
misc re-opened this discussion on 26 Jul, 2010 05:23 PM
3 Posted by misc on 26 Jul, 2010 05:23 PM
I thought with subversion there's the option of ignoring a lock? I dont
particularly want a file locked - but i would like some way of knowing that
someone else is also working on a file. Plus in this particular instance,
there's only 2 other people working on this project so the issue of people
forgetting and leaving a file locked isn't likely to be much of a problem.
I probably wont be able to use git or mercurial if they are mainly used from
the command line. I dont have a problem using the command line, but i know
the others will. It needs to be something that requires very little extra
steps to work with.
Thanks for your suggestions.
I'll take a look at the GUI for git and mercurial anyhow though and see if
they have enough functionality for my needs.
thanks
Support Staff 4 Posted by Ken Robertson on 26 Jul, 2010 06:40 PM
Its been about 8 years since I used locking with any source control systems, so I'm not entirely sure on Subversion's locking. I rarely hear of people using locks though, since most people have bad experiences. My last project that used locks was with only 3 others and we still had headaches. Regardless of team size, if your codebase is small, the changes of encountering it go up.
Ken Robertson closed this discussion on 26 Jul, 2010 06:40 PM.