Export (0) Print
Expand All

DbSyncConflict Class

Represents a synchronization conflict at the row level.

System.Object
  Microsoft.Synchronization.Data.DbSyncConflict

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

[SerializableAttribute]
public class DbSyncConflict

The DbSyncConflict type exposes the following members.

  NameDescription
Public methodDbSyncConflict()Initializes a new instance of the DbSyncConflict class by using default values.
Public methodDbSyncConflict(DbConflictType, DbSyncStage)Initializes a new instance of the DbSyncConflict class by using conflict type and conflict stage parameters.
Top

  NameDescription
Public propertyErrorMessageGets or sets the error message that is returned when DbConflictType is set to ErrorsOccurred.
Public propertyLocalChangeGets the DataTable object that contains the conflicting rows from the local database.
Public propertyRemoteChangeGets the DataTable object that contains the conflicting rows from the remote database.
Public propertyStageGets or sets the DbSyncStage enumeration value that represents the synchronization stage during which the conflict occurred.
Public propertyTypeGets or sets the DbConflictType enumeration value that represents the type of synchronization conflict.
Top

  NameDescription
Public methodEquals (Inherited from Object.)
Protected methodFinalize (Inherited from Object.)
Public methodGetHashCode (Inherited from Object.)
Public methodGetType (Inherited from Object.)
Protected methodMemberwiseClone (Inherited from Object.)
Public methodToString (Inherited from Object.)
Top

In Sync Framework, conflicts and errors are detected at the level of the row. A row is in conflict when it has been changed at more than one node between synchronizations. Errors that occur during synchronization typically involve a constraint violation, such as a duplicate primary key. Applications should be designed to avoid conflicts if they can, because conflict detection and resolution introduce additional complexity, processing, and network traffic. 

If a row cannot be applied during synchronization, this is usually because either an error or a data conflict occurred. In both cases, the ApplyChangeFailed event is raised. Conflict and error resolution should be handled in response to this event.

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.
Show:
© 2015 Microsoft