SharePoint 2010 Base Types, List Template and Definition IDs, and Content Types IDs

Base Types

These Base Types come from the SPBaseType enumeration.

Base Type	ID
Custom List	0
Document Library	1
Not used	2
Obsolete. Use 0 for discussion boards.	3
Surveys	4
Issues List	5

 List Definitions

These List Definitions come from the SPListTemplateType enumeration.

Enumeration Name	Description	ID
InvalidType	Not used	-1
NoListTemplate	unspecified list type	0
GenericList	Custom list	100
DocumentLibrary	Document library	101
Survey	Survey	102
Links	Links	103
Announcements	Announcements	104
Contacts	Contacts	105
Events	Calendar	106
Tasks	Tasks	107
DiscussionBoard	Discussion board	108
PictureLibrary	Picture library	109
DataSources	Data sources for a site	110
WebTemplateCatalog	Site template gallery	111
UserInformation	User Information	112
WebPartCatalog	Web Part gallery	113
ListTemplateCatalog	List Template gallery	114
XMLForm	XML Form library	115
MasterPageCatalog	Master Page gallery	116
NoCodeWorkflows	No Code Workflows	117
WorkflowProcess	Custom Workflow Process	118
WebPageLibrary	Wiki Page Library	119
CustomGrid	Custom grid for a list	120
SolutionCatalog	Solutions	121
NoCodePublic	No Code Public Workflow	122
ThemeCatalog	Themes	123
DataConnectionLibrary	Data connection library for sharing information about external data connections	130
WorkflowHistory	Workflow History	140
GanttTasks	Project Tasks	150
Meetings	Meeting Series (Meeting)	200
Agenda	Agenda (Meeting)	201
MeetingUser	Attendees (Meeting)	202
Decision	Decisions (Meeting)	204
MeetingObjective	Objectives (Meeting)	207
TextBox	Text Box (Meeting)	210
ThingsToBring	Things To Bring (Meeting)	211
HomePageLibrary	Workspace Pages (Meeting)	212
Posts	Posts (Blog)	301
Comments	Comments (Blog)	302
Categories	Categories (Blog)	303
Facility	Facility	402
Whereabouts	Whereabouts	403
CallTrack	Call Track	404
Circulation	Circulation	405
Timecard	Timecard	420
Holidays	Holidays	421
IMEDic	IME (Input Method Editor) Dictionary	499
ExternalList	External	600
IssueTracking	Issue tracking	1100
AdminTasks	Administrator Tasks	1200
HealthRules	Health Rules	1220
HealthReports	Health Reports	1221

Content Types

These content types come from the Content Type ID list.

Content Type	ID
System	0x
Item	0×01
Document	0×0101
Event	0×0102
Issue	0×0103
Announcement	0×0104
Link	0×0105
Contact	0×0106
Message	0×0107
Task	0×0108
Workflow History	0×0109
Post	0×0110
Comment	0×0111
East Asia Contact	0×0116
Folder	0×0120

Referred :- 

http://joelblogs.co.uk/2011/06/16/sharepoint-2010-base-types-list-template-and-definition-ids-and-content-types-ids

and MSDN site

 

ASP.NET User Controls

In addition to using Web server controls in your ASP.NET Web pages, you can create your own custom, reusable controls using the same techniques you use for creating ASP.NET Web pages. These controls are called user controls.

A user control is a kind of composite control that works much like an ASP.NET Web page—you can add existing Web server controls and markup to a user control, and define properties and methods for the control. You can then embed them in ASP.NET Web pages, where they act as a unit.

SharePoint USER Controls

A user control is a control that is associated with a .ASCX extension and was originally intended for a developer to re-use within a single project.  ASP.NET developers know it is really easy to create a new user control, drag and drop some controls onto a visual designer, put some logic in the control’s code-behind, and re-use the control within a single project.  This is because the .ASCX file associated with the control enables you to create markup for your control:

<%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %>

<%@ Control Language="C#" 

        AutoEventWireup="true" 

        CodeBehind="EchoControl.ascx.cs" 

        Inherits="ControlsDemo.ControlTemplates.ControlsDemo.EchoControl" %>

Enter some text:

<asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>

<asp:Button ID="Button1" runat="server" Text="Button" />

<asp:Label ID="Label1" runat="server" Visible="false"></asp:Label>

Because you can add markup for your control, you get the nice WYSIWYG designers for your control.  This allows you to drag items from the toolbox, such as a button, a label, and a text box. 

SharePoint Server Controls

A server control is a compiled control that renders on the server.  Where user controls derive from System.Web.UI.UserControl, a server control (also known as a custom control) typically derives from System.Web.UI.WebControl.  The main difference is that server controls do not have a corresponding .ASCX control.  For some scenarios, this can be highly beneficial because the page parser does not need to parse the .ASCX control.

Creating a server control is very easy.  In Visual Studio 2010, add a new ASP.NET Server Control item to your project from the Web group.

image

The generated template is just a suggestion, you can edit the class to suit your needs.  Here is a useful control for SharePoint developers that simply shows the name of the server that is currently processing the request.

using System;

using System.Web.UI.WebControls;

using System.Web.UI;

namespace ControlsDemo

{

    [ToolboxData("<{0}:ServerNameControl runat=server></{0}:ServerNameControl>")]

    public class ServerNameControl : WebControl

    {

        protected override void CreateChildControls()

        {

            Label l = new Label();

            l.Text = System.Environment.MachineName;

            Controls.Add(l);   

        }

    }

}

NPOI

What IS NPOI

NPOI  is the .NET version of POI Java project at http://poi.apache.org/. POI is an open source project which can help you read/write xls, doc, ppt files. It has a wide application.

we can use it to

a. generate a Excel report without Microsoft Office suite installed on your server and more efficient than call Microsoft Excel ActiveX at background;

b. extract text from Office documents to help you implement full-text indexing feature (most of time this feature is used to create search engines).
c. extract images from Office documents

d. generate Excel sheets that contains formulas

Advantage of NPOI

a. It's totally free to use

b. Cover most features of Excel (cell style, data format, formula and so on)

c. Professional support service (even 24*7) from NPOI team (not free)

d. Support xls, xlsx, docx.

e. Designed to be interface-oriented (take a look at NPOI.SS namespace)

f. Support not only export but also import

g. .Net 2.0 based even for xlsx and docx (though we also support .NET 4.0)

h. Successful cases from all over the world

i. huge amout of basic examples

System Requirement

VS2010 with .NET 4.0 runtime
VS2005 or VS2008 with .NET 2.0 Runtime (SP1)
vs2003 with .NET 1.1
medium trust environment in ASP.NET

Reading the excel data:-

Documentum Overview

What is Documentum?

Documentum is document management software that provides management of document content and attributes such as check-in, check-out, workflow, and version management. The Documentum product is a three-tier, client-server system built on top of a relational database.

A Docbase is a Documentum repository that stores document content, attributes, relationships, versions, renditions, formats, workflow, and security. Documentum Query Language (DQL), an extended SQL dialect, is used to query Documentum data. A Docbase is the equivalent of an Oracle instance or a DB2^(R) database plus document content files. 

The metadata is stored in the underlying relational database management system (RDBMS), and the content is stored as binary large objects (BLOBs) in the database or as files stored within the file-system of the server system. For more information on Documentum, refer to the Documentum manuals.

The wrapper for Documentum allows you to add a Documentum data source to a DB2 federated system. By adding the Documentum data source to a federated system, you can use SQL statements to access and query objects and registered tables in a Documentum Docbase. You can then integrate this data with other data sources in your federated system without having to move the data out of the native data source. 

Enterprise Content Management Documentum Overview


What is ECM?


Enterprise Content Management (ECM) is the technologies used to capture, manage, store, preserve, and deliver content and documents related to organizational processes. ECM tools and strategies allow the management of an organization's unstructured information, wherever that information exists.


Why we need ECM?


1- Enterprise Content Management The ECM platform helps manage unstructured content Over 80% of enterprise content is unstructured Problems associated with unstructured content: Ineffectively classified Difficult to find Not secure Structured Unstructured Email & Attachments PDFs Checks X-rays Paper Documents Rich Media Web Pages Audio & Video Records Invoices Manuals Claims Contracts Instant Messages Forms Images XML Rows and Columns






History In 2003


EMC acquires Documentum, Inc., further advancing its Information Lifecycle Management strategy—to enable customers to get the maximum value from their information, from creation and collaborative use to archiving and disposal. In 2005 continuing its focus on the content management opportunity, EMC acquires Captiva Software, a leading provider of input management solutions. Captiva's market leading products provide capabilities critical to implementing advanced information lifecycle management initiatives.






EMC Content Management Portfolio

Documentum Family The EMC Documentum product family helps you manage all types of content across multiple departments within a single repository. With a unified repository, various groups can easily share and reuse their content with other areas of the business that would benefit from access to this valuable information. Our product family also allows your business to share its content safely with outside organizations including partners, vendors, and customers. Captiva Family The EMC Captiva family helps you transform business critical information from paper, fax and electronic data sources into business-ready content suitable for processing by enterprise applications. You’ll easily automate the processing of billions of documents annually, quickly and accurately converting their contents into information that is usable for all enterprise business processes in a timely and cost-effective manner