In my previous post , I discussed using ServerSyncProviderProxy with ChannelFactory<T> , and explained how you can get up and running with that combination. While the described modification is definitely necessary, there's at least one other caveat...

Sync Services for ADO.NET 2.0 allows a proper n-tier architecture where you can synchronize a client with a back-end data store via a web service. To do this, your web service must expose a simple interface consisting of four operations. As described...