Abstract
In previous versions of SharePoint, developers accessed content and performed operations via server side code called Server Object Model and/or used SharePoint Web Services. Now Microsoft has introduced a new way for developers to communicate with SharePoint Foundation 2010; this third way of writing code is known as Client Object Model. (SharePoint Server Object Model and SharePoint Web Services are still options). The Client Object Model (Client OM) API can be used in .NET based applications, Silverlight applications, and in ECMAScript (JavaScript) that executes in the browser. Although the Client OM API is not as rich as the Server Object Model, it has its own benefits, such as an object-oriented way of accessing SharePoint content without the complexities of Server Object Model and SharePoint Web Services, no packaging and deployment hassles, easy access to content stored in SharePoint list/libraries, quick and easy scripting, etc.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2011 Steve Wright, Dan Bakmand-Mikalski, Razi bin Rais, Darrin Bishop, Matt Eddinger, Brian Farnhill, Ed Hild, Joerg Krause, Cory Loriot, Sahil Malick, Matthew McDermott, David Milner, Ed Musters, Tahir Naveed, Mark Orange, Doug Ortiz, Barry Ralston, Ed Richard, Karthick Sethunarayanan
About this chapter
Cite this chapter
Wright, S. et al. (2011). The SharePoint 2010 Client Object Model. In: Expert SharePoint 2010 Practices. Apress. https://doi.org/10.1007/978-1-4302-3871-3_7
Download citation
DOI: https://doi.org/10.1007/978-1-4302-3871-3_7
Publisher Name: Apress
Print ISBN: 978-1-4302-3870-6
Online ISBN: 978-1-4302-3871-3
eBook Packages: Professional and Applied ComputingApress Access BooksProfessional and Applied Computing (R0)