Steps to create Custom Columns and Custom Content Type using Visual Studio

The steps to be followed to create a custom content type using visual studio are as follows:
  • Open up the VS 2010 with the Admin priviledge
  • Create a new "Content Type Project"
  • Provide the URL of the site where the content type needs to be created and validate it
  • If required deploy it as a SandBox Solution or else deploy it as a Farm Solution and click on the Finish button, this will create the solution
  • Choose the base content type, for e.g. "Item" and click on the Finish button
  • Set the scope of the feature as "Site" or whatever is needed
  • In the Solution Explorer under the name provided for the content type there will be a file as "Elements.xml", open up the file, it is good to rename the xml file e.g. XXXContentType.xml
  • In this file we need to provide the following details:
    • ID - this is the GUID which is autogenerated
    • Name - the name of the content type
    • Description - the description of the content type
    • Group - the heading under which it should be displayed in the site, for e.g. "Custom Content Type"
    • Inherits - this should be set to "True"
    • Version - this is the version number
  • Build the solution to make sure there are no errors
  • Now some custom fields needs to be added to the content type before it can used, to do this right click on the solution name and click on "Add a new item"
  • From the window that opens up, choose the option "Empty Element" and give it a name
  • In the Solution Explorer under the name provided for the custom field there will be a file as "Elements.xml", open up the file, it is good to rename the xml file e.g. XXXCustomColumns.xml
  • In this file we will create the fields that are needed, the details to be provided are as follows:
    • ID - this is the GUID which can be created using the Make GUID tool in VS
    • Type - the type of the field
    • Name - the internal name of the field
    • Display Name- the name that will be displayed to the user
    • Required - whether the value for this field is required or not
    • Group - specify a group name

  • After the fields have been created we need to map it to the content type of whose it should be a part of, in order to do so we need to open up the Elements.xml file of the content type
  • In the file inside the tag "<FieldRefs></FieldRefs>" we need to add a tag as "<FieldRef ID="{GUID}"/>", the GUID should be the same that we have specified when the fields were created, the name and the display name
  • Build the solution and deploy it
  • Under the "Site Collection Features" of the site make sure that the feature is activated
  • In the site collection under "Site Settings - Galleries - Site Columns" the columns created should be displayed
  • In the site collection under "Site Settings - Galleries - Site Content Type" the content type should be displayed under the custom content type group heading

Comments

Post a Comment

Popular posts from this blog

jQuery Basics

jQuery Introduction The files needed to run a jQuery function can be downloaded from the URL mentioned below: http://jquery.com/download/ There are actually two versions of the file that is available, the first one id the minified and compressed version, jquery-1.10.1.min.js , which is basically used for the production environment and the other is the full version, uncompressed and readable, which is used for the development environment. If somebody does not want to download the file, they can use it from the CDN (Content Delivery Network) provided both by Google and Microsoft, the details are here under: Google - http://ajax.googleapis.com/ajax/libs/jquery/1.10.1/jquery.min.js Microsoft - http://ajax.aspnetcdn.com/ajax/jQuery/jquery-1.10.1.min.js Note:  If you look at the Google URL above - the version of jQuery is specified in the URL (1.10.1). If you would like to use the latest version of jQuery, you can either remove a number from the end of the version st...
Read more

What is the difference between a Page Layout and Master Page in SharePoint?

A Page Layout is nothing but a template which when used in conjuncture with the Master Page gives the look and feel and contents of the page. Each page layout has an associated content type that determines the kind of content that can be stored on pages based on that page layout. Master Pages and Page Layouts dictate the overall look and feel of your SharePoint site. Master Pages contain controls that are shared across multiple page layouts, such as navigation, search, or language-preference for multilingual sites. Page layouts contain field controls and Web Parts. All page layouts reference a master page that is based on the CustomMasterUrl property of the SPWeb class. The top-level SharePoint Server site for a site collection hosted on SharePoint Server 2010 has a special document library called the Master Page and Page Layout Gallery. All Page Layouts and Master Pages are stored in this document library. Reference: http://blog.beckybertram.com/Lists/Posts/Post...
Read more

Accessing data from SharePoint 2010 to an ASP.NET application

Image
In order to access the SharePoint lists and document libraries data from a native ASP.NET application we need to make use of the web services that have been provided. The full list of the web services available from within SharePoint 2010 can be found here http://www.etechplanet.com/blog/sharepoint-web-services-7c-list-of-all-web-services-available-with-wss-30moss-2007.aspx The steps to access the web service are as follows: Create a native ASP.NET web application Add a reference of the web service Create an object of the web site Pass on to the web service object the credentials using which the access will be authorized Retrieve the results using the appropriate method
Read more