SharePoint List Template Id’s

When creating SharePoint 2007 receivers, the ListTemplateId attribute is associated with a “value” that is an optional unique identifier for the target template for which the receiver is being built. The value of templates are as shown below. 

Value	Description
1200	Administrator tasks list
104	Announcements list
303	Blog Categories list
302	Blog Comments list
301	Blog Posts list
105	Contacts list
120	Custom grid for a list
118	Custom Workflow Process
130	Data Connection library
110	Data sources
108	Discussion board
101	Document library
106	Events list
150	Gantt Tasks list
100	Generic list
1100	Issue tracking
103	Links list
114	List template gallery
116	Master pages gallery
201	Meeting Agenda list
202	Meeting Attendees list
204	Meeting Decisions list
207	Meeting Objectives list
200	Meeting Series list
210	Meeting text box
211	Meeting Things To Bring list
212	Meeting Workspace Pages list
117	No-Code Workflows
2002	Personal document library
109	Picture library
300	Portal Sites list
2003	Private document library
111	Site template gallery
102	Survey
107	Tasks list
112	User Information list
113	Web Part gallery
119	Wiki Page library
140	Workflow History
115	XML Form library

SharePoint Elements by Scope

This excerpt was taken straight from the MSDN but I’ve blogged this, just in case it gets archived. I believe it’s extremely useful when developing custom solutions for SharePoint. 

SharePoint Content Deployment Alternatives

While the out-of-the-box SharePoint content deployment features can be restrictive; allowing only one-way replication of content, Syntergy offer a solution with their Syntergy Replicator product. If you are ever faced with an international replication scenario, I would suggest that you consider this product; noting that workflow instances are not replicated (see next paragraph for more details). Syntergy’s products are not freeware and come at a price.  

While Syntergy Replicator allows for two-way replication of SharePoint content, I have faced a situation around the replication of workflow instances. Workflow instance entities can only be actioned on the server on which they have been instantiated. While the workflow instance entities (workflow tasks, for example) are replicated faithfully, the workflow instances that are related to these tasks are not replicated across. Unfortunately, work-arounds have to be built for this scenario as international users attempting to action a workflow task are presented with an error message in SharePoint.

Another product from Syntergy called Presentation Publisher that is still in Beta (as of this writing) has the ability to replicate web parts and layouts.

In my experience, Syntergy have good support personnel and quality assurance teams in the U.S. and Canada who are always ready to help.