On the local client we are using a FileSyncProvider and on the remote server we are using an implementation of the FullEnumerationSyncProvider which stores files on Azure.
We're coming across a problem where the Sync Framework is trying to apply an update to a file because it thinks it's changed, but hasn't. I think the problem may be because of a mismatch between the timestamps on the local files and the timestamps that
the server is returning.
The ApplyingChangeEventArgs for the update that is being applied from the server to the client are:
CurrentFileData.CreationTime: 08/10/2010 15:47
CurrentFileData.LastAccessTime: 01/01/1601 00:00
CurrentFileData.LastWriteTime: 08/10/2010 15:47
CurrentFileData.Size: 169653
NewFileData.CreationTime: 08/10/2010 14:47
NewFileData.LastAccessTime: 01/01/1601 00:00
NewFileData.LastWriteTime: 08/10/2010 14:47
NewFileData.Size: 169653
So I'm assuming that the Sync Framework wants to update the file because the timestamps differ. NewFileData is coming from the server, which always stores and returns times in UTC. The client is installed with UK time, currently UTC+1.
Can anyone offer any suggestions?