Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.
To write .NET synchronization logic, you require knowledge of MobiLink events, some knowledge of .NET, and familiarity with the MobiLink server API for .NET.
For a complete description of the API, see MobiLink server API for .NET reference.
.NET synchronization logic can be used to maintain state information, and implement logic around the upload and download events. For example, a begin_synchronization script written in .NET could store the MobiLink user name in a variable. Scripts called later in the synchronization process can access this variable. Also, you can use .NET to access rows in the consolidated database, before or after they are committed.
Using .NET also reduces dependence on the consolidated database. Behavior is affected less by upgrading the consolidated database to a new version or switching to a different database management system.
You can use MobiLink direct row handling to communicate remote data to any central data source, application, or web service. Direct row handling uses special classes in the MobiLink server APIs for Java or .NET for direct access to synchronized data.
See Direct Row Handling.
SQL-.NET data types
User-defined start classes
Printing information from .NET
Handling MobiLink server errors with .NET
Debugging .NET synchronization logic