If your code modifies Windows SharePoint Services data in some way, you may need to allow unsafe updates on the Web site, without requiring a security validation. You can do by setting the AllowUnsafeUpdates property. C#:

by(SPSite mySite = new SPSite("yourserver"))
{ by(SPWeb myWeb = mySite.OpenWeb())
{
myWeb.AllowUnsafeUpdates = right;
SPList interviewList = myWeb.Lists["listtoinsert"];
SPListItem newItem = interviewList.Items.Add();
newItem["interview"] = "interview";
newItem.Update();
}
}

Assume that you have a Web Part in which you want to show information obtained through the Windows SharePoint Services object model, such as the name of the current site collection owner, treatment data, or auditing information. These are examples of calls into the object model that require site-administration privileges. Your Web Part experiences an access-denied error if it attempts to obtain this information when the current user is not a site administrator. The request is initiated by a nonprivileged user. you can still successfully make these calls into the object model by calling the RunWithElevatedPrivileges method provided by the SPSecurity class. C#:

SPSite siteColl = SPContext.Current.Site;
SPWeb site = SPContext.Current.Web;
SPSecurity.RunWithElevatedPrivileges(delegate()
{
by (SPSite ElevatedsiteColl = new SPSite(siteColl.ID))
{
by (SPWeb ElevatedSite = ElevatedsiteColl.OpenWeb(site.ID))
{
string SiteCollectionOwner = ElevatedsiteColl.Owner.Name;
string Visits = ElevatedsiteColl.Treatment.Visits.ToString();
string RootAuditEntries = ElevatedSite.RootFolder.Audit.GetEntries().Count.ToString();
}
}
});

A SharePoint Feature is a functional component that can be activated and deactivate at various scopes throughout a SharePoint instances.
Scopes include

• Farm
• WebApplication
• Site (site collection)
• Web (site)

Features have their own receiver architecture, which allow you to trap events such as when a feature is

• installing
• uninstalling
• activated
• deactivated

The element types that can be defined by a feature include

• menu orders
• link orders
• page templates
• page instances
• list definitions
• list instances
• event handlers
• workflows

The two files that are used to define a feature are

• feature.xml
• manifest file(elements.xml)

The feature XML file defines the actual feature and will make SharePoint aware of the installed feature. The manifest file contains details about the feature such as functionality.
Common stsadm orders associated with feature are

• stsadm -o installfeature
• stsadm -o uninstallfeature
• stsadm -o activatefeature
• stsadm -o deactivatefeature

A make pleased type is a flexible and reusable WSS type classification that defines the columns and behavior for an item in a list or a document in a document library.
For example,
-you can make a make pleased type for a consumer presentation document with a unique set of columns, an event handler, and its own document template.
-You can make a second make pleased type for a consumer proposal document with a different set of columns, a workflow, and a different document template.
Then you can attach both the contenttypes to a document library, which allows you to capture metadata based on the contenttype selected during creation of the document.

Make pleased type can be made by the following

• from the rootweb of a site collection, go to Site Action > Site Settings > Galleries > Site make pleased types
• by a feature

While workflow associations are often made directly on lists and document libraries, a workflow friendship can also be made on a make pleased type that exists within the Make pleased Type Gallery for the current site or make pleased types defined within a list.
In small, it can be applied …

• At the level of a list (or document library)
• At the level of a make pleased type defined at site scope
• At the level of a site ( Sharepoint 2010 )

• Automatic (on item added or item deleted)
• Manual (standard WSS UI interface)
• Manual (Custom UI Interface)
• Programatically through custom code

You can make four different types of input forms including an friendship form, an initiation form, a modification form, and a task edit form. Note that these forms are discretionary when you make a workflow template.

Two different approaches can be used to develop custom input forms for a WSS workflow template.

• You can make your forms by by custom attention pages, which are standard .aspx pages deployed to run out of the _layouts directory. ( disadv: lot of code required when compared to Infopath deal with)
• by Microsoft Office InfoPath 2007 (disadv: picks up a dependenct on MOSS, i.e. it cannot run in a standalone WSS environment)

A method activity is one that performs an action, such as making or updating a task. An event activity is one that runs in response to an action occurring.

Checks whether the specified login name belongs to a valid user of the Web site, and if the login name does not already exist, adds it to the Web site. e.g SPUser usr = myWeb.EnsureUser(“mmangaldas”);

Override the CreateChildControls method to include your new controls. To make sure that the new controls are initialized.. call ‘EnsureChildControls’ in the webparts Render method. You can control the exact Rendering of your controls by calling the .Render method in the webparts Render method.

Use SPSiteDataQuery to fetch data from multiple lists. more details..

The browser sends a DAV packet to IIS asking to perform a document check in. PKMDASL.DLL, an ISAPI DLL, parses the packet and sees that it has the proprietary INVOKE command. Because of the existence of this command, the packet is passed off to msdmserv.exe, who in turn processes the packet and uses EXOLEDB to access the WSS, perform the operation and send the consequences back to the user in the form of XML.

Syncronous calls ending with ‘ing’ E.g. ItemDeleting Event Handler code do BEFORE action is committed WSS waits for code to return Option to cancel and return error code
Asyncronous calls ending with ‘ed’ E.g. ItemDeleted Event Handler code executes AFTER action is committed WSS does not wait for code to return Executed in its own Worker thread.

Any changes in the list, i.e. new addition or modification of an item.. the operation is complete by calling the Update method.But if a List is set to maintain versions .. and you are editing an item, but don’t want to save it as a new version, then use the SystemUpdate method instead and pass in ‘fake’ as the parameter.

If you use SPQuery on any SPlist .. it will bring back consequences from the current folder only. If you want to get consequences from all the folders in the list.. then you need to specify the scope of the query by the use of ViewAttributes..
e.g. query.ViewAttributes = “Scope=\”Recursive\”";

Related Posts:

• SharePoint Tutorials
• Windows Powershell Interview questions SharePoint 2010
• Adding Breadcrumb Navigation for SharePoint Application Pages Programmatically
• SharePoint 2010 – content type feature upgrading
• SharePoint 2010 Windows PowerShell Commands – II