The document outlines a session by Chis O'Brien and Chis Givens focused on using Client-Side Object Model (CSOM) in PowerShell scripts with Office 365. It includes an agenda detailing CSOM overview, deployment processes, and steps for development along with references and resources for further reading. Key points include the importance of authentication and best practices in CSOM usage within SharePoint environments.

2. About Me

3. Credit for this session
http://www.sharepointnutsandbolts.com/
Chis O’Brien - MVP
Reference:
http://www.sharepointnutsandbolts.com/20
13/12/Using-CSOM-in-PowerShell-scripts-
with-Office365.html

4. Session Raffle
http://blogs.architectingconnectedsystems.
com/blogs/cjg/default.aspx
Chis Givens - MVP
Twitter: @givenscj

5. Agenda
Background CSOM Overview
Why PowerShell + CSOM
Final Thoughts &
QA
How to Start

6. “FTC to CAM – Stop creating content types and site
columns declaratively”
http://blogs.msdn.com/b/vesku/archive/2013/11/06/ftc-to-cam-stop-creating-content-
types-and-site-columns-declaratively.aspx
My Journey to PowerShell + CSOM

7. Typical CT deployment process

8. What is being recommended

10. CSOM Overview

11. How CSOM Works

12. CSOM Overview

13. • Create Context
ClientContext ctx = new ClientContext("http://intranet.contoso.com");
• Call Load and ExecuteQuery Before Accessing Value Properties
Web web = ctx.Web;
ctx.Load(web);
ctx.ExecuteQuery();
Console.WriteLine(web.Title);
How CSOM Works

15. • Local Machine
• SharePoint 2013 Environment
Steps to start developing

16. • Located at C:Program FilesCommon
Filesmicrosoft sharedWeb Server
Extensions15ISAPI
• All DLLs that starts with
Microsoft.SharePoint.Client
Local Machine

17. SharePoint Environment

18. Add reference to your DLLs

19. Authentication - SPO

20. Authentication – On-Prem

23. *
Some Advantages

25. • Microsoft.SharePoint.Client
Summary