Fine adding but some things are ruining the experience: - performance. It is SLOW. Slower than any diff/review tool that I've ever used. Even when used with DVCS it is slow - window with list of changed files should be re-sizable - when commits to review are not sequential, tool shows changes that are not made in commits that I want to be reviewed
Our team has been using this tool with great success. We use Git and this tool integrates very nicely with it. It has great features such as the ability to leave review comments directly in the code being reviewed, when re-work is needed the tool handles subsequent revisions very nicely, the use of VS diff tool, etc. This tool handles revisions based on commits and not shelve sets, so it feels natural to work with it in a feature branch work flow. The whole experience is great, no need to leave the IDE. Very easy to install and get up and running and very low maintenance. We started with the free version and then purchased the very affordable license. Everyone is very happy with this tool.
This is deceptively advertised as a 'free' extension when really it is just crippleware and a complete waste of time. By all means make a profit from your work but the bait-and-switch nonsense has to stop.
We were looking for an alternative to the Premium+ code review features in VS as we have a professional license. We installed the free trial and 3 days later purchased a full license. It does everything we need it to do for code reviews and has a reporting tool. It is definitely worth the license fee and a much better price than upgrading our Pro subscription. The functionality for code reviews is great, especially the ability to comment on specific lines of code.
Definitely give the free trial a try. You won't be disappointed. Don't forget to vote and submit to their UserVoice too. It's still being actively developed so the features are only going to get better.
Unfortunately Review Assistant does not generate any reports presently. Please, vote for this suggestion at UserVoice in order for us to create a list of features that are most needed by our users: http://devart.uservoice.com/forums/145340-review-assistant/suggestions/3478370-please-add-metrics-and-reporting You can as well suggest to expand the limit of users in the free version and this suggestion will surely be considered.
We used Review Assistant on a trial basis with a small team and immediately purchased a license for the whole company when it was over. With Review Assistant, you can have code review for a tiny fraction of the cost to outfit your entire company with Premium+ licenses for this essential ability. I don't know why MS decided to require Premium+ to get code review, but this definitely fills the void. Great product. Simple setup. I am excited to see what comes in future releases.
Hello Bryan, we would like to place your feedback on our website, can you please contact us via the email - marinanatdevartdotcom , so that we could settle all the details. Sorry for contacting you this way, but unfortunately we haven't found your contact information.
We setup the review assistant up to work with a small set of developers. At first there seem to be problems with the search functionality but now it seems fine. I do not know if it was fixed or an environment problem. In either case it resolved a big issue I was having with having with the tool.
Combined with code compare and running review assistent on the tfs server, it provides a good way to share code and comments amount our team. For us it would be nice if it provided the ability to print and store a report on the review. For example: The report could list moderator, author, changeset reviewed, files changed, review comments and defects. However, I understand that this is beyond the scope of the tool.
We had been using the code review tool with TFS2012 and just upgraded. Now after upgrading none of us are able to login to TFS at the Projects tab, 'credentials...' option. Is this a known bug or something unique to us?
We have a similar support request. If this request is yours, please, wait and our team will get in touch with you shortly.
If it's not, could you please fill this form and describe an issue in detail? - http://www.devart.com/company/contactform.html?product=review-assistant
Thank you for the feedback. Our team plans to significantly change notification system of Review Assistant.
For now, you can off the auto refresh and make it manually, so the pop-up window will not appear at all.
Review Assistant is able to integrate with Git or TFS repositories, so the answer is Yes, you can use Review Assistant in Visual Studio Online. Read how to do this:
- with Git: http://www.devart.com/review-assistant/docs/index.html?gitrepositoryintegrationsetup.html
- with TFS: http://www.devart.com/review-assistant/docs/index.html?tfs_repository_integration_setup.html
I cannot connect to our TFS Server 2012 when trying to create a project in Review Assistant. Below is my entry for my Project in Review Assistent:
Remote Directory: $/Dev/TestCodeReview
Working Directory: C:/Dev/TestCodeReview
Below is the Error:
TF31002: Unable to connect to this Team Foundation Server: http://sgdctfs:8080/tfs.
Team Foundation Server Url: http://sgdctfs:8080/tfs.
Possible reasons for failure include:
- The name, port number, or protocol for the Team Foundation Server is incorrect.
- The Team Foundation Server is offline.
- The password has expired or is incorrect.
Technical information (for administrator):
The remote server returned an error: (404) Not Found.
What could be the reason. I am trying to convince my team 160 developers to make use of your tool. Please help.
I am evaluating your tool, trying to decide what the best code review process for our team might be. When I start Visual Studio 2012, I've been getting a notification to update from 220.127.116.11 to 1.2.35. However, this notification has been freezing, and I have to End Task on it. Thankfully, I haven't had to End Task on Visual Studio, but it did take a bit to figure out what was going on, since the notification wasn't visible when I tried to switch back to Visual Studio, from another window.
Since I've had to put off my evaluation for a few days, I haven't cared about the update, but I'm going to go ahead and update it, now. I'm frustrated by the issue, though, so I wanted to be sure to report it. (I can't recall if I finished writing and sending the email to the address listed on your web site)
But, I'm also wondering why you're going around the built in update process within Visual Studio? Is there a good reason for it? This isn't really something I'm eager to pass on to my team, because it can get quite frustrating, if you're not expecting the issue, or if you don't know that you need to use Task Manager to get around it. Even when I kept the Visual Studio window focused, I wasn't able to click on the update notification to respond to it, and I've only been able to update by ending task, and then once Visual Studio has fully loaded I use the menu to get to the update.
Getting access issues of all sort, if you try to access as a client it just does not work.
1. My developers are only getting error: "Version Control Access Error TF30063", which is false because when the go to "TeamExplorer" -> "Connect to Team Project" they can surely see "DefaultCollection" with all the available projects.
2. Our project besides the TFS repository has a SVN repository, this time if any developer opens a solution under the repository, then opens any given class and try to "Add Review Comment" they get "Cannot add comment to this document. This file doesn't belong to any repository of the current Review Assistant Project"...
If I do the same operations from the machine where the server is hosted, these problems does not occur.
1. This error generally happens when you enter incorrect credentials. Your problem may be be solved if you use the "Use Windows authentication" option for TFS connection.
2. Please, carefully check the Review Assistant working directory option. Maybe, you have them in one place on the server, but your developers have them in another one. This option can be configured separately for each developer.
When i try use the "Add Review Comment" a receive the follow message error:
"Cannot add comment to this document.
This file doesn't belong to any repository of the current Review Assistant Project"
The type of my repositorie is Custom.
You may be misled that Review Assistant allows you to add a file to review, which does not belong to the repositories folder - it is a minor bug and it will be fixed in the next version. Review Assistant allows to add comments only for files, that are within the repository of review that you choose in Code Review Board or within any repository of the project in the case when you choose ad-hoc comments. If you see another behavior, please, let us know.
When selecting multiple changesets from TFS for a review from an author where the changesets aren't necessarily in sequence (i.e. some other people checked in between some of the changesets) Review Assistant currently seems to include all the changes from the other people who checked in as well. The only way to get around this is then to manually delete all the other files which is obviously a great pain.
My biggest problem with this tool is that there seems to be only limited search capacity. My first issue is that the keyword search does not seem to work as advertised. When I type in a key word all my reviews disappear even when there is clearly a match. The search on review id works as long as you know your id but it also means all searches enterred starting with a numeric value are interpreted as a review id even when you are intending to search on a changeset value. My biggest problem is that I cannot search on changeset (revision) values. This is a big deal for our process which requires review records for each changeset submitted.
In the latest version of Review Assistant (1.0.26) we added search by changeset numbers and by name of review participant.
As for the reports, feel free to add this improvement at http://devart.uservoice.com/forums/145340-review-assistant/. If it gets enough votes, we will implement it in one of the next versions.