Aroh's Microsoft 365 Musings

Sunday, June 27, 2010

Enabling javascript IntelliSense in Visual Studio 2010 for SharePoint 2010

Hi all,

Its quite confusing when you develop a custom dialog box or customize ribbon control in SharePoint 2010 there is no javascript IntelliSense in VS 2010. Its easy to enable by adding referencing these JavaScript files on the top:

/// <reference name="MicrosoftAjax.js" />
/// <reference path="file://C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/14/TEMPLATE/LAYOUTS/SP.core.debug.js" />
/// <reference path="file://C:/Program Files/Common Files/Microsoft Shared/Web Server Extensions/14/TEMPLATE/LAYOUTS/SP.debug.js" />

Its a tip from Chakkardeep's blog.
In fact, its similar for Microsoft Ajax library where ASP.NET developers have to add a reference to the MicrosoftAjax.js to the JavaScript files.

/// <reference name="MicrosoftAjax.js"/>

Cheers,
--Aaroh

Friday, June 18, 2010

The solution cannot be removed when a job is scheduled or running.

Hi All,

While working for a custom feature which is a third party component for SharePoint. Somehow, I wanted to removed and eventually delete this feature. Surprisingly, when I tried rectract this feature via Central Admin, I got a an error.

BUG:
The solution cannot be removed when a job is scheduled or running.

After googling, someone had the same issue. What we have to do is follow these steps:

Open command prompt and enumerate the running deployments by executing this command:
stsadm -o enumsdeployments
Now, we obtain the jobid and cancel this deployement as follows:
stsadm -o canceldeployment -id 2529c788-971c-46a3-b69f-a2a0a1fcc851

That's it. We can then retract and delete the solution.

Cheers,
--aaroh

Friday, May 28, 2010

My tryst with groups and custom permissions programmatically in SharePoint 2007,

Hi all,

Of late, I had to work for a project where business needed custom groups and permissions to be provisioned. Well, working with creating custom groups/permissions programmatically is not cup of tea as concepts are quite involved.

Business requirement:

There are different set of groups which has to be hooked to a site and document library.

Group	Web permission	List permission
Manager	Can add users into different groups but can not create new group not add/edit/delete items in a document library. (Custom permission)	Read only
Author	Can add/edit/delete his/her own document but can not delete other's users document. (Event handler)	Contribute
Contributor	Can add/edit/delete document. (SharePoint OOTB permission)	Contribute
System Administrator	Has full control (SharePoint OOTB permission)	Full control

The SharePoint Security Model:

When we create site via "Central Admin" and choose Team or Blank template, by default SharePoint creates three groups as follows:

Group	Site Owners	Site Contributors	Site Visitor
Permission level	Full Control	Contributor	Read
Permissions	Contribute permissions + Manage Lists, Override checkout	Read permissions + Add, Edit, Delete items, delete versions	View, Open items, View versions, create alerts, View Application pages

NOTE:

1) Please note if we create sites programmatically, the default groups will be not present.

We have to create these groups programmatically via code.

2) When we develop our custom groups or role definitions, its most important that we have to "RunWithElevatedPrivileges" which is a delegate method that run with elevated privileges. This method runs under "Application pool" identity.

Caveat!!

Daniel Larson does NOT recommend RunWithElevatedPrivileges method in the object model but use "SPUserToken" to impersonate. Also, check out this blog where author has elevated the privileges without using RunWithElevatedPrivileges method.

Creating groups programmatically:

I have to develop groups and permissions in a separate classes so that even the permission have been changed groups part is intact. In my scenario, I have 4 SharePoint Groups and Manager group is the one who can create add/remove users in any of 4 SharePoint groups but he/she could be delete any lists and should have access to the lists as read-only access.

I have defined a GroupHelper class, which create a those 4 SharePoint groups. When I provided my custom SharePoint group and added a user named "local1Manager" who is in "Manager" (SharePoint Group). When I logged in as "local1Manager", I was not able to add any user in any SharePoint Group such as Manager, Contributor, System Administrator and Author. SharePoint displayed this message:

You do not have permission to view the membership of the group

I also looked at one of person who had same issue. Apparently, when we create a SharePoint site, three SharePoint groups are provided by default (Site Owners, Site Members and Site Visitors). These groups have a permission level (Full Control/Contribute/Read)

Group	Permission level	Group Owner
Site Owners	Full Control	Site Owners
Site Members	Contribute	Site Owners
Site Visitors	Read	Site Owners

This means, that Site Owner MUST BE group owner for all the groups as well.

By default, when we create the groups programmatically, the group owner will be always "System Account". But I wanted to give this role to my own custom SharePoint Group (Manager) and explicitly assign the group owner as "Manager" for all 4 custom SharePoint Groups.

The bottom line is that, when we create groups programmatically and in one of the group such as "Manager" who want to add users to some other groups then, we MUST explicitly assign the group owner as manager for all other SharePoint groups.

Following is the code:

Receiver Code

-----------------------------------------------------------------------

namespace Company.SiteProvisioning

{

class CompanyGroups : SPFeatureReceiver

{

public override void FeatureActivated(SPFeatureReceiverProperties properties)

{

//Get the web instance

using (var web = properties.Feature.Parent as SPWeb)

{

if (null != web)

{

#region 1) Creating the Custom Groups here

GroupsHelper.CreateGroups(web);
#endregion

}

}

---------------------------------------------------------------------------

GroupHelper.cs
--------------------------------------------------------------------------

namespace Company.Common.Utilities

{

public class GroupsHelper

{

#region Methods

/// <summary>

/// This function creates all the Company groups

/// </summary>

/// <param name="web">The web where groups have to be created.</param>

public static void CreateGroups(SPWeb web)

{

SPGroup group;

try

{

                #region 1) For Manager (Manager will be "Group Owner" for other custom SharePoint groups)
   if (!SPUtility.GroupExists(web, Groups.ManagerName))
                                {

                                      #region i) Create an Company Group

web.SiteGroups.Add(Groups.ManagerName, web.Site.Owner, web.Site.Owner, Groups.ManagerDescription);

group = web.SiteGroups[Groups.ManagerName];

#endregion

#region ii) Bind the web to the associated groups

web.AssociatedGroups.Add(group);

web.Update();

#endregion

#region iii) Assign the custom group owner to be "Manager"

group.Owner = web.SiteGroups[Groups.ManagerName];

group.Update();

#endregion

}

// DO THE SAME STUFF OF OTHER 3 CUSTOM SharePoint Groups

}

--------------------------------------------------------------------------------------------------------------

Theory of SharePoint security, Role definitions, Role Types, Role assignments and ISecurableobject:

SharePoint 2007 technologies is on top of and depends on the security of underlying technologies such as:
>> ASP.NET
>> IIS 6/7
>> SQL Server 2005/2008/2008 R2
>> Windows server 2003/2008
as well firewall configuration.

Any web application for SharePoint site is only as secure as its weakest link and therefore security is a concern across all the components of our SharePoint 2007 deployment. Security is addressed at different levels in SharePoint that includes:
>>Organization's security policies
>>SharePoint Product and Technology configuration
>> Windows Server 2003/2008 configuration
>> IIS configuration
>> ASP.NET configuration
>> communication configuration etc.

SharePoint product and technology make use of a number of technologies so that it mitigates the risk of security being comprised.

Authentication that uses Windows principles (authentication methods, password policies, encryption etc.)
Authorization that is based on the permission model to ensure a high level of granular control over access to contents of a site.
Code access security (CAS)
Security techniques (such as Secure Sockets Layer (SSL, HTTPS://))

WSS 3.0 security and permission model is role-based.

a) Role Definition (Permission level):
A role definition is a collection of rights which are hooked up to a user or a SharePoint group. They have following definitions:

>> Full Control (Administrator)

>> Contribute

>> Read

>> Design

>> Limited access

We can develope your own custom permission which I will use for "Manager". Manager can add users but he/she CAN NOT create a new group neither he/she can add/edit/delete documents.

Its obviously not an OOTB permission. I have created a new class named "Permission.cs" which just details all the permissions. Later, if the business needs the permission to be altered then we have to change in just one file i.e. Permissions.cs

If we deep dive into the SharePoint's object model, SPRoleDefinition defines a single role definition, including a name, description, management properties, and a set of rights.

Permissions.cs
-------------------------------------------------------------------------------------------------------------------

using System.Linq;

using Microsoft.SharePoint;

using Company.Common.Utilities;

namespace Company.Common.Constants

{

public static class Permissions

{

#region i) Permissions for the Manager

public static SPRoleDefinition ManagerWebPermission (SPWeb web)

{

if (!SPUtility.IsRoleDefinitionExists(Groups.ManagerName,web))

{

#region i) Create a custom permission level

SPRoleDefinition roleDefinition = new SPRoleDefinition

{

Name = Groups.ManagerName,

Description =

Groups.ManagerDescription,

BasePermissions =

SPBasePermissions.FullMask ^

(SPBasePermissions.ManagePermissions |

SPBasePermissions.ManageLists |

SPBasePermissions.AddListItems |

SPBasePermissions.EditListItems |

SPBasePermissions.DeleteListItems |

SPBasePermissions.ViewVersions |

SPBasePermissions.DeleteVersions |

SPBasePermissions.CreateAlerts |

SPBasePermissions.CreateGroups)

};

#endregion

#region ii) Create a custom permission and bind it to the web

web.RoleDefinitions.Add(roleDefinition);

web.Update();

#endregion

}

web.AllowUnsafeUpdates = true;

SPRoleDefinition userManagerRoleDef = web.RoleDefinitions

.Cast<SPRoleDefinition>()

.First(def => def.Name == Groups.ManagerName);

//SPRoleDefinition userManagerRoleDef = web.RoleDefinitions[Groups.ManagerName];

web.AllowUnsafeUpdates = false;

return userManagerRoleDef;

}

public static SPRoleDefinition ManagerListPermission (SPWeb web)

{

return web.RoleDefinitions.GetByType(SPRoleType.Reader);

}

#endregion

#region ii) Permissions for the Document Author

public static SPRoleDefinition DocAuthorWebPermission(SPWeb web)

{

return web.RoleDefinitions.GetByType(SPRoleType.Reader);

}

public static SPRoleDefinition DocAuthorListPermission(SPWeb web)

{

return web.RoleDefinitions.GetByType(SPRoleType.Contributor);

}

#endregion

}

}
}

--------------------------------------------------------------------------------------------------------------------------

Let's discuss the code above. SPBasePermissions defines all the built-in permissions which available SharePoint. These base permissions are extremely powerful and we can customize the permissions as we want. In the code above I have defined SPBasePermission.FullMask means for Manager who has full rights. But he do not want to give permissions full rights as he can not delete/add/edit rights. Therefore, use "^" operator to negate those permissions. Please refer how to use these operators.

After the we have defined a custom permission level, we need to bind this permission to the web

web.RoleDefinitions.Add(roleDefinition);

web.Update();

While developing the code, I found a bug which I have commented.

//SPRoleDefinition userManagerRoleDef = web.RoleDefinitions[Groups.
ManagerName];

When I debugged the code, I got this bug.

BUG: Microsoft.SharePoint.SPException: You cannot grant a user a permission level that is not attached to a web. at Microsoft.SharePoint.SPRoleDefinitionBindingCollection.AddInternal(SPRoleDefinition roleDefinition)
at Microsoft.SharePoint.SPRoleDefinitionBindingCollection.Add(SPRoleDefinition roleDefinition)

ISSUE: It may be because SharePoint doesn’t allow you to use the SPRoleDefinition you just created and you have to return the one you just added.

FIX:
a) using System.Linq
b) SPRoleDefinition userManagerRoleDef = web.RoleDefinitions

.Cast<SPRoleDefinition>()

.First(def => def.Name == Groups.ManagerName);

it will fix this issue.

b) Role Assignment: We have defined a custom permission level that is bound to the web. But, now we have to bind this permission level to the user or the SharePoint group. This can be achieved by leveraging the role assignment. The SPRoleAssignment class defines the role assignments for a user or group on the current object.

The RoleAssignment property comes with an interface named: ISecurableObject. This interface is extremely useful as we can implement by the SharePoint:
SPWeb,
SPList,
SPListItem classes.
Have a look onto its implementation at this URL.

Therefore, I added one more function as follows:

GroupHelper.cs
-----------------------------------------------------------------------------------------------------------

/// <summary>

/// This function assigns the permissions to the web or to the list.

/// </summary>

/// <param name="web">The web</param>

/// <param name="securableObject">Securable object which could be a web, list or list item</param>

/// <param name="principal">Principal could be a group or an individual user.</param>

/// <param name="roleDefinition">The permission level bound to a specific user or group</param>

public static void AssignPermissions(SPWeb web, ISecurableObject securableObject, SPPrincipal principal, SPRoleDefinition roleDefinition)

{

//Assign the role to group/users

SPRoleAssignment roleAssignment;

//SPList list;

try

{

if (securableObject.GetType().Name == "SPWeb")

{

web.AllowUnsafeUpdates = true;

#region i) Get an SPPrincipal (Group/Users) and assign custom permission level

// create a new role assigment for the group/users

roleAssignment = new SPRoleAssignment(principal);

//bind the role assignment to the role definition

roleAssignment.RoleDefinitionBindings.Add(roleDefinition);

#endregion

#region ii) Bind the role assignment to the web, associate the group to the web and update

//bind the role assignment to the web, associate the group to the web and update

web.RoleAssignments.Add(roleAssignment);

web.AssociatedMemberGroup = (SPGroup) principal;

web.Update();

#endregion

#region iii) Assign the role assigment to the securableObject

securableObject.RoleAssignments.Add(roleAssignment);

#endregion

web.AllowUnsafeUpdates = false;

}

if(securableObject.GetType().Name == "SPDocumentLibrary")

{

web.AllowUnsafeUpdates = true;

#region i) Check if the Doc Lib has unique permissions or not.

if (!securableObject.HasUniqueRoleAssignments)

{

securableObject.BreakRoleInheritance(true);

}

#endregion

#region ii) Get the reference of role assignment to the SPPrincipal(Group), Bind role assigment to roledefintion

roleAssignment = new SPRoleAssignment(principal);

roleAssignment.RoleDefinitionBindings.Add(roleDefinition);

#endregion

#region iii) Bind the role assigment to the securableObject

securableObject.RoleAssignments.Remove(principal);

securableObject.RoleAssignments.Add(roleAssignment);

#endregion

web.AllowUnsafeUpdates = false;

}

catch (Exception ex)

{

SPUtility.LogToULS(ex);

}

#endregion

------------------------------------------------------------------------------

This functions come with 4 parameters:
AssignPermissions(SPWeb web, ISecurableObject securableObject, SPPrincipal principal, SPRoleDefinition roleDefinition)

SPWeb: The Web object we pass in the feature receiver.
ISecurablObject: The web, SPList or the ListItem parameter and therefore gives flexibility in the code.
SPPrincipal: A SharePoint user or a group.
SPRoleDefinition: The custom permission level which is pre-defined.

Once we are defined with custom SharePoint groups permissions, we complete out code for the feature receiver.

Receiver Code

-----------------------------------------------------------------------

namespace Company.SiteProvisioning

{

class CompanyGroups : SPFeatureReceiver

{

public override void FeatureActivated(SPFeatureReceiverProperties properties)

{

//Get the web instance

using (var web = properties.Feature.Parent as SPWeb)

{

if (null != web)

{

#region 1) Creating the Custom Groups here

                    GroupsHelper.CreateGroups(web);
#endregion

                     SPSecurity.RunWithElevatedPrivileges(delegate

{

#region 2) Assign the permission to the groups. Permissions to the web and to the list

SPGroup grp;

//SPRoleDefinition roleDefinition;

#region i) Manager

grp = web.SiteGroups[Groups.rManagerName];

GroupsHelper.AssignPermissions(web, web, grp,

Permissions.WebPermission(web));

GroupsHelper.AssignPermissions(web, web.Lists[Register.ListDocLibName], grp,

Permissions.ManagerListPermission(web));

#endregion

#region ii) Doc Author

grp = web.SiteGroups[Groups.DocAuthorName];

GroupsHelper.AssignPermissions(web, web, grp,

Permissions.DocAuthorWebPermission(web));

GroupsHelper.AssignPermissions(web, web.Lists[Register.ListDocLibName], grp,

Permissions.DocAuthorListPermission(web));

#endregion

}

}

Note that in permissions.cs we have defined custom permission level for Manager on the web but reader permission on the lists. Whereas, author/contributor has read only access to the web but contributor permission to the list.

I guess, these sample codes will give an idea on SharePoint groups and permissions.

Cheers,
--aaroh

References:
BUG: You cannot grant a user a permission level that is not attached to a web.
BUG: You do not have permission to view the membership of the group
SharePoint Groups and Permissions concepts (Reza)
Sample codes for groups/permissions
SPRoleDefinition class, SPRoleAssignment class, SPBasePermissions class, ISecurableObject 1, ISecurableObject 2

Sunday, May 16, 2010

How to: Displaying SharePoint List Data by using the SPGridView Control in SharePoint 2007

Hi all,

In my one of the blog posts, I had demonstrated a simple SPGridView which hosts in SharePoint 2007. Its possible to bind the SharePoint list data onto the SPGridView which has similar SharePoint look and feel. Some other functions such as pagination, sorting, filtering, groups etc are possible as well. Lets dive into this simple walk-through. I will extend the same "CustomAppPageGrid" project.

Step1: Open the "CustomAppPageGrid" project >> On "LAYOUTS" folder, right click >> Add >> New Item >> Choose "Web Form" >> Name: AppPage2.aspx

Step2: Copy all the elements of AppPage.aspx to AppPage2.aspx. It should look this:

AppPage2.aspx
--------------------------------------------------------------------------------------

<%@ Page Language="C#" MasterPageFile="~/_layouts/application.master" AutoEventWireup="true" Inherits="CustomAppPage.AppPage2, CustomAppPage, Version=1.0.0.0, Culture=neutral, PublicKeyToken=fe057018f74cd3a4" %>

<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Import Namespace="Microsoft.SharePoint" %>

<%--Control Place Holder--%>
<asp:Content ID="PageTitle" runat="server" contentplaceholderid="PlaceHolderPageTitle" >
   Customer Page Title
</asp:Content>

<asp:Content ID="PageTitleInTitleArea" runat="server"
             contentplaceholderid="PlaceHolderPageTitleInTitleArea" >
   Customer Title Area
</asp:Content>

<asp:Content ID="Main" runat="server" ContentPlaceHolderID="PlaceHolderMain">
    Custom SPGridView2

   <SharePoint:SPGridView
   runat="server"
   ID="GridView1"
   AutoGenerateColumns="false"
   RowStyle-BackColor="#DDDDDD" />

</asp:Content>
--------------------------------------------------------------------------------------------------

AppPage2.aspx.cs
---------------------------------------------------------------------------------------------------

using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;

namespace CustomAppPage
{
     public partial class AppPage2 : Page
    {

        protected void Page_Load(object sender, EventArgs e)
        {
            if (!IsPostBack)
            {
                #region 1. Creating new fields (columns) to the Grid

                //Creating new fields (columns) to the Grid
                SPGridViewHelper.AddField("Name", "Name", GridView1);
                SPGridViewHelper.AddField("Type", "Type", GridView1);

                #endregion

            }
        }

        protected override void CreateChildControls()
        {
            base.CreateChildControls();

            #region 2. Binds the SharePoint list to the Grid

            SPSite site = new SPSite("http://localhost/sites/Demo/");
            SPWeb web = site.OpenWeb();

            SPList list = web.Lists["Shared Documents"];

            SPGridViewHelper.BindListToGrid(site, list, GridView1);

            #endregion

        }

    }
}
---------------------------------------------------------------------------------------------------

This example, we are inheriting from PAGE class.

Step3: Under Utility folder, we create a new Helper class which will facilitate us to create and we call it SPGridViewHelper2.cs

The code for this helper class will illustrated below:
SPGridViewHelper2.cs
------------------------------------------------------------------------------
using System.Data;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using System.Web.UI.WebControls;

namespace CustomAppPage
{
    public class SPGridViewHelper
    {

        /// <summary>
        /// Creates a new column in the SPGridView
        /// </summary>
        /// <param name="dataField">The data field</param>
        /// <param name="headerText">The header text</param>
        /// <param name="grid">The Grid</param>
        public static void AddField(string dataField, string headerText, SPGridView grid)
        {
            BoundField columnName = new BoundField();
            columnName.DataField = dataField;
            columnName.HeaderText = headerText;

            grid.Columns.Add(columnName);

        }

        /// <summary>
        /// Binds the list the SPGridView
        /// </summary>
        /// <param name="spSite">The SPSite</param>
        /// <param name="spList">The SPList</param>
        /// <param name="grid">The grid</param>
        public static void BindListToGrid(SPSite spSite, SPList spList, SPGridView grid)
        {
            using(SPSite site = spSite)
            {
                using (SPWeb web = site.OpenWeb())
                {
                    SPList list = spList;
                    SPDataSource dataSource = new SPDataSource();
                    dataSource.List = list;

                    grid.DataSource = dataSource;
                    grid.DataBind();
                }
            }
        }

    }
}
------------------------------------------------------------------------------
Lets look at the functions below:

AddField(string dataField, string headerText, SPGridView grid):
This helper function take two string parameters and the SPGridView as parameter. When we are creating columns in the Grid, we have to supply two parameters named DataField and HeaderText. We can leverage the Utility class to create these columns and pass in the SPGridView as an additional parameter.

BindListToGrid(SPSite spSite, SPList spList, SPGridView grid):
This function take three parameter: SPSite, SPList, SPGridView.For bind this SharePoint list, we need to pass in the site, and the list which we want to attach to the grid. We then create an instance of SPDataSource which will be the data source for the grid and eventually bind to the list.

Deploy and test the solution

Step4: The Pagination

We can also do some kind of pagination of our grid. SPGridView comes different events such as PageIndexChanging, Sorting etc. through which we can give end users a better visual appeal. Lets create another application page named "AppPage3.aspx" page.

AppPage3.aspx
------------------------------------------------------------------------------------------------
<%@ Page Language="C#" MasterPageFile="~/_layouts/application.master" AutoEventWireup="true" Inherits="CustomAppPage.AppPage3, CustomAppPage, Version=1.0.0.0, Culture=neutral, PublicKeyToken=fe057018f74cd3a4" %>

<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
<%@ Import Namespace="Microsoft.SharePoint" %>

<%--Control Place Holder--%>
<asp:Content ID="PageTitle" runat="server" contentplaceholderid="PlaceHolderPageTitle" >
   Customer Page Title
</asp:Content>

<asp:Content ID="PageTitleInTitleArea" runat="server"
             contentplaceholderid="PlaceHolderPageTitleInTitleArea" >
   Customer Title Area
</asp:Content>

<asp:Content ID="Main" runat="server" ContentPlaceHolderID="PlaceHolderMain">
    Custom SPGridView3

   <SharePoint:SPGridView
   runat="server"
   ID="GridView1"
   AutoGenerateColumns="false"
   RowStyle-BackColor="#DDDDDD" />

</asp:Content>
------------------------------------------------------------------------------------------------

AppPage3.aspx.cs
------------------------------------------------------------------------------------------------
using System;
using System.Collections;
using System.Configuration;
using System.Data;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.HtmlControls;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;

namespace CustomAppPage
{
    public partial class AppPage3 : System.Web.UI.Page
    {
        private DataView dv;

        protected void Page_Load(object sender, EventArgs e)
        {
            if (!IsPostBack)
            {

                #region 1. Creating new fields (columns) to the Grid

                //Creating new fields (columns) to the Grid
                SPGridViewHelper.AddField("Name", "Name", GridView1);
                SPGridViewHelper.AddField("Type", "Type", GridView1);                #endregion


            }
        }

        protected override void CreateChildControls()
        {
            base.CreateChildControls();

            #region 2. Binds the SharePoint list to the Grid

            SPSite site = new SPSite("http://localhost/sites/Demo/");
            SPWeb web = site.OpenWeb();
            SPList list = web.Lists["Shared Documents"];

            DataTable dt = list.Items.GetDataTable();
            dv = new DataView(dt);

            SPGridViewHelper.BindListToGrid(site, list, GridView1);

            #endregion

            #region 3. Paging

            //Paging
            GridView1.PageSize = 5;
            GridView1.AllowPaging = true;
            GridView1.PageIndexChanging += new GridViewPageEventHandler(GridView1_PageIndexChanging);
            GridView1.PagerTemplate = null;

            GridView1.DataBind();
            #endregion

            #region 4. Sorting
            //Sorting

            GridView1.AllowSorting = true;
            GridView1.Sorting += new GridViewSortEventHandler(GridView1_Sorting);
            #endregion

        }

        void GridView1_Sorting(object sender, GridViewSortEventArgs e)
        {
            var sortDirection = SortDirection.Ascending;

            string lastExpression = "";
            if (ViewState["SortExpression"] != null)
                lastExpression = ViewState["SortExpression"].ToString();

            string lastDirection = "asc";
            if (ViewState["SortDirection"] != null)
                lastDirection = ViewState["SortDirection"].ToString();

            string newDirection = "asc";
            if (e.SortExpression == lastExpression)
                newDirection = (lastDirection == "asc") ? "desc" : "asc";

            ViewState["SortExpression"] = e.SortExpression;
            ViewState["SortDirection"] = newDirection;

            if (newDirection == "asc")
            {
                sortDirection = SortDirection.Ascending;
            }
            else
            {
                sortDirection = SortDirection.Descending;
            }

            dv.Sort = e.SortExpression + " " + newDirection;
            GridView1.DataBind();

        }

        void GridView1_PageIndexChanging(object sender, GridViewPageEventArgs e)
        {
            GridView1.PageIndex = e.NewPageIndex;
            GridView1.DataBind();
        }
    }
}

------------------------------------------------------------------------------------------------

The events Paging and Sorting events are very similar as GridView in ASP.NET. Deploy and test