Contents
SharePoint client object model (CSOM) provides lots of APIs to retrieve, update, and manage data in SharePoint. There are limitations to what can be done client-side compared to server-side, say for example: You cannot access the FARM level properties, you can get/set only the properties at the web application level.
The SharePointOnlineCredentialstakes in two parameters which are your Login Email for your Office 365 SharePoint site and your password in the SecureStringformat. You can grab all the required SharePoint 2013 client assemblies from here: http://www.microsoft.com/en-us/download/details.aspx?id=35585
How to authenticate a.NET client object model?
The process of authenticating the .NET Client Object Model in SharePoint Online has been greatly simplified in the 2013 version. Earlier (2010), you had to go through a lot of steps for doing the exact same thing.
Where can I find the Managed Client object model?
The Managed object model can be used to create .NET applications that run on Windows operating systems that aren’t phones or SharePoint servers. The managed client object model dlls are found inside the ISAPI folder ( %ProgramFiles%\\Common Files\\Microsoft Shared\\web server extensions\\15\\ISAPI). Microsoft.SharePoint.Client.dll
We will also see more than 25+ examples in the SharePoint client object model. Apart from SharePoint CSOM examples, we will discuss on CRUD operations in CSOM. Here, we will focus purely on the SharePoint .Net client object model.
Do you need a development machine to use SharePoint?
No SharePoint installation is required in the development machine. Only the Client DLL’s are required. No Compilation required as required on the server-side, NO IISRESET required. There are 4 types of SharePoint client object model available to work with SharePoint 2013/2016/2010 or SharePoint Online. .Net client object model (C#.Net)