What are detected changes in tfs vs 'changes'

Question

Hello,
I've done a lot of changes in our tfs collection like creating different branches and renaming/moving stuff, and change our primary workspace from server to local (vs2013).
After checking in EVERYTHING from inside VS, when I'm issuing the command 'tf status', it returns a lot of changes, and the final line tels me "0 change(s), 3858 detected change(s)"   (every change is an 'add' type) . I've never seen
that. what does it mean, that difference betwee 'changes' and 'detected changes' ? When I check from pending changes from VS it shows ZERO changes.
Also, I've seen that 'tf status' has a toogle '[/nodetect]' that our beloved docs at msdn do not explain, they only mention it (https://msdn.microsoft.com/en-us/library/9s5ae285.aspx)... What's the point for that option ?
Thanks in advance,
Roger Tranchez

Answer 1

Hi Roger,
take a look at this blog post (http://blogs.msdn.com/b/phkelley/archive/2013/05/29/server-workspaces-vs-local-workspaces.aspx)
While edits in a local workspace can be pended implicitly just by editing the file, adds and deletes still must be explicitly pended. However, TFS version control’s workspace scanner also detects new files which are ‘candidates’ for addition, and missing
files and folders which are candidates for deletion. The Team Explorer’s Pending Changes Page has a link which shows the number of detected adds and deletes, and provides a link to the Promote Candidate Changes dialog which can be used to pend ‘real’ adds
or deletes on these items. This is called “promoting” the candidate adds and/or deletes – because they become real pending changes.
Detect Changes comes from local Workspace.
Regards,
Daniel