MSDeploy only deploys files that it has deemed as having changed. By default, this involves comparing the files' Last Modified timestamps. If your source control / build process causes these to be updated, but they will always be updated.
There is an alternative. If you pass -useCheckSum
to the command line, it will compare the contents of the files (via a checksum).
It would be my preference to fix the issue that's causing your last modified dates to change, though, as -useCheckSum
is obviously going to be slower.