Downsides of checking in files that have no changes?

Question

Regardless of whether it is a bug, that TFS forces files to be in the pending changes section, even when there are no changes, is there a downside to checking those files in?

Please note that according to this, the way to get rid of files that have no changes, would be to issue the following command with TFS power tools:

tfpt uu /noget /r 

What is the downside of checking in files that have no changes? Does it pose some sort of obstacle to the regular agile TFS workflow? Why shouldn't I check in files that have no changes?

Answer 1

From everything I've found, TFS (2017) inherently prohibits unmodified files from being checked in. If you try to force the issue, the server will reject the "changes" with the error:

All of the changes were either unmodified files or locks. The changes have been undone by the server.

If you mix changed and unchanged files in a single check in, only the modified files actually leave any record. The server undoes the "changes" to the unmodified files as if they had never been modified. The resulting changeset will only show files that were actually modified.

Answer 2

The solution that worked for me after many attempts is this: When receiving the message all of the changes were either unmodified files or locks. the changes have been undone by the server That means no change is made, Therefore the tfs rejects the change When I made a change and then I did a check in it wrote to me that it worked, In my case I did not understand why it does not save me all the changes when I run Chrome, or Explorer This is the answer- 3 steps: In the menu - Project - Properties The debug of the file I needed was on a local debug I changed to debug only enter image description here

Then I changed in solution the problematic file I had Report Project1 and then I pressed a right key I changed The access to sql that was old in TARGET SERVER VERSION

enter image description here Then I did a deploy to the file and finally worked it out