Team Explorer (Pending changes view) hides actual pending changes in a confusing way - by Andreas Presthammer

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 781972 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/23/2013 5:03:28 AM
Access Restriction Public


When I have a changeset that include many files, the Pending Changes view in the Team Explorer switches into a different mode where is only displays a subset of the actual pending changes. I find this disturbing and confusing in itself and really dont like this behavior, but this bug-report isn't so much about what is hides, as it is about what it displays. (I know I can click the "Go to All Changes" button to actually show all).

If you have the following pending changes:
Directory A has 300 files with pending changes.
Directory B has 5 files with pending changes.

When you review the pending changes view it will show you something like the following subset:.
Directory A

It will NOT display that Directory B has any changes to it. If I know that I want to check in all the changes to directory A,but not the changes to Directory B, then this view would suggest that you will only commit changes to Directory A, but in fact you will also be commiting to Directory B.

I find this terribly confusing. This would NOT be a problem if you didn't not do any "mode switching" in the pending changes view, and always display all the changes.
Sign in to post a comment.
Posted by Deon [MSFT] on 4/29/2014 at 12:29 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from:
Posted by Microsoft on 3/25/2013 at 12:08 PM
Thanks for reporting this issue with the Pending Changes experience. We have heard a lot of feedback from users on this issue, and we have fixed it. You will see the new experience in the next major VS release.

Posted by Microsoft on 3/25/2013 at 1:57 AM
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 3/23/2013 at 5:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(