Menu
What are your recommendations to use as a source control, project repository for a Windows - .NET development environment (two coders, possible one using the system)?
Addition: also the team includes three developers. One Visual Basic 6.0 moving to .NET, myself in .NET, and one web developer (PHP, JavaScript, etc.)
The system I am looking for would be something that easily integrates into the IDE of Visual Studio.
309
Git is one of the best version control tools that is available in the present market. Provides strong support for non-linear development. Distributed repository model. Compatible with existing systems and protocols like HTTP, FTP, ssh.
SCM version control is a way to manage and document changes developers make to software code. Version control system (VCS) are also known as source control management (SCM), so the terminology is interchangeable.
Without a doubt, Git is the single most popular version control system in use. Not only does Git offer the strongest feature set for developers, but it also has the most reliable workflow and is supported by the most third-party platforms on the market.
VCS are sometimes known as SCM (Source Code Management) tools or RCS (Revision Control System). One of the most popular VCS tools in use today is called Git.
You can use TortoiseSVN and any Visual Studio plugin for svn: AnkhSVN or VisualSVN.
Quite some time has passed. If I were to answer this question today, I'd strongly recommend using git. I personally use it even when working alone. I didn't try to integrate it into Visual Studio, but standalone app SourceTree serves me well. If you never used git before I'd recommend reading Pro Git book (it's free). Evening or two spent on it will pay off.
140
Team Foundation Server is probably the most integrated into Visual Studio.
However, I personally love Kiln (which also integrates nicely into VS). This is nice for a small team, being hosted and very elegant and easy to use.
Other options include Subversion and Git. However, without knowing more requirements, it's difficult to suggest the "best" option for a small .NET team. Self-hosted vs. hosted for you is probably the largest factor in making your decision...
36
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
