Workaround : Ajax and publishing pages.

When you have configured SharePoint for use with AJAX you will see , when you deploy an AJAX web part and put this on a pages, that when running this page the web part will fire the events but not will render de web part.

The work around for this “bug” is to move the <WebPartPages:SPWebPartManager ID="SPWebPartManager1" runat="server"/> just below the
scriptmanager tag in side the form tag.

Original:
<WebPartPages:SPWebPartManager ID="SPWebPartManager1" runat="server"/>
<form runat="server" onsubmit="return _spFormOnSubmitWrapper();">
<asp:ScriptManager ID="ScriptManager1" runat="server">
</asp:ScriptManager>

Change it to:

<form runat="server" onsubmit="return _spFormOnSubmitWrapper();">
<asp:ScriptManager ID="ScriptManager1" runat="server">
</asp:ScriptManager>
<WebPartPages:SPWebPartManager ID="SPWebPartManager1" runat="server"/>

Then you will se the web part will be rendered after fire ring an event.

Sharepoint: ListTemplateId

If you want to add a Event Handler Assembly to a specific list in Sharepoint with a Feature you have to pass a ListTemplateId.

List Types with there ID

• Genericlist -> 100
• DocumentLibrary ->101
• Survey -> 102
• Links ->103
• Announcements ->104
• Contacts ->105
• Events ->106
• Tasks ->107
• DiscussionBoard ->108
• PictureLibrary ->109
• DataSources ->110
• WebTemplateCatalog ->111
• UserInformation ->112
• WebPartCatalog ->113
• ListTemplateCatalog ->114
• XMLForm ->115
• MasterPageCatalog ->116
• NoCodeWorkflows ->117
• WorkflowProcess ->118
• WebPageLibrary ->119
• CustomGrid ->120
• DataConnectionLibrary ->130
• WorkflowHistory ->140
• GanttTasks ->150
• Meetings ->200
• Agenda ->201
• MeetingUser ->202
• Decision ->204
• MeetingObjective ->207
• TextBox ->210
• ThingsToBring ->211
• HomePageLibrary ->212
• Posts ->301
• Comments ->302
• Categories ->303
• IssueTracking ->1100
• AdminTasks ->1200