When will it support SharePoint 2013 client object model

Sep 3, 2013 at 10:53 AM
Seems like it works with only SharePoint 14 and throw assembly not found exception when used in SharePoint 2013 App.

Try rebuilding the code using updated DLL but it is not working. Any Idea?
Coordinator
Sep 3, 2013 at 9:26 PM
youranupama hi,
what kind of app you mean here? Are you talking about classical Sharepoint app (which according to MS now should be basic way for customizing Sharepoint), or some general app (e.g. console application), which uses managed client object model? In the last case you may try to add assembly binding redirect for Microsoft.SharePoint.Client.dll from version 14.0.0.0 to 15.0.0.0 to app.config, like shown e.g. here http://sadomovalex.blogspot.com/2011/09/assembly-binding-redirect-in-sharepoint.html (i.e. using assemblyBinding element).
Sep 4, 2013 at 5:33 AM
Hello Sadomovalex,

Thanks for the reply and let me compliment you on the library you have created.

I wanted to use the client side assembly in SharePoint 2013-Office365 provider hosted app. Since the client assembly was build on .Net framework 3.5 and SharePoint 14, I was not able to call the methods.

You assembly redirection on console app might work but for now, I have rebuild the source code using SharePoint 15 and .Net framework 4.5 and so far it is working fine.

So you might just put up the steps to use the same assembly for SharePoint 2013 apps without rebuilding and upgrading framework.

Hope It make sense.

Anupama


Coordinator
Sep 4, 2013 at 8:37 AM
Anupama hi,
thanks for sharing your steps. I added it to future development list (https://camlex.codeplex.com/wikipage?title=Future%20improvements) and will check how to do it when will finish other features which are under development. If assembly binding redirect will work, probably will write instructions somewhere.
Sep 4, 2013 at 9:37 AM
Great. Thanks.

Sent from my Windows Phone