MemoryConflictLog.SaveConflict Method

Saves information about a change that caused a concurrency conflict.

Namespace:  Microsoft.Synchronization
Assembly:  Microsoft.Synchronization (in Microsoft.Synchronization.dll)

Syntax

'Declaration
Public Sub SaveConflict ( _
    conflictingChange As ItemChange, _
    conflictingChangeData As Object, _
    conflictingChangeKnowledge As SyncKnowledge _
)
'Usage
Dim instance As MemoryConflictLog
Dim conflictingChange As ItemChange
Dim conflictingChangeData As Object
Dim conflictingChangeKnowledge As SyncKnowledge

instance.SaveConflict(conflictingChange, _
    conflictingChangeData, conflictingChangeKnowledge)

public void SaveConflict(
    ItemChange conflictingChange,
    Object conflictingChangeData,
    SyncKnowledge conflictingChangeKnowledge
)

public:
virtual void SaveConflict(
    ItemChange^ conflictingChange, 
    Object^ conflictingChangeData, 
    SyncKnowledge^ conflictingChangeKnowledge
) sealed

abstract SaveConflict : 
        conflictingChange:ItemChange * 
        conflictingChangeData:Object * 
        conflictingChangeKnowledge:SyncKnowledge -> unit 
override SaveConflict : 
        conflictingChange:ItemChange * 
        conflictingChangeData:Object * 
        conflictingChangeKnowledge:SyncKnowledge -> unit 

public final function SaveConflict(
    conflictingChange : ItemChange, 
    conflictingChangeData : Object, 
    conflictingChangeKnowledge : SyncKnowledge
)

Parameters

• conflictingChange
  Type: Microsoft.Synchronization.ItemChange
  The item metadata for the conflicting change.

• conflictingChangeData
  Type: System.Object
  The item data for the conflicting change.

• conflictingChangeKnowledge
  Type: Microsoft.Synchronization.SyncKnowledge
  The knowledge to be learned if this change is applied. This must be saved with the change.

Implements

IConflictLogWriter.SaveConflict(ItemChange, Object, SyncKnowledge)

Exceptions

Exception	Condition
ArgumentNullException	conflictingChange or conflictingChangeKnowledge is a null reference (Nothing in Visual Basic).

Remarks

The conflict is saved to the in-memory conflict log. To save the conflict after synchronization completes, call Persist.

See Also

Reference

MemoryConflictLog Class

Microsoft.Synchronization Namespace