Anyone can upload a patch. Patches are evaluated by project team members and either Applied or Declined.
1-5 of 5Patches
< Previous 1 Next >
Being evaluated
|
121 |
Jul 6 2007 at
4:58 PM |
JBBrown |
Fix for 2508
|
2508
|
Download
|
Being evaluated
|
111 |
Jul 3 2007 at
9:51 PM |
JBBrown |
Resolve Issue ID #2260 - Add Extensions to Replay Chain
|
|
Download
|
Being evaluated
|
110 |
Jul 3 2007 at
8:44 PM |
JBBrown |
Resolve Issue #2262 - Line Numbers are incorrect when after a collapsed definition
|
2262
|
Download
|
Being evaluated
|
88 |
Jun 25 2007 at
6:05 PM |
JBBrown |
*. Added fields in field mappings for Code Project, Code Namespace, Code Class, Code Member, Start Line, and End Line
*. Included new Code Review.wit and Code Review Item.wit with new layout to accommodate new fields. Many of the new fields are reportable and can be queried upon.
*. Added close button to field mappings form
*. Added Configuration Upgrade chain of responsibility pattern to fix problems introduced in patch 38 and to update configs and to update for this patch.
*. Added Code Review Replay Tool window. This window is used to see all the submitted code review items attached to a code review. The window allows the cycling through of the attached items, and re-opens the document for each item, re-highlights the line numbers of the item and displays the suggested resolution in the tool window.
*. Added Replay chain of responsibility to allow for future extension of the re-highlighting of review items to be less fragile if changes have occurred between the times the review was submitted and replayed.
I'll be posting something on my blog with a more detailed description and screenshots later on:
http://jb-brown.blogspot.com
|
|
Download
|
Being evaluated
|
38 |
Jun 3 2007 at
6:46 AM |
JBBrown |
here's a list of changes I made:
1. I changed the Delete button in the Settings form to be context sensitive and only delete the highlighted node and it's children.
2. I added a "Links Queries" section to the Settings. The potential values are the Project's Team Queries, and one of those queries
should be added and set as the default for each project.
3. The Work Items in the selected "Links Queries" are displayed during work item submission. There's a drop down and a text box to see the work item's description. The selected item in the drop down will be linked to the code review item that is submitted.
4. The user most recently assigned a submitted Code Review item is the default value for the "Assign To" drop down on subsequent submissions.
5. The Associated Work Item most recently used when submitting a Code Review item is the default value on subsequen submissions.
6. The Description field is prepoulated with the name of the Code Element that contained the highlighting, and the line numbers
that were highlighted. Review this in detail, it seems to have some short comings. Everythign I accomplished is with gratitude
to this blog post from Rick Strahl http://west-wind.com/weblog/posts/3405.aspx since I simply copied his example.
7. The file that was highlighted within is attached to the work item being submitted and is accessible form the Attachments control of the work item.
8. I included two work item type XML files in the zip, "Code Review.xml" and "Code Review Item.xml." The Code Review type would
be used to request a code review to happen, and the Code Review Item would be the type that is mapped to with the AddIn. Using these
Types along with a Team Query for "All open Code Reviews" really shows off the new features of the AddIn.
|
|
Download
|
1-5 of 5Patches
< Previous 1 Next >