Create Taxonomy Group in SharePoint 2010 Programmatically Using VS 2012

Introduction

 

Today, in this article let's play around with one of the interesting and most useful concepts in SharePoint 2010.

 

Question: What is Taxonomy?

 

In simple terms "Taxonomy is formally defined as the practice of classification according to natural relationships which can be tagged or filtered whereby associating with the specific term store".

 

Step 1: Open SharePoint 2010 Central Administration and navigate to a specific site.

 

Step 2: Open up Visual Studio 2012 and create an "Empty SharePoint project", as in:

 

OpenSharepoint2010.jpg
 

 

Step 3: Select "

Deploy as a farm solution" as in the following and click on the "Finish" button. Now an empty project is created.

 

DeploySharepoint2010.jpg
 

 

Step 4: Add a new visual webpart for that project.

 

AddVisualWebPart.jpg
 

 

Step 5: The complete code of visualwebpart1usercontrol.ascx looks like this:


<div align="center">
    <table style="font-family: Verdana">
        <tr>
            <td colspan="2">
                <asp:label id="Label1" runat="server" text="Create Group and TermSet - SharePoint 2010 via Visual Studio 2012"
                    font-bold="true" forecolor="Maroon" font-size="Large"></asp:label>
            </td>
        </tr>
        <tr>
            <td>
                <asp:label id="Label2" runat="server" text="Please Enter Group Name: "></asp:label>
            </td>
            <td>
                <asp:textbox id="TextBox1" runat="server" width="117px"></asp:textbox>
            </td>
        </tr>
        <tr>
            <td>
                <asp:label id="Label3" runat="server" text="Please Enter Term Set Name:"></asp:label>
            </td>
            <td>
                <asp:textbox id="TextBox2" runat="server" width="117px"></asp:textbox>
            </td>
        </tr>
        <tr>
            <td>
                <asp:label id="Label5" runat="server" text="Please Enter Term Name:"></asp:label>
            </td>
            <td>
                <asp:textbox id="TextBox3" runat="server" width="117px"></asp:textbox>
            </td>
        </tr>
        <tr>
            <td>
                <asp:label id="Label6" runat="server" text="Please Enter Term Description :"></asp:label>
            </td>
            <td>
                <asp:textbox id="TextBox4" runat="server" textmode="MultiLine" width="117px"></asp:textbox>
            </td>
        </tr>
        <tr>
            <td colspan="2" style="text-align: center">
                <asp:button id="Button1" runat="server" text="Create Group" forecolor="Orange" font-bold="true"
                    backcolor="Black" onclick="Button1_Click" width="142px" style="margin-left: 0px" />
            </td>
        </tr>
        <tr>
            <td colspan="2" style="text-align: center">
                <asp:label id="Label4" runat="server" font-bold="true"></asp:label>
            </td>
        </tr>
    </table>
</div>

Step 6: The complete code of visualwebpart1usercontrol.ascx.cs looks like this:


using Microsoft.SharePoint;
using Microsoft.SharePoint.Taxonomy;
using System;
using System.ComponentModel;
using System.Web.UI.WebControls.WebParts;namespace SharePointProject1.VisualWebPart1
{
    [ToolboxItemAttribute(false)]
    public partial class VisualWebPart1 : WebPart
{
    // Uncomment the following SecurityPermission attribute only when doing Performance Profiling on a farm solution
        // using the Instrumentation method, and then remove the SecurityPermission attribute when the code is ready
        // for production. Because the SecurityPermission attribute bypasses the security check for callers of
        // your constructor, it's not recommended for production purposes.
        //
        [System.Security.Permissions.SecurityPermission(System.Security.Permissions.SecurityAction.Assert, UnmanagedCode = true)]
        public VisualWebPart1()
        {
        }
        protected override void OnInit(EventArgs e)
        {
            base.OnInit(e);InitializeControl();
        }
        protected void Page_Load(object sender, EventArgs e){TextBox1.Focus();
        }
        protected void Button1_Click(object sender, EventArgs e)
        {
            if (string.IsNullOrEmpty(TextBox1.Text) || string.IsNullOrEmpty(TextBox2.Text) ||string.IsNullOrEmpty(TextBox3.Text) || string.IsNullOrEmpty(TextBox4.Text))
            {
                Label4.Text = "Please Enter Some Values";
                Label4.ForeColor = System.Drawing.Color.Red;
            }
            else{SPSite site = new SPSite("http://win-5c3g1lanj3k:46908/");
                TaxonomySession session = new TaxonomySession(site);
                TermStore termStore = session.TermStores["Managed Metadata Service"];
                Group group = termStore.CreateGroup(TextBox1.Text);
                TermSet termSet = group.CreateTermSet(TextBox2.Text);
                Term term = termSet.CreateTerm(TextBox3.Text, 1033);
                term.SetDescription(TextBox4.Text, 1033);
                termStore.CommitAll();
                Label4.Text = TextBox1.Text + " - Taxonomy Group Created Successfully";
                Label4.ForeColor = System.Drawing.Color.Green;
                TextBox1.Text = string.Empty;
                TextBox2.Text = string.Empty;
                TextBox3.Text = string.Empty;
                TextBox4.Text = string.Empty;
            }
        }
    }
}

 

Step 7: Deploy the solution file and add the new webpart to the SharePoint site.

 

Step 8: The output of the application looks like this:

 

OutputSharepoint2010.jpg
 

 

Step 9: Data entering output of the application looks like this:

 

DataEnteringOutputSharepoint.jpg
 

 

Step 10: Taxonomy group created output of the application looks like this:

 

TaxonomySharepoint2010.jpg

 

I hope this article is useful for you.

Up Next
    Ebook Download
    View all
    Learn
    View all
    MVC Corporation is consulting and IT services based company.