Context menu shortcuts show up but don't work in "All Included Changes" view of Team Explorer

Context menu shortcuts show up but don't work in "All Included Changes" view of Team Explorer by NIGregR

Active

Type:	Bug
ID:	778571
Opened:	2/5/2013 7:04:07 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

In Visual Studio 2012 Ultimate I assigned a shortcut key to TeamFoundationContextMenus.PendingChangesPageChangesToInclude.Tfs.ContextPendingChangesPageCompareWithWorkspaceVersion. This works fine when I select a file in the Pending Changes view of the Team Explorer. It even works whether the selected file in in the "Included Changes" section or the "Excluded Changes" section. However when I have a lot of files in a change, these views do not show all of them. I must go to the "All Included Changes" view. In this view although the context menu on a file does show my assigned key on its "Compare with Workspace Version" menu item, the shortcut key does nothing.

This is similar to the report below but it seems to be talking about the Pending Changes view.
http://connect.microsoft.com/VisualStudio/feedback/details/759866/team-explorer-pending-changes-context-menus-ignore-shortcut-keys#details

Details (expand)

Visual Studio 2012 Update 2

Assign a shortcut key in the Team Explorer scope to TeamFoundationContextMenus.PendingChangesPageChangesToInclude.Tfs.ContextPendingChangesPageCompareWithWorkspaceVersion.
Check out enough files that the Pending Changes view will not show all of them and shows the "Go to All Changes" option. (somewhere around 200 files)
Go to that view.
Verify that the context menu on a file still shows the assigned shortcut key.
Select a file and press the shortcut key.

English

Windows 8

English

Nothing.

The compare should be invoked.

0 attachments

Posted by NIGregR on 5/8/2013 at 9:29 AM

I have verified that this was not fixed in Update 2 which was the next quarterly update. The "All Included Changes" view still does not honor shortcut keys. Either the description of when the fix was coming was inexact or you misunderstood the problem.

Posted by Microsoft on 2/6/2013 at 2:12 PM

Hello,

Thank you for the feedback. We've actually fixed this internally and you should see this fix in the next quarterly update. Please let us know if you hit any other issues.

Thanks,
Taylor
TFS Version Control

Posted by Microsoft on 2/5/2013 at 11:43 PM

Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.

Posted by Microsoft on 2/5/2013 at 7:50 AM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)