For Windows developers, What types of source control do you use with Visual Studio projects?

VSS (Visual Source Safe)
TFS (Team Foundation Server)
CVS and/or Subversion
Mostly use VSS/TFS, some use of CVS/SVN
Mostly use CVS/SVN, some use of VSS/TFS
Other system(s)
Do not use source control
Do not use Visual Studio

Author Topic: Poll: Visual Studio and Source Control  (Read 14526 times)


  • New Community Member
  • Posts: 1
  • Hero Points: 0
Re: Poll: Visual Studio and Source Control
« Reply #15 on: September 27, 2007, 10:40:01 pm »
Perforce.  Single license free version.  I never actually use it from within Visual Studio (or SlickEdit, for that matter) source code control integration in Visual Studio adds stuff to your .sln and/or .xproj files which end up causing more problems than it is worth.  On top of that, for both Visual Studio and SlickEdit, whenever I have used integrated scc it slows down project open way too much.  I am happy using the command-line or gui tools with whatever scc I use and keeping my development environments clean.