Priority, ChangeSet association and Saved settings are new in TeamReview

A new release of TeamReview has been published - and this is a fun one. For the first time I wasn't the only coder. Our newest team member both added a bunch of great new inspiration to the release and cleaned up a lot of my perpetual hacking-just-to-make-it-work, and TeamReview is much better off for it.

As I said - we have some very fun stuff for you to try out-

1. You can now associate code review responses directly with a change-set
2. A priority can be assigned to your code review feedback - and - this is backwards compatible to the client - you can have an old client and a new Work Item Type
3. You can choose individual code review responses in the Code Review Replay window
4. TeamReview has it's own output window to help you remember what you've done in your code review activity
5. The default values for the size and location of the New Code Review Response window are persisted between VS.Net sessions
6. The last used values for the New Code Review Response fields are saved per Team Project and are persisted between VS.Net sessions
7. Thanks to Libaty we have an optional Japanese language Work Item Type definition for Code Review Response
8. A handful of bug fixes

Release 1.1.0 has the full detail on these new features and the links to download the latest version of TeamReview