Walkthrough: Create a Custom Field, Content Type, List Definition, and List Instance

Display the New Project dialog box by pointing to New on the File menu, and then clicking New Project.

Expand the SharePoint node under either Visual C# or Visual Basic, and then click 2010.

Click Empty SharePoint Project in the Templates pane, change the name of the project to CustomField1, and then click OK.

The SharePoint Customization Wizard appears. The Empty Project template is used for custom field items because there is no template for them.

On the Specify the site and security level for debugging page, enter the URL for the SharePoint server site to which you want to add the new custom field item, or use the default location (http://<system name>/).

In the What is the trust level for this SharePoint solution? section, use the default value Deploy as a sandboxed solution.

For more information about sandboxed and farm solutions, see Sandboxed Solution Considerations.

Click Finish. You should see the project appear in Solution Explorer.

Add an Empty Element project item to the project. To do this, click the field's project node (CustomField1) in Solution Explorer and then click Add New Item on the Project menu.

Expand the SharePoint node under either Visual C# or Visual Basic, and then click 2010.

In the Templates pane, select Empty Element, keep the default name EmptyElement1, and then click Add.

In the Elements.xml file under EmptyElement1, add the following after the <Elements> tag:

<Field ID="{5744d18c-305e-4632-8bd1-09d134f4830d}" 
    Type="Note" 
    Name="PatientName" 
    DisplayName="Patient Name" 
    Group="A Custom Group">
</Field>

This adds a field that is named Patient Name.

Important
When adding a custom field, you must specify the ID, Type, Name, DisplayName, and Group attributes for the field to appear correctly in SharePoint. Statement completion erroneously indicates that you need only the first three of these attributes when in fact all five are required.

Press F5 to run and deploy the project to SharePoint.

If you get a message that script debugging is disabled, click Yes to continue debugging.

If this is the first time you have debugged a Web application in Visual Studio, you will be asked whether you want to modify the Web configuration file to enable debugging. Answer Yes.

At the top of the SharePoint Web page, click the Site Actions button and then click Site Settings.

Under the Galleries section of the Site Settings page, click the Site columns link.

In the Site Column Gallery page, scroll the page down to the Custom Columns heading and note the new field item added, Patient Name.

Close the browser.

Add a content type to the project. To do this, click the project node in Solution Explorer and then click Add New Item on the Project menu.

Expand the SharePoint node under either Visual C# or Visual Basic, and then click 2010.

In the Templates pane, select Content Type and use the default name, ContentType1.

In the SharePoint Customization Wizard, select Contact as the content type on which to base the new one, and then click Finish.

This opens the content type's Elements.xml file for editing.

In the <FieldRefs> section of Elements.xml, copy and paste in:

<FieldRef ID="{5744d18c-305e-4632-8bd1-09d134f4830d}" 
    Name="PatientName" 
    DisplayName="Patient Name" 
    Required="TRUE"/>

The FieldRef ID used here refers to the Field ID we created for the custom field.

Press F5 to run and deploy the project.

At the top of the SharePoint Web page, click the Site Actions button and then click Site Settings.

Under the Galleries section of the Site Settings page, click the Site content types link.

In the Site Content Types Gallery page, note the new content type we just created, CustomField1 - ContentType1. Click it to view its fields. In the list of fields for CustomField1 - ContentType1, note the field Patient Name is added.

Close the browser.

Add a list definition to the project. To do this, click the project node in Solution Explorer and then click Add New Item on the Project menu.

Expand the SharePoint node under either Visual C# or Visual Basic, and then click 2010.

In the Templates pane, select List Definition From Content Type and use the default name, ListDefinition1.

In the What is the display name of the list definition? box, leave the default value, CustomField1 - ListDefinition1.

In the What content type would you like to use for your list definition? list, use the default (and only) value, CustomField1 - ContentType1.

This creates a customizable list definition based on the new, modified Contacts list.

Select the Add a list instance for this list definition box to add a list instance project item to the project. The list instance will be an instance of the new list definition.

Click Finish. You should see the list definition appear in Solution Explorer.

In Solution Explorer, double-click Schema.xml under ListDefinition1 to view it.

Schema.xml defines all of the fields and other elements of the list definition, such as name and address. Notice under the <Fields> element at the top of the file that the following field definition was added by the content type:

<FieldRef ID="{5744d18c-305e-4632-8bd1-09d134f4830d}" 
    Name="PatientName" 
    DisplayName="Patient Name" 
    Required="TRUE" />

Press F5 to run and deploy the project.

Under the Lists section in the SharePoint QuickLaunch bar, click the CustomField1 - ListInstance1 link.

This is the list instance for the new list definition. Note that the new Patient Name field does not yet appear as a column in the list instance.

Click List in the List Tools menu tab at the top of the page and then click the Modify View button on the ribbon bar.

In the list of available Column Names, select Patient Name and then click OK. Notice that the Patient Name field now appears in the list instance.