Identity : Microsoft.SharePoint
Description : Windows SharePoint Services
Path : To add a reference to a Sharepoint API, Right-click the project(in VS) and select Add Reference. Click the Browse tab and select the following directory:
C:\program files\common files\microsoft shared\web server extensions\12\isapi
Some useful Microsoft.SharePoint Namespaces follows with Description :
Provides types and members for working with a top-level site and its subsites or lists.
Provides administrative types and members for managing a Windows SharePoint Services deployment.
Provides types and members for performing backup and restore operations on SharePoint sites.
Provides types and members for importing and exporting content between Windows SharePoint Services Web sites.
Provides the base class for the data retrieval service adapters used in Windows SharePoint Services.
Provides types and members that can be used to customize Meeting Workspace sites.
Provides server controls for rendering the mobile forms and view pages used in SharePoint lists.
Provides types and members for customizing the navigation structures and site maps of SharePoint Web sites.
Provides a set of code access permission and attribute classes designed to protect a specific set of resources and operations, such as access to the Windows SharePoint Services object model, the ability to do unsafe saving on HTTP Gets, and enabling point-to-point Web Part connections.
Provides an interface for creating custom operations to run at the command prompt in STSADM.EXE
Provides types and members for upgrading a Windows SharePoint Services deployment.
Provides utilities for encoding strings and processing user information.
Provides server controls that are used on site and list pages in a SharePoint site.
Provides classes, interfaces, and members for creating custom Web Parts and Web Part pages
Provides types and members for associating, initiating, and managing workflow templates and instances.
Provides types that represent workflow activities. These activities can be assembled into workflow activities.
Some useful Microsoft.SharePoint Classes follows with Description and Example :
Represents a collection of sites in a Web application, including a top-level Web site and all its subsites. Each SPSite object, or site collection, is represented within an SPSiteCollection object that consists of the collection of all site collections in the Web application.
E.g : SPSite siteCollection = SPControl.GetContextSite(Context);
Represents a Windows SharePoint Services Web site.
E.g : SPWeb objWebSite = siteCollection.OpenWeb();
Represents a collection of SPWeb objects.
E.g : SPWebCollection objWebCollection = siteCollection.AllWebs;
Provides static security management properties and methods.
E.g : SPSecurity.CodeToRunElevated myCode =
Represents a collection of SPList objects.
E.g : SPListCollection objListCollection = objWebSite.Lists ;
Represents a list on a SharePoint Web site.
E.g : foreach(SPLists objLists in objListCollection)
Represents a user in Microsoft Windows SharePoint Services.
E.g : SPUser objUser = objWebSite.CurrentUser ;
SharePoint 2010 Object Model
In Sharepoint Object model there are two Important namespaces.
The Microsoft.Office.Server namespace is the root namespace of all Office Server objects and Microsoft.SharePoint is the root namespace for all WSS objects.
The Chart Below illustrates some of the key classes contained in each of these namespaces, as well as to which functional area they belong.
Document Libraries (Microsoft.SharePoint)
SPDocumentLibrary , SPPictureLibrary
Business Data Catalog (Microsoft.Office.Server.ApplicationRegistry.Administration)
EntityCollection , ApplicationRegistry
SPFeatureDefinition, SPFeatureScope, SPElementDefinition, SPFeature, SPFeatureProperty
SPSite, SPSiteAdministration, SPSiteCollection, SPWeb
User Profiles (Microsoft.Office.Server.UserProfiles)
SPsolution, SPFeatureReceiver, SPSolutionCollection
SPList, SPListItem, SPListItemCollection
* To use the SharePoint API, your code must reside on one of the machines in a SharePoint
application server farm. Your code can still work with other sites in the farm from any
other site in the farm, but you cannot, for example, work with the SharePoint API from a
machine on which MOSS or WSS is not installed.
* The only practical way to consume SharePoint data and functionality from a remote client is to use the SharePoint web services.
* The object model is not designed to support Remoting.