CODEWITHSUNDEEP
visual-studiovisual-studio-2012tfs
StefanG
StefanG

Reputation: 1264

TFS: Show really all changes

From time to time, when I want to check in with Visual Studio (2012) my pending changes to Team Explorer, I get a strange abstract "Included Changes (x of y)" Where x is smaller than y. Even when I check in from the root directory of the solution and when I select "Show all" I can't see really all changes.

In the case below: When I set "Show Solution Changes" I see 96 of 452, when I select "Show all" I see 178 of 452. The missing files are part of the solution and common source files as the others.

Tfs_Show_All

P.S: Policy warning is irrelevant and conflicts are irrelevant to this behavior.

Upvotes: 4

Views: 3672

Answers (2)

DavidScherer
DavidScherer

Reputation: 884

This is a really old question, but I recently encountered it while searching for a similar problem and for me I was seeing files that were previously checked in show up under All Changes for a solution that didn't show up when viewing Solution Changes.

For me the only thing that fixed it was closing VS and renaming the hidden $tfs directories in my TFS folder. Upon opening VS again new $tfs directories were created and all of my issues went away.

Upvotes: 0

Obsidian Phoenix
Obsidian Phoenix

Reputation: 4155

Show All simply removes any filter you have applied using either Show Solution Changes or Custom Filter.

If you want to view all your changes, you need to use the Go to All Changes link, right next to your Show All Link. This will show you the complete list of all changes across the workspace.

It takes a little getting used to, but I actually quite like it this way. I believe the rationale behind doing it was to keep that space fairly small, so as not to push the Excluded Items list way to the bottom (Excluded Items will also behave in the same manner, I believe).

There is an extension for Visual Studio called Team Pilgrim that will give you a version of the old style pending changes window.

Another point of note is that this behaviour is no longer the case in VS2013 (1) (Thanks to StefanG for pointing this out)

Upvotes: 4

Related Questions