I'm aware that there are a lot of questions on SO with similar content, but I can assure you that I have read the most of them completely with answers and comments.
My situation is slightly different in means that our company is mostly Java-oriented and thus the standard ALM tool set is already set up:
- SVN for Source Control
- Jira for task/issue tracking
- Jenkins for continuous integration
Now, I run a team of .NET developers and we need to set up something similar for our dev process and the discussion is whether to go separately with TFS or to reuse the existing infrastructure and plug in the .NET projects there as well.
I realize that the biggest pro-TFS argument is good integration with VS, but with our current setup I am wondering if there are some good arguments for not using TFS at all.
Best Answer
As someone who is using both SVN and TFS for .NET developmnet, here are the biggest reasons to choose SVN over TFS in my opinion:
Bottom line, I've found SVN to be cheaper to operate, more stable, and definitely more mature.