1

I have a web project that should consume both On-premise Sharepoint 2010 and Sharepoint 2013.

So, we have two different versions of the following dlls :

  • Microsoft.SharePoint.Client V 14.0.0.0
  • Microsoft.SharePoint.Client.Runtime V 14.0.0.0
  • Microsoft.SharePoint.Client V 16.0.0.0
  • Microsoft.SharePoint.Client.Runtime V 16.0.0.0

Which version of dll should I safely use to consume the API from two different server versions?

1

I Just used below

Microsoft.SharePoint.Client.dll V 16.1.5026.1200
Microsoft.SharePoint.Client.Runtime.dll 16.1.5026.1200

and its working fine for SharePoint 2010,2013 and Online.

Up To my knowledge latest dll will be compatible with all.

  • Any official reference about this? – systempuntoout Jul 28 '16 at 15:08
  • I am not sure about this as I was unable to find any official documentation which says that the latest DLL are always compatible with lower versions of SharePoint, but when I practically tried the solution I was also able to update the list item in SharePoint 2010 and SharePoint 2013 with the use of V16 DLL. – Aakash Maurya Jul 29 '16 at 4:25
  • Architecture of Client Object Model for SharePoint 2010 and above are almost same. so whenever Microsoft upgrades sharepoint, it will keep backward compatibility unless and until architecture changes. – Anil Pal Jul 29 '16 at 6:30
  • True, and untrue. There will be a lot of errors with this approach when you are using methods in the .dll that are not supported for 2013, 2010 – Robert Lindgren Aug 5 '16 at 8:09
  • @RobertLindgren : Would a substitution to a newer DLL without changing the used functions be OK then? We need to update because the underlying Server is updated and does not provide .Net 2.0. – Urs Feb 3 '17 at 10:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.