SynchronizationExeption when trying to get items from Azure

[mema]

I have an Mobile Service with 0 items. When I start my demo app and do a 

await MainViewModel.Instance.Context.SynchronizeAsync();

I get an exeption with the following message

Method not found: 'Newtonsoft.Json.Serialization.ITraceWriter Newtonsoft.Json.JsonSerializerSettings.get_TraceWriter()'.

Any hints as to why?? Am I referencing a wrong version of Newtonsoft.Json (Currently it is Version 4.5.0.0, which were added by template)

[Deyan]

Hello Mikkel,

Thanks for writing.

This looks like a problem caused by mismatched assembly versions. Would it be possible that you send us a zip with your project or simply let us know which steps to take so that we can reproduce the scenario on our side and see how to fix it?

Regards,
Deyan
Telerik

 

 

[Mikkel]

Hi Deyan

I seem to have fixed the issue. I looks like the 'Newtonsoft.Json.dll' supplied in the x86 folder is incompatible.
I added the newest Json.net via nuget, but I also had to change the hintpath for the assembly in the .csproj file.

Also following the guide at http://www.telerik.com/help/windows-phone/radcontrols-cloud-synchronization-gettingstarted-azure.html did not seem to work. I got timeouts all the time. It seems you expect a SynchronizationId column, which is not present, when no items have been created yet.
So the method 'await MainViewModel.Instance.Context.SynchronizeAsync();' kept throwing a SynchronizationException until I added this column.

Mikkel

[Deyan]

Hi Mikkel,

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:
- API
- functionality
- performance, etc.

Since we are actively developing it now, your experience is important to us.

Thanks for your time!

Regards,
Deyan
Telerik