Apache Subversion vs. Review Assistant

It's a relatively simple version control system so it works great for an individual or small team (less than 10 people). But if you have a medium to large team, especially one with members distributed over a large geographic area, or one where individuals need to be able to work "offline" without access to a central server, Apache Subversion will likely not be the best choice.

Also, if you're maintaining an open-source project where outside people will be interacting with your code repository, git is probably a better choice because it's becoming the de-facto standard these days and what most developers are familiar with.

Incentivized

Combined with Code Compare and running Review Assistant on the TFS server, it provides a good way to share code and comments amount our team. It does everything we need it to do for code reviews and has a reporting tool.

• Revision control done properly - you have end to end visibility of all changes in the project.
• Conflict resolution - visually highlighting the differences helps to track down the problem.
• Being open source and very popular.
• We are using SVN hosted in our network - it is very stable, we had almost zero downtime in 4 years.
• Rollbacks are made simple and easy to use.

Incentivized

• Review Assistant does everything that I was hoping the default Visual Studio reviews would do. The iterations through accept/reject were the key winner.
• The functionality for code reviews is great, especially the ability to comment on specific lines of code.
• You don't have to leave the IDE.

• Distributed development - I've never worked in an environment where distributed development (developers widely scattered geographically) was a factor, but that's why git exists.
• Merging - Merging of code from one branch to another can be painful, especially if it's not done frequently. (On the other hand, doing merges is one of the reasons I get a nice salary, so I can't complain too much!)
• Acceptance - Let's face it, git is what "all the cool kids are using." If you've got a bunch of developers fresh out of school, they'll probably know git and not Subversion.

Incentivized

• Integration with JIRA is missing.
• Ability to search, filter and order comments.
• There is no support for Visual Studio Code.

While there are interesting alternatives, such a GIT, Subversion has been a breath of fresh air compared to its predecessors like CVS or Microsoft Source Safe (now called Team Foundation Server). Its ease of use and high adoption rate is going to keep me using this product for years to come.

Git has become the new standard of version control, with its support for distributed design. As a tool to manage and control versions, Subversion does it well, but Git is the future.

Incentivized

Microsoft provides a handy feature for code review inside the Visual Studio IDE. Review Assistant, though providing a similar code review user experience, supports work scenarios that are not covered by the Microsoft's IDE. Moreover, the version control systems support is broader in Review Assistant.

• Subversion helps us feel secure in maintaining access to all of our product code, both current and historical.
• Being free and open source makes it an even better "investment".

Incentivized

• The tool saves a huge amount of time while reviewing the code. Review Assistant supports threaded comments, so team members can discuss code without scheduled meetings.