Hi I am currently using Visual SourceSafe, I do not find it easy going. What are other people using, and does it a) integrate into Visual Studio 2005 and 2008. b) allow a migration path from Visual SourceSafe with full history/versions.
Thanks
+6
A:
Both are excellent source control systems.
We use SVN in work as there are serveral good clients (TortoiseSVN) for explorer and for integration with the IDE (AnkhSVN or VisualSVN)
Also search Stackoverflow for "Visual Studio" & "Source Control" or either of the above specific SCM's and you'll find plenty of other people sharing their opinions and experience with them.
Eoin Campbell
2009-06-04 09:11:49
+1 for SVN. Also there are a great number of same questions on SO
abatishchev
2009-06-04 09:14:25
+1
A:
What about SourceGear's Vault ?
It uses a SQL Server database to store your projects, it has VS.NET integration, etc... You can also convert or import your VSS databases into it.
It used to have a free license for single user licenses, but I don't know if that is still the case ...
If you would like to stay with MS tools, you could also take a look at TFS ?
Frederik Gheysels
2009-06-04 09:15:24
+1 - Vault is a great and very useful tool - highly recommended. Free for teams up to 2 programmers, and worth every penny for larger installs.
marc_s
2009-06-04 11:23:50
+2
A:
I'm a big fan of SVN - usually via TortoiseSVN (IDE integration is over-rated, IMO).
A quick search shows a tool here that will move VSS into SVN with history.
For hosting; IMO, the (free) VisualSVN Server is unbeatable; a breeze to install (next/next/next...) - and it can use your domain accounts for access (rather than a separate user database).
Marc Gravell
2009-06-04 09:16:00
I have used the migration tool, Although it's slow it will take a VSS path (which could be the root of the repository) and create a copy in SVN with all the revision history kept intact!
OneSHOT
2009-06-04 09:20:07
It highly depends on the size of the development team. TFS is overkill for small groups (1-3 people).
TFM
2009-06-04 09:48:05
@Kent: More a case of: TFS is overkill for source control *only*. Makes more sense if you use reporting/task tracking/... as well.
Richard
2009-06-04 10:59:47
I agree with Richard...TFS is great if you wan´t more than just source control (even though it has a great source control system that can handle "upgrades" from VSS). :-)
Johan Leino
2009-06-06 14:25:21
+2
A:
I am using Plastic SCM Professional for a while now and it really keeps me going. It has Visual Studio IDE integration and an importer for VSS.
Joop
2009-06-04 09:29:07
A:
svn is bad idea. most big teams already migrate from them.
I prefer GNU Bazaar and git. Monotone also is good choice but I do not know which of them compatible with Visual studio
vitaly.v.ch
2009-06-04 09:42:09