Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
The Configuration.ConflictResolutionPolicy in FileSyncProvider RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hello *,

    does it make sense to set some value to Configuration.ConflictResolutionPolicy property of FileSyncProvider? I've tested this today and it looks, that it has no effect and provider is doing some careful renames etc. to handle conflicts.

    Thanks for reply. JC
    • Moved by Max Wang_1983 Thursday, April 21, 2011 10:21 PM forum consolidation (From:SyncFx - Technical Discussion [ReadOnly])
    Wednesday, November 28, 2007 12:12 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Jiri,

     

    As you've noticed currently FileSyncProvider has its own conflict resolution policies and does not support specifying custom ones. While technically you could set the property to something it is strongly recommended that you don't as it will mess with FSP's internal conflict resolution and may result in non-optimal handling of conflicts. We're considering adding custom/extensible conflict resolution policies to FSP but it's not something we've been able to fit into the current release. For now please don't set the property to anything. Note that the same is true in native code where the application should specify CRP_NONE in the ISyncSession.Start call if it's using native FSP providers.

     

    thanks,

    Lukasz Gwozdz

    Thursday, November 29, 2007 8:53 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Jiri,

     

    As you've noticed currently FileSyncProvider has its own conflict resolution policies and does not support specifying custom ones. While technically you could set the property to something it is strongly recommended that you don't as it will mess with FSP's internal conflict resolution and may result in non-optimal handling of conflicts. We're considering adding custom/extensible conflict resolution policies to FSP but it's not something we've been able to fit into the current release. For now please don't set the property to anything. Note that the same is true in native code where the application should specify CRP_NONE in the ISyncSession.Start call if it's using native FSP providers.

     

    thanks,

    Lukasz Gwozdz

    Thursday, November 29, 2007 8:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for explanation.

     

    JC

    Sunday, December 2, 2007 11:03 PM