SyncConflict Class
Represents a synchronization conflict at the row level.
Inheritance Hierarchy
System.Object
Microsoft.Synchronization.Data.SyncConflict
Namespace: Microsoft.Synchronization.Data
Assembly: Microsoft.Synchronization.Data (in Microsoft.Synchronization.Data.dll)
Syntax
'Declaration
<SerializableAttribute> _
Public Class SyncConflict
'Usage
Dim instance As SyncConflict
[SerializableAttribute]
public class SyncConflict
[SerializableAttribute]
public ref class SyncConflict
[<SerializableAttribute>]
type SyncConflict = class end
public class SyncConflict
The SyncConflict type exposes the following members.
Constructors
Name | Description | |
---|---|---|
![]() |
SyncConflict() | Initializes a new instance of the SyncConflict class by using default values. |
![]() |
SyncConflict(ConflictType, SyncStage) | Initializes a new instance of the SyncConflict class by using conflict type and conflict stage parameters. |
Top
Properties
Name | Description | |
---|---|---|
![]() |
ClientChange | Gets or sets the DataTable object that contains the conflicting rows from the client database. |
![]() |
ConflictType | Gets or sets the ConflictType enumeration value that represents the type of synchronization conflict. |
![]() |
ErrorMessage | Gets or sets the error message if ConflictType is set to ErrorsOccurred. |
![]() |
ServerChange | Gets or sets the DataTable object that contains the conflicting rows from the server database. |
![]() |
SyncStage | Gets or sets the SyncStage enumeration value that represents the synchronization stage during which the conflict occurred. |
Top
Methods
Name | Description | |
---|---|---|
![]() |
Equals | (Inherited from Object.) |
![]() |
Finalize | (Inherited from Object.) |
![]() |
GetHashCode | (Inherited from Object.) |
![]() |
GetType | (Inherited from Object.) |
![]() |
MemberwiseClone | (Inherited from Object.) |
![]() |
ToString | (Inherited from Object.) |
Top
Remarks
For conflicts encountered during synchronization, the data from each conflicting row is stored in a SyncConflict collection. It is possible for this collection to grow large enough to cause an out of memory error in the following situations:
There are a large number of conflicting rows. Consider synchronizing a smaller number of rows in each session, or limit the number of conflicts by updating a particular row at only one node.
The conflicting rows contain columns with large data types. Consider not including the columns with large data types in the set of columns that is synchronized. For more information, see How to: Filter Rows and Columns.
Examples
For an example of how to handle conflicts, see How to: Handle Data Conflicts and Errors.
Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.