The following 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
There are three main event classes:
* SPItemEventReceiver
* SPListEventReceiver
* SPWebEventReceiver
Attributes of Feature.XML File
| 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. |
