Thanks for writing.
Yes, I myself have been able to identify the reason for the error with the Newtonsoft version. Good that you've managed to resolve that on your side. I will see why this happens by default and will make sure to address it in our codebase.
There are a couple of system properties that aid the synchronization algorithms. The datetime properties, as well as the SynchronizationId
property. I don't recall having issues similar the the one you mention but I will make sure to replay the scenario.
I will strongly encourage you to share with us any feedback you might have regarding this component in terms of:
- performance, etc.
Since we are actively developing it now, your experience is important to us.
Thanks for your time!
DevCraft Q1'14 is here! Watch the online conference to see how this release solves your top-5 .NET challenges. Watch on demand now.