TFS commits unchanged files

Question

We\'re using MS Visual Studio 2008.

TFS seems to take into account the creation date of a file or something, to determine whether the files should be committed.

Answer 1

When you actually perform the check-in of the file, have a look at the changeset that actually is created in the history view. Normally TFS will check the contents of the files uploaded and will only include a file in the changeset if the MD5 hash of the file is different to the last version that was in version control.

Is this not what you see? Do you have multiple versions of the same file that are identical in content? If so - what extension do the files have? .XML or something else?