INotifyingChangeApplierTarget2::SaveConstraintConflict Method
When overridden in a derived class, saves information about items that are involved in a constraint conflict.
Assembly: Microsoft.Synchronization (in Microsoft.Synchronization.dll)
void SaveConstraintConflict( ItemChange^ conflictingChange, SyncId^ conflictingItemId, ConstraintConflictReason reason, Object^ conflictingChangeData, SyncKnowledge^ conflictingChangeKnowledge, bool temporary )
Parameters
- conflictingChange
- Type: Microsoft.Synchronization::ItemChange
The item metadata for the conflicting change from the source provider.
- conflictingItemId
- Type: Microsoft.Synchronization::SyncId
The item ID of the item in the destination replica that conflicts with the item specified by conflictingChange.
- reason
- Type: Microsoft.Synchronization::ConstraintConflictReason
The reason the conflict occurred.
- 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.
- temporary
- Type: System::Boolean
true if this is a temporary conflict. Otherwise, false.
The following example shows how to save a temporary constraint conflict by using a MemoryConflictLog object.
public void SaveConstraintConflict(ItemChange conflictingChange, SyncId conflictingItemId, ConstraintConflictReason reason, object conflictingChangeData, SyncKnowledge conflictingChangeKnowledge, bool temporary) { if (!temporary) { // The in-memory conflict log is used, so if a non-temporary conflict is saved, it's // an error. throw new NotImplementedException("SaveConstraintConflict can only save temporary conflicts."); } else { // For temporary conflicts, just pass on the data and let the conflict log handle it. _memConflictLog.SaveConstraintConflict(conflictingChange, conflictingItemId, reason, conflictingChangeData, conflictingChangeKnowledge, temporary); } }
Show: