Following are the classes in Server Object Model from development point of view:
-
- SPFarm
- SPWebApplication
- SPSite
- SPWeb
- SPList
- SPListItem
- SPDocumentLibrary
Before we begin – let us see what do these two abbreviations stand for.
- SPS means SharePoint Portal Services
- STS means SharePoint Team Services
i.) Document management system in SPS is better than STS.
ii.) The search engine in SPS is better, more efficient and possesses the capability to crawl multiple content sources in comparison to STS.
iii.) If Document Management is not required, STS is easier to manage for team environment while SPS is better for an organization where Document Management is required.
Four types of input forms can be created for a workflow:
- Association form
- Initiation form
- Modification form
- Task edit form
The difference between the two types lies in the architecture produced by them:
- Share point web part base class: is designed to build over the Microsoft ASP.NET web part infrastructure. Whereas, ASP.NET 2.0 Web Parts base class: provide the integrated set of controls to create a website. This enable the user to modify the content and behavior of the webpage using the user interface and directly from the browser.
- Share point web part base class: It provides the backward compatibility and can be used with ASP.NET application also and other applications that include the functionality to execute the code. Whereas, ASP.NET 2.0 Web Parts base class: doesn’t include backward compatibility and allow easy to use user interface.
- Share point web part base class: There are some features to be provided with it such as:
- Cross page connections: this is used to include the pages that are connected with each other but not as a part of the website
- Connections between Web Parts: these are the connections that are outside the Web Part
- Client-side connections: includes the web part service components that include all the services that are required to be shown.
- Data caching infrastructure: consists of the data structure that is used to keep all the data in the cache for future use.
Whereas, ASP.NET web parts base class: consists of controls that can be saved and some session that can be personalized using the web part capabilities.
Global assembly cache includes the assembly code or the machine code that is used to run the program so that it doesn’t have to bring the program in the memory. If the same program runs again then the binaries are fetched from the cache itself that makes it faster and easier to manage. It provides custom binaries that are deployed to be used in between the receiver and the sender. It is used with the .NET assemblies’ cache for the command line platform. It consists of the totally controlled repositories with the addresses given of the shared library.
CreateChildControls() method notifies the server about the control that to implement the child controls for posting back and for rendering. The statement is given as:
Protected: virtual void CreateChildControls();
The example shows the implementation of the CreateChildControls() method that is:
‘Override CreateChildControls to create the control tree.
<System.Security. Permissions.PermissionSetAttribute(System.Security.Permissions.SecurityAction.Demand, Name:=”FullTrust”)> _
Protected Overrides Sub CreateChildControls()
‘ Add a LiteralControl to the current ControlCollection.
Me.Controls.Add(New LiteralControl(“<h3>Value: “))
‘ Create a text box control, set the default Text property,
‘ and add it to the ControlCollection.
Dim box As New TextBox()
box.Text = “0”
Me.Controls.Add(box)
Me.Controls.Add(New LiteralControl(“</h3>”))
End Sub ‘CreateChildControls
This is the method that is used to instantiate the control and fetches the properties to set it according to the website. The add () method of the control class adds the control in the collection. The method CreateChildControls () implies that the WebPart consists of a collection of child controls.