Microsoft SharePoint - Explained
A SharePoint page is built by combining the web parts into a web page, to be accessed using a browser. Any web editor supporting ASP.NET can be used for this purpose, even though Microsoft OfficeSharePoint Designer is the preferred editor. The extent of customization of the page depends on its design.
WSS pages are ASP.NET applications, and SharePoint web parts use the ASP.NET web parts infrastructure, and using the ASP.NET APIs, web parts can be written to extend the functionality of WSS. In terms of programmability, WSS exposes an API and object model to programmatically create and manage portals, workspaces and users. In contrast, the MOSS API is more geared towards automation of tasks and integration with other applications. Both WSS and MOSS can use the web parts API to enhance the end user functionality. In addition, WSS document libraries can be exposed over ADO.NET connections to programmatically access the files and revisions in them.
Microsoft SharePoint Portal services also helps organization to share the information and enable to work together as a team and people driven processes. Using this users can create their own workspaces and share the files between teams and organization. This helps maintain secured sharing. Enables organization to extend a customized collaboration of the workspace across partners and customer anytime anywhere.
This makes it easy for the organization to share and communicate to the right person using proper identities across corporates. Enable to build complete application using common framework that aggregates multiple portals and applications. This helps increase the efficiency of the process
* Accelerate innovation and collaboration across the organization
* Leverage the collaborative workspace infrastructure to streamline collaborative authoring and information sharing to quickly and easily build collective intelligence.
* Leverage the collaboration workspace infrastructure to provide users with better ways for users to have persistent conversations with others, both within and outside the organization.
Sharepoint API overview:
Windows Sharepoint Portal Services includes an object model that allows programs to manipulate the structure of Sharepoint Sites. The main hierarchy of API object classes is:
* SPWebApplication is an entire Web Application
* SPContentDatabase is a Content Database used within a web application and stored in a separate
* SPSite is a Site Collection that includes multiple sites, similar to an IIS virtual directory
* SPWeb is a Web Site or a web page, typically an .aspx file
* SPList is a List on a web site
* SPListItem is an item in a list
* SPField is a field of an item in a list
All of these classes are found in the Microsoft.SharePoint namespace in the assembly Microsoft.Sharepoint.dll, which is located in the Global Assembly Cache.SharePoint is built on top of ASP.NET, so it uses many familiar ASP.NET concepts such as .aspx files, master pages, and web parts. Within a .aspx page, the SharePoint objects can be accessed using the SPContext.Current object, for example:
SPWeb currentWeb = SPContext.Current.Web;
foreach(SPWeb subWeb in currentWeb.Webs)
foreach(SPList list in subWeb.Lists)...
Understanding SharePoint lists (SPList objects) is central to understanding how SharePoint manages information. Essentially everything that is managed by SharePoint will be in a list at some level. For example, the Quick Launch of a Windows SharePoint Services site presents a hierarchy of sites, subsites, and lists (including lists of lists), instead of pages as such. If you add a page to such a site, the new page appears in the Quick Launch as a new item in a list of shared documents, not as a child node under the home page or some other page.
Third-party packages for Windows SharePoint Services :