We are planning to use Team Foundation Server, but we need to decide whether to use the Visual Studio Team Foundation Server source control plugin or the VisualSVN source control plugin inside Visual Studio.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
We are planning to use Team Foundation Server, but we need to decide whether to use the Visual Studio Team Foundation Server source control plugin or the VisualSVN source control plugin inside Visual Studio.
If you plan to use TFS, go for the TFS Source Control, feature-wise it’s as good as SVN if not better (history is managed the same way, branches too, perfs are better).
But where you get benefits in the TFS Source Control compared with SVN is in the integration with Work Item and the rest of TFS.
When you work on a given Task Work Item you can associate your check-ins (then changeset) with the Task, and it’s very powerful because you’ll have a more project based view than code view.
The Source Control of TFS is the lowest layer of the ALM Solution, you can avoid using it, but you’ll lose a lot of things (integration with Work Item, Continuous Integration, Reports, etc.)