Skip to main content
Email Password   helpLost your password?

Overview

Applies To

Summary

Microsoft provides ways to extend the out of the box functionality of SharePoint Portal Server 2007 e.g. Features, SharePoint Designer 2007, Windows Workflow Foundation etc. Features offer flexibility in terms of developing extended functionality � such as Page Templates, List, Content Types, Web Parts, Workflow and events � to new and existing SharePoint 2007 sites.

Contents

Introduction

The Feature Framework has been extended to allow developers to create custom Features. Features can be deployed by using SharePoint Portal Server 2007 new form of deployment, namely Solution Deployment. Solutions are custom packages (e.g. WSP file) or redistributable CAB files, created by developers and deployed by SharePoint Administrators. Administrator can deploy Features to the individual site or to all Web front End Servers.

In this article, I will walk-through Creating and deploying an Event Handler Feature, which can be activated on the Web or Site, Site Collection, Web Application or Farm Level.

Components of Feature

A Feature can include any number of files, but it must include a Feature.xml file. The Feature.xml file, or Feature manifest, is the driver of the Feature, and this is the first file SharePoint looks at when invoking a Feature.

Features are organized in folders under the Features directory located under 12 hives; Where SharePoint Server 2007 puts all of its system files, at the following path: %SystemDrive%\Program Files\Common Files\Microsoft Shared\web server extensions\12.

In addition to the Feature.xml file, Features can include sub-folders and supporting files, such as element files that include for example, event handler references, ASPX pages deployed as part of the Feature, ASCX files, and DLL and RESX files.

Event Handler Feature

SharePoint Event Handler is a program that enhances and adds functionality throughout SharePoint List, List Items or Sites. Event Feature can be deployed to new or existing sites by using Features. SharePoint Object Model provides several event classes that can target event handlers to List, List Item or Sites.

Synchronous and Asynchronous Events

In addition to asynchronous events, SharePoint Server 2007 introduces synchronous events i.e. events that activate before the action occurs. Synchronous events can trap an item, document library or site before it is deleted. Synchronous events removed the ability for users to delete an item from the document library or event restricts users to delete columns from the document library.

SharePoint Object Model exposes several event classes inherited from Microsoft.SharePoint assembly. There are three main event classes:

Each class includes both synchronous and asynchronous methods to work with Item, List or Web Level. In this article, I will demonstrate how to hook an ItemDeleting, FieldDeleting or SiteDeleting Event to restrict users from deleting an item from the document library or from deleting a column from the document library.

SPItemEventReceiver

By overriding a member of the SPItemEventReceiver class, developers can restrict users from deleting, updating an Item in a List. Some of the important SPItemEventReceiver class members are described below:

Event Event Type Description
ItemAdded Asynchronous After an Item added in a list
ItemAdding Synchronous Before an Item added in a list
ItemAttachmentAdded Asynchronous After an attachment added from a list item
ItemAttachmentAdding Synchronous Before an attachment added from a list item
ItemAttachmentDeleted Asynchronous After attachment deleted from a list item
ItemAttachmentDeleting Synchronous Before attachment deleted from a list item
ItemCheckedOut Asynchronous After an item checked-In in a list
ItemCheckingOut Synchronous Before an item is checked out in a list
ItemCheckedIn Asynchronous After an item is checked-In in a list
ItemCheckingIn Synchronous Before an item is checked-In in a list
ItemDeleted Asynchronous After an item is deleted from a list
ItemDeleting Synchronous Before an item is deleted from a list
ItemUpdated Asynchronous After an item is updated in a list
ItemUpdating Synchronous Before an item is updated in a list

For the demonstration, I am using a synchronous event i.e. ItemDeleting, which restricts users from deleting an item in a list (document library). You can invoke this event with any type of list of document library by specifying the ListTemplateId attribute in a Feature Schema file e.g. ItemEventReceiver.xml.

See the screenshot below of ItemEventReceiver.cs and ItemEventReceiver.xml for defining the ListTemplateId and Assembly.

ItemDeletingEvent.JPG
ItemEventReceiver.cs class

ItemDeletingEvent.JPG
ItemEventReceiver.xml file

The following table shows the default list template integer IDs that you can use in defining the template ID for event handlers.

List Template Id List Template
100 Generic list
101 Document library
102 Survey
103 Links list
104 Announcements list
105 Contacts list
106 Events list
107 Tasks list
108 Discussion board
109 Picture library
110 Data sources
111 Site template gallery
113 Web Part gallery
114 List template gallery
115 XML Form library
120 Custom grid for a list
200 Meeting Series list
201 Meeting Agenda list
202 Meeting Attendees list
204 Meeting Decisions list
207 Meeting Objectives list
210 Meeting text box
211 Meeting Things To Bring list
212 Meeting Workspace Pages list
300 Portal Sites list
1100 Issue tracking
2002 Personal document library
2003 Private document library

SPListEventReceiver

By overriding a member of the SPListEventReceiver class, developers can restrict users from deleting, updating a list from a Site. Some of the important SPListEventReceiver class members are described below.

Event Event Type Description
FieldAdded Asynchronous After a document is added in a List
(Document Library)
FieldAdding Synchronous Before a document is added in a List
(Document Library)
FieldDeleted Asynchronous After a document is deleted from a list
(Document Library)
FieldDeleting Synchronous Before a document is deleted from a list
(Document Library)
FieldUpdated Asynchronous After a document is updated in a list
(Document Library)
FieldUpdating Synchronous Before a document is updated in a list
(Document Library)

For the demonstration, I am using a synchronous event i.e. FieldDeleting, which restricts users from deleting a document from a list (Document Library). In this case, I am again specifying ListTemplateId = 101 for Document Library in a ListEventReceiver.xml file.

SPWebEventReceiver

By overriding a member of the SPWebEventReceiver class, developers can restrict users from deleting a site from a site collection or even completely delete a site collection. Some of the important SPWebEventReceiver class members are described below:

Event Event Type Description
SiteDeleted Asynchronous After a site collection has been deleted
SiteDeleting Synchronous Before a site collection is being deleted
WebDeleted Asynchronous After a web site has been deleted
WebDeleting Synchronous Before a web site is being deleted

For the demonstration, I am using a synchronous event i.e. WebDeleting, which restricts users from deleting a web site from a site collection.

Building the Solution

We need Visual Studio 2005 to create a solution for providing the required functionality.

The steps required to create an event handler for SharePoint Sever application are described below:

Attributes of Feature.XML File

Some of the attributes of Feature Tag are described below:

Attribute Value Description
ID GUID Contains the globally unique identifier (GUID) for the Feature.
Title Text Returns the title of the Feature. Limited to 255 characters.
Scope Farm/WebApplication/Site/Web Can contain one of the following values: Farm (farm), WebApplication (Web application), Site (site collection), and Web (Web site).
Hidden True/False This attribute equals FALSE by default.
AlwaysForceInstall True/False Optional Boolean. TRUE if the Feature is installed by force during installation even if the Feature is already installed. For example, if set to TRUE, Feature installation callouts will always fire anytime a user tries to install the Feature (even if it is already installed) by using either the scanforfeatures or installfeature command-line operation. This attribute equals FALSE by default. The AlwaysForceInstall attribute affects Features of all scopes.

See screenshot below of Feature.XML file.

FeatureXML.JPG

Note: Complete source code of solution and package file is attached with this article.

Packaging the Features

In SharePoint Server 2007, Solutions are used to package and deploy Features, Site Definitions, Web Parts, Template Files, Assemblies and Code Access Security (CAS) policies to SharePoint front-end servers.

Steps for creating a Solution Package are described below:

Make WSP Cabinet File.JPG

Deploying the Features

Steps for deploying a Solution Package are described below:

add solution.JPG pg1.JPG

See screen below for a list of solutions deployed in a farm.

pg2.JPG pg3.JPG pg3.JPG

Activating the Solution

pg6.JPG Activate.JPG

Testing the Solution

Navigate to a Document Library in a Site, Where you have activated ItemEventResource feature.

pg8.JPG

Navigate to a Document Library in a Site, Where you have activated ListEventResource feature.

pg7.JPG

Navigate to a Site in a Web Application, Where you have activated WebEventResource feature.

Deactivating and Uninstalling the Solution

You can choose to turn deactivate a particular feature on your site or web application, or you can choose to uninstall a feature, which completely removes the feature from your SharePoint deployment. Features can be deactivated either through the administrative user interface or by using the STSADM.EXE command-line tool.

deactivate.JPG

Note: Files deployed as part of the Feature, such as ASPX, ASCX files are not removed when a Feature is uninstalled.

Platforms Tested

I have tested the included project on the following platforms:

References

Conclusion

In the article, I have demonstrated how to work with Features to enhance and extend SharePoint Sites by creating features for restricting users from deleting item, column and site for web application. This article also covered Features Packaging and deployment option and how can you de-activate or uninstall an existing feature.

You must Sign In to use this message board.
 
 
Per page   
 FirstPrevNext
Generalproblem with handling page events Pin
abdul1
1:41 10 Nov '09  
GeneralSharePoint Features it is easy Pin
itsaranga
2:28 29 Sep '09  
QuestionUpdate or extended the existing Feature Pin
Member 4750963
7:39 7 May '09  
GeneralError for sitedelete Pin
mstabb
7:15 11 Mar '09  
Generalunable 2 delete the site. Pin
shamsiya
16:44 10 Mar '09  
GeneralCorrection Pin
Jose Pablo Vega
7:29 24 Dec '08  
QuestionEvent not firining Pin
TheYoda
21:01 12 Nov '08  
QuestionFeature not found in the sitecollection feature Pin
raajii
5:58 22 Oct '08  
GeneralHow can use with itemadded for a particular document library Pin
sonashish
9:51 2 Oct '08  
GeneralExcellent article Pin
Member 3634250
11:05 19 Aug '08  
GeneralRe: Excellent article Pin
Portatofe
9:38 2 Oct '08  
GeneralProject Server 2007 Event Handler Pin
henryoh
6:55 16 Jul '08  
GeneralHi, May I ask: SharePoint EventHandler Deployed as Solution + Feature(.wsp or .wsp.cab), cannot deploy, no resources, and cannot trigger EventHandler Code. Thank you! Pin
qurl2008
17:12 10 Jul '08  
QuestionDeactivating and uninstalling features [modified] Pin
Lucy
5:29 10 Mar '08  
GeneralVery Good Effort adnan Pin
Tariq Younas
0:59 26 Feb '08  
Generalcan we customer listview with new webpart containing paging Pin
sanong
16:11 18 Nov '07  
GeneralTrap event When a role is created Pin
Saisreenath
1:09 14 Nov '07  
GeneralExcellent article Pin
Aziz ur Rahman Syed
22:43 13 Nov '07  
GeneralHow to Trap the folder creation event Pin
Saisreenath
19:09 18 Oct '07  
GeneralKeep up the good work - Adnan Pin
boura
18:59 12 Oct '07  
GeneralGreat article but please resolve this Pin
powerkru
23:31 11 Oct '07  
GeneralSharepoint portal Pin
Brave_Gass
22:53 4 Oct '07  
QuestionPut the user profile properties " Departament " in eventhandler Pin
deharf
13:15 26 Sep '07  
GeneralHi good article - and I need your advise Pin
sanong
6:41 8 Sep '07  
QuestionCustomizing Item Checkingin event handler Pin
Red October 7
22:29 19 Aug '07  


Last Updated 18 Nov 2007 | Advertise | Privacy | Terms of Use | Copyright © CodeProject, 1999-2009