Page 1 of 1

DLL conflict in .Net API

Posted: Mon Oct 08, 2012 4:33 am
by BenjBayfield
I have a CMS installed which uses the .Net 3.5 Framework, and already has a dependency on Newtonsoft.Json.dll

The .Net 3.5 API from ScientiaMobile also has a dependency on Newtonsoft.Json.dll, but on a newer version. As I can't install both DLLs within the application, I tried setting the ScientiaMobile .Net API within a web service, but the API relies on the HttpContext object which can't be serialized, so that won't work.

I can't get the Cloud Service to work as it stands - is there a workaround?

Re: DLL conflict in .Net API

Posted: Mon Oct 08, 2012 2:01 pm
by kamermans
We are looking into the situation for you. In the meantime, would you mind telling us which CMS you're using?

Re: DLL conflict in .Net API

Posted: Mon Oct 08, 2012 2:23 pm
by kamermans
It looks like the only practical solution is to compile our client with a different version of the JSON DLL. Can you send us the Newtonsoft.Json.dll that your CMS is using to support@[our domain name], or tell me how to obtain that DLL, so we can figure out how to proceed?

Re: DLL conflict in .Net API

Posted: Tue Oct 09, 2012 4:29 am
by BenjBayfield
Thanks - I've sent you our DLL, version 3.5.0.0

Our CMS is Sitecore version 6.5.0 on .Net 3.5

Re: DLL conflict in .Net API

Posted: Tue Oct 09, 2012 1:03 pm
by sm_support2
We created a custom build of the DLL for you, but your spam filter is bouncing us. Please advise on alternative ways to send you the DLL

Thanks