Introduction
Today, in this article let's play around with one of the interesting and most useful concepts in SharePoint 2010.
Question: What is Document Set?
In simple terms "Document set helps to manage group of documents as a single entity".
Step 1
Open SharePoint 2010 Central Administration and navigate to the specific site.
Step 2
Open up Visual Studio 2012 and try to select "SharePoint Visual Web Part" project, as in:
![visualstudio2012.png]()
Step 3
Select "Deploy as a farm solution" as in the following and click on the "Finish" button.
![sharepointwizardwindow.png]()
Step 4
The complete code of visualwebpart1usercontrol.ascx looks like this:
<%@ Assembly Name="$SharePoint.Project.AssemblyFullName$" %>
<%@ Assembly Name="Microsoft.Web.CommandUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls"
Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="Utilities" Namespace="Microsoft.SharePoint.Utilities" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Register TagPrefix="asp" Namespace="System.Web.UI" Assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %>
<%@ Import Namespace="Microsoft.SharePoint" %>
<%@ Register TagPrefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages"
Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Control Language="C#" AutoEventWireup="true" CodeBehind="VisualWebPart1.ascx.cs"
Inherits="DocumentSetApp.VisualWebPart1.VisualWebPart1" %>
<center>
<div>
<table style="text-align: center">
<tr>
<td colspan="2">
<asp:label id="Label1" runat="server" text="DocumentSet - SharePoint 2010 Programatically using VS 2012"
font-bold="true" font-size="Large" font-names="Verdana" forecolor="Maroon"></asp:label>
</td>
</tr>
<tr>
<td>
<asp:label id="Label2" runat="server" text="Please Enter List Name" font-size="Large"
font-names="Verdana" font-italic="true"></asp:label>
</td>
<td>
<asp:textbox id="TextBox1" runat="server"></asp:textbox>
</td>
</tr>
<tr>
<td>
<asp:label id="Label3" runat="server" text="Please Enter DocumentSet Name" font-size="Large"
font-names="Verdana" font-italic="true"></asp:label>
</td>
<td>
<asp:textbox id="TextBox2" runat="server"></asp:textbox>
</td>
</tr>
<tr>
<td colspan="2">
<asp:button id="Button1" runat="server" text="Create Document Set" font-names="Verdana"
width="174px" backcolor="Orange" font-bold="True" onclick="Button1_Click" />
</td>
</tr>
<tr>
<td colspan="2">
<asp:label id="Label5" runat="server" font-bold="true" font-names="Verdana"></asp:label>
</td>
</tr>
</table>
</div>
</center>
Step 5
The complete code of visualwebpart1usercontrol.ascx.cs looks like this:
using Microsoft.Office.DocumentManagement.DocumentSets;
using Microsoft.SharePoint;
using System;
using System.Collections;
using System.ComponentModel;
using System.Web.
I.WebControls.WebParts;
namespace DocumentSetApp.VisualWebPart1
{
[ToolboxItemAttribute(false)]
public partial class VisualWebPart1 : WebPart
{
// Uncomment the following SecurityPermission attribute only when doing Performance Profiling 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))
{
Label5.Text = "Please Enter Some Values"; Label5.ForeColor = System.Drawing.Color.Red;
}
else
{
try
{
SPWeb web = SPContext.Current.Web; SPList list = web.Lists[TextBox1.Text];
if (list != null)
{
SPContentType contentType = web.ContentTypes["Document Set"];
if (contentType != null)
{
var hashTable = new Hashtable();
hashTable.Add("DocumentSet", "New Doc Setting"); hashTable.Add("CreatedBy", SPContext.Current.Web.CurrentUser.Name);
hashTable.Add("ModifiedBy", SPContext.Current.Web.CurrentUser.Name);
DocumentSet documentSet = DocumentSet.Create(list.RootFolder, TextBox2.Text, contentType.Id, hashTable,true);
documentSet.Item.ProgId = "SharePoint.DocumentSet"; documentSet.Item.Update();
}
}
}
catch (SPException ex)
{
Label5.Text = ex.Message;
}
Label5.Text = TextBox2.Text + " Document Set Created Successfully";
Label5.ForeColor = System.Drawing.Color.Green;
TextBox1.Text = string.Empty;
TextBox2.Text = string.Empty;
}
}
}
}
Step 6
Deploy the solution file and add the created webpart to SharePoint site.
Step 7
The output of the application looks like this:
![sharepoint2010output.png]()
Step 8
Entering document set data output of the application looks like this:
![createdocumentinsharepoint2010.png]()
Step 9
Document set create output of the application looks like this:
![documentsetcreateoutputinsharepoint2010.png]()