VIVEK KUMAR PANDEY

Programming in Sharepoint 2010

2012-11-06T21:38:00.000-08:00

Move Item and Document

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Data;
using System.IO;
using System.Configuration;
using System.Xml;
using System.Xml.Linq;
using Microsoft.SharePoint;
namespace BPCLContentArchival
{
    class MoveItemMethods
    {
        #region Global Variables
        private static string LogFilePath = ConfigurationManager.AppSettings["LogFileFolderPath"];
        private static string RecordListXML = ConfigurationManager.AppSettings["RecordListXML"];
        #endregion

        /// <summary>
        /// Logging is a method to add record in log Files
        /// </summary>
        /// <param name="exMessage">Pass Exception</param>
        /// <param name="functionName">Pass Meassage</param>
        private static void Logging(Exception exMessage, string functionName)
        {
            string FileName = Convert.ToDateTime(DateTime.Today).ToString("dd-MMM-yyyy");
            using (StreamWriter writer = File.AppendText(LogFilePath + "\\" + FileName + ".txt"))
            {
                writer.Write("\r\nLog Entry : ");
                writer.WriteLine("{0} {1}", DateTime.Now.ToLongTimeString(),
                    DateTime.Now.ToLongDateString());
                writer.WriteLine(" :");
                if (exMessage != null)
                {
                    writer.WriteLine("Source Function:{0}", functionName);
                    writer.WriteLine(" :{0}", exMessage.Message);
                    writer.WriteLine(" :{0}", exMessage.StackTrace);
                }
                else
                {
                    writer.WriteLine("Source Function:{0}", functionName);
                }
                writer.WriteLine("-------------------------------");
                // Update the underlying file.
                writer.Flush();
                // Close the writer and underlying file.
                writer.Close();
            }
        }
        /// <summary>
        /// CreateListNameTableStructure is a method to Create DataTable Structure.
        /// </summary>
        /// <returns>Returns DataTable Structure</returns>
        public DataTable CreateListsNameTableStructure()
        {
            DataTable ListsName = new DataTable();
            DataColumn SiteUrl = new DataColumn("SiteUrl");
            DataColumn Source = new DataColumn("Source");
            DataColumn Destination = new DataColumn("Destination");
            DataColumn Type = new DataColumn("Type");
            try
            {
                /// Add Columns to DataTable.

                SiteUrl.DataType = System.Type.GetType("System.String");
                Source.DataType = System.Type.GetType("System.String");
                Destination.DataType = System.Type.GetType("System.String");
                Type.DataType = System.Type.GetType("System.String");
                ListsName.Columns.Add(SiteUrl);
                ListsName.Columns.Add(Source);
                ListsName.Columns.Add(Destination);
                ListsName.Columns.Add(Type);
                Console.WriteLine("CreateListsNameTableStructure() : Create DataTable Structure.");
                Logging(null, "CreateListsNameTableStructure() : Create DataTable Structure.");

            }
            catch (Exception ex)
            {
                Logging(ex, "Error in CreateListsNameTableStructure()");
            }
            finally
            {
                SiteUrl = null;
                Source = null;
                Destination = null;
                Type = null;
            }
            return ListsName;
       }
        /// <summary>
        /// ReadRecordXMl is a method to read values from XML File
        /// And Add values in DataTable
        /// </summary>
        /// <returns>Returns DataTable with values</returns>
        public DataTable ReadRecordXML()
        {
            //RecordListXML = "RecordListNames.xml";
            string SiteUrl = string.Empty;
            string Source = string.Empty;
            string Destination = string.Empty;
            string Type = string.Empty;
            DataRow row;
            DataTable ListsName = CreateListsNameTableStructure();
            string xmlPath = Path.GetFullPath(Environment.CurrentDirectory) +"\\"+ RecordListXML;
            Console.WriteLine("ReadRecordXML() : Record List XML Path=" + xmlPath);
            Logging(null, "ReadRecordXML() : Record List XML Path=" + xmlPath);
            XDocument groupsXml = XDocument.Load(xmlPath);
            try
            {
                var fields = from fieldsGroup in groupsXml.Root.Elements("Field")
                             select new
                             {
                                 SiteUrl = fieldsGroup.Attribute("SiteUrl").Value,
                                 Source = fieldsGroup.Attribute("Source").Value,
                                 Destination = fieldsGroup.Attribute("Destination").Value,
                                 Type = fieldsGroup.Attribute("Type").Value
                             };
                ///Start of For Loop: Add row with values from xml to DataTable
                foreach (var fieldsGroup in fields)
                {
                    row = ListsName.NewRow();
                    row["SiteUrl"] = fieldsGroup.SiteUrl;
                    row["Source"] = fieldsGroup.Source;
                    row["Destination"] = fieldsGroup.Destination;
                    row["Type"] = fieldsGroup.Type;
                    ListsName.Rows.Add(row);
                }
                ///End of For Loop
                Console.WriteLine("ReadRecordXML() : Add values from XMl file to DataTable.");
                Logging(null, "ReadRecordXML() : Add values from XMl file to DataTable.");
            }
            catch (Exception ex)
            {
                Logging(ex, "Error in ReadRecordXML()");
            }
            finally
            {
                 SiteUrl = null;
                 Source = null;
                 Destination = null;
                 Type = null;
                 row = null;
                 xmlPath = null;
                 groupsXml = null;
            }
            return ListsName;
        }
        /// <summary>
        /// MoveToDocLib is a method to move Document from Source Library to Destination Library
        /// </summary>
        /// <param name="siteUrl">Pass Site url of SiteCollection</param>
        /// <param name="Source">Pass Source Library Name</param>
        /// <param name="Destination">Pass Destination Library Name</param>
        public void MoveToDocLib(string siteUrl, string Source, string Destination)
        {
            SPQuery qry = new SPQuery();
            string camlquery = string.Empty;
            string destlibUrl = string.Empty;
            SPListItemCollection Srccollitem;
            SPList destlib;
            SPFile moveFile;
            try
            {
                using (SPSite rootSite = new SPSite(siteUrl))
                {
                    using (SPWeb spWeb = rootSite.OpenWeb())
                    {
                        //TODO: only less than operator
                        camlquery = "<Where>"
                                          + "<Lt>"
                                          + "<FieldRef Name='Expiry_x0020_Date' />"
                                          + "<Value IncludeTimeValue='FALSE' Type='DateTime' ><Today /></Value>"
                                          + "</Lt>"
                                          + "</Where>";
                        qry.Query = camlquery;
                        ///Get the Collection of SourceLibraryDocument by Caml Query
                        Srccollitem = spWeb.Lists[Source].GetItems(qry);
                        destlib = (SPDocumentLibrary)spWeb.Lists[Destination];
                        destlibUrl = destlib.RootFolder.Url;
                        ///Start of ForEach Loop to Move Document one by one from Source List ot Destination List.
                        foreach (SPListItem item in Srccollitem)
                        {
                            moveFile = item.File;
                            Console.WriteLine("MoveToDocLib() : FileName=" + item.File.Name + ", SiteUrl=" + siteUrl + ", Source=" + Source + ", Destination=" + Destination);
                            Logging(null, "MoveToDocLib() : FileName=" + item.File.Name + ", SiteUrl=" + siteUrl + ", Source=" + Source + ", Destination=" + Destination);
                            moveFile.MoveTo(destlibUrl + "/" + moveFile.Name, true);
                        }
                        ///End of ForEach Loop
                    }
                }
            }
            catch (Exception ex)
            {
                Logging(ex, "Error in MoveToDocLib()");
            }
            finally
            {
                 qry = null;
                 camlquery = null;
                 destlibUrl = null;
                 Srccollitem=null;
                 destlib=null;
                 moveFile=null;

            }

        }
        /// <summary>
        /// MoveToList is a method to move Item from Source List to Destination List
        /// </summary>
        /// <param name="siteUrl">Pass Site url of SiteCollection</param>
        /// <param name="Source">Pass Source List Name</param>
        /// <param name="Destination">Pass Destination List Name</param>
        public void MoveToList(string siteUrl, string Source, string Destination)
        {
            SPQuery qry = new SPQuery();
            string camlquery = string.Empty;
            SPListItemCollection Srccollitem;
            SPList destlib;
            SPListItem item;
            SPListItem targetItem;
            try
            {
                using (SPSite rootSite = new SPSite(siteUrl))
                {

                    using (SPWeb spWeb = rootSite.OpenWeb())
                    {
                        camlquery = "<Where>"
                                           + "<Lt>"
                                           + "<FieldRef Name='Expiry_x0020_Date' />"
                                           + "<Value IncludeTimeValue='FALSE' Type='DateTime' ><Today /></Value>"
                                           + "</Lt>"
                                           + "</Where>";
                        qry.Query = camlquery;
                        ///Get the Collection of SourceListItem by Caml Query
                        Srccollitem = spWeb.Lists[Source].GetItems(qry);
                        destlib = spWeb.Lists[Destination];
                        ///Start of For Loop to move items one by one from Source List to Destination List
                        for (int i = Srccollitem.Count - 1; i >= 0; i--)
                        {
                            item = Srccollitem[i];
                            targetItem = destlib.Items.Add();
                            ///Start of ForEach Loop to add value of each Field from Source to Destionation
                            foreach (SPField f in item.Fields)
                            {
                                //Copy all except attachments.
                                if (!f.ReadOnlyField && f.InternalName != "Attachments"
                                    && null != item[f.InternalName])
                                {
                                    targetItem[f.InternalName] = item[f.InternalName];
                                }
                            }
                            ///End of ForEach Loop
                            Console.WriteLine("MoveToList() : ItemName=" + item.Name + ", SiteUrl=" + siteUrl + ", Source=" + Source + ", Destination=" + Destination);
                            Logging(null, "MoveToList() : ItemName=" + item.Name + ", SiteUrl=" + siteUrl + ", Source=" + Source + ", Destination=" + Destination);
                            spWeb.AllowUnsafeUpdates = true;
                            targetItem.Update();
                            item.Delete();
                            spWeb.AllowUnsafeUpdates = false;
                        }
                        ///End of For Loop.
                    }
                }
            }
            catch (Exception ex)
            {
                Logging(ex, "Error in MoveToList()");
            }
            finally
            {
                qry = null;
                camlquery = null;
                Srccollitem=null;
                destlib=null;
                item=null;
                targetItem=null;

            }

        }
        /// <summary>
        /// GetArchivalDetails is a method to get Data from DataTable.
        /// And according to Type it Call method to Move File/Item from 1
        /// Library/List to another Library/List.
        /// </summary>
        public void GetArchivalDetails()
        {
            DataTable dt;
            string siteurl=string.Empty;
            string Source=string.Empty;
            string Destination=string.Empty;
            string Type=string.Empty;
            try
            {
                Console.WriteLine("GetArchivalDetails() : Start Of Function.");
                Logging(null, "GetArchivalDetails() : Start Of Function.");
                dt = ReadRecordXML();
                ///Start of For Loop to get parameter use to move Item.
                for (int i = 0; i < dt.Rows.Count; i++)
                {
                    siteurl = dt.Rows[i]["SiteUrl"].ToString();
                    Source = dt.Rows[i]["Source"].ToString();
                    Destination = dt.Rows[i]["Destination"].ToString();
                    Type = dt.Rows[i]["Type"].ToString();
                    Console.WriteLine("GetArchivalDetails() : SiteUrl=" + siteurl + ", SourceListName=" + Source + ", DestinationListName=" + Destination + ", Type=" + Type);
                    Logging(null, "GetArchivalDetails() : SiteUrl=" + siteurl + ", SourceListName=" + Source + ", DestinationListName=" + Destination + ", Type=" + Type);
                    if (Type == "Library")
                    {
                        MoveToDocLib(siteurl, Source, Destination);
                    }
                    else if (Type == "List")
                    {
                        MoveToList(siteurl, Source, Destination);
                    }
                }
                ///End of for Loop.
                Console.WriteLine("GetArchivalDetails() : End Of Function.");
                Logging(null, "GetArchivalDetails() : End Of Function.");
            }
            catch (Exception ex)
            {
                Logging(ex, "Error in GetArchivalDetails()");
            }
            finally
            {
                 dt=null;
                 siteurl = null;
                 Source = null;
                 Destination = null;
                 Type = null;

            }

        }
    }
}

Tuesday, 28 February 2012

Use to add or remove user from site collection Administrator in c# in sharepoint

using System;
using System.Security.Permissions;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Security;
using Microsoft.SharePoint.Utilities;
using Microsoft.SharePoint.Workflow;
using Microsoft.SharePoint.Administration;
using System.Configuration;

namespace CCMListUserProject.EventRCCMListUser
{
    /// <summary>
    /// List Item Events
    /// </summary>
    public class EventRCCMListUser : SPItemEventReceiver
    {

        private string SiteUrl = ConfigurationManager.AppSettings["SiteURL"];
        private string AdminUrl = ConfigurationManager.AppSettings["AdminUrl"];
        private string ListName = ConfigurationManager.AppSettings["CCMListName"];
        private string DomainName = ConfigurationManager.AppSettings["DomainName"];
       /// <summary>
       /// An item is being added.
       /// </summary>
       public override void ItemAdding(SPItemEventProperties properties)
       {
           base.ItemAdding(properties);
       }

       /// <summary>
       /// An item is being deleted.
       /// </summary>
       public override void ItemDeleting(SPItemEventProperties properties)
       {
           if (properties.ListTitle.ToString() == ListName)
           {
               SPListItem _currentItem = properties.ListItem;

               using (SPSite spSite = new SPSite(SiteUrl))
               {
                   SPWebApplication spwebapp = new SPWebApplication();
                   spwebapp = spSite.WebApplication;
                   SPSiteCollection allsitecoll;
                   allsitecoll = spwebapp.Sites;
                   foreach (SPSite site in allsitecoll)
                   {
                       SPWeb web = site.OpenWeb();
                       string CCMUserName = DomainName + "\\" + _currentItem["CCMUserName"].ToString();
                       SPUser objSpuser = web.AllUsers[CCMUserName];
                       objSpuser.IsSiteAdmin = false;
                       web.AllUsers.Remove(CCMUserName);
                       SPSecurity.RunWithElevatedPrivileges(delegate()
                       {
                           web.AllowUnsafeUpdates = true;
                           objSpuser.Update();
                           web.AllowUnsafeUpdates = false;
                       });
                   }

               }
               using (SPSite spSite = new SPSite(AdminUrl))
               {

                   SPWeb web = spSite.OpenWeb();
                   string CCMUserName = DomainName + "\\" + _currentItem["CCMUserName"].ToString();
                   SPUser objSpuser = web.AllUsers[CCMUserName];
                   objSpuser.IsSiteAdmin = false;
                   web.AllUsers.Remove(CCMUserName);
                   SPSecurity.RunWithElevatedPrivileges(delegate()
                   {
                       web.AllowUnsafeUpdates = true;
                       objSpuser.Update();
                       web.AllowUnsafeUpdates = false;
                   });

               }
           }
           base.ItemDeleting(properties);
       }

       /// <summary>
       /// An item was added.
       /// </summary>
       public override void ItemAdded(SPItemEventProperties properties)
       {
           if (properties.ListTitle.ToString() == ListName)
           {
               SPListItem _currentItem = properties.ListItem;

               using (SPSite spSite = new SPSite(SiteUrl))
               {
                   SPWebApplication spwebapp = new SPWebApplication();
                   spwebapp = spSite.WebApplication;
                   SPSiteCollection allsitecoll;
                   allsitecoll = spwebapp.Sites;
                   foreach (SPSite site in allsitecoll)
                   {
                       SPWeb web = site.OpenWeb();
                       string CCMUserName = DomainName + "\\" + _currentItem["CCMUserName"].ToString();
                       web.AllUsers.Add(CCMUserName, "", "", "");
                       SPUser objSpuser = web.AllUsers[CCMUserName];
                       objSpuser.IsSiteAdmin = true;
                       SPSecurity.RunWithElevatedPrivileges(delegate()
                       {
                           web.AllowUnsafeUpdates = true;
                           objSpuser.Update();
                           web.AllowUnsafeUpdates = false;
                       });
                   }

               }
               using (SPSite spSite = new SPSite(AdminUrl))
               {

                   SPWeb web = spSite.OpenWeb();
                   string CCMUserName = DomainName + "\\" + _currentItem["CCMUserName"].ToString();
                   web.AllUsers.Add(CCMUserName, "", "", "");
                   SPUser objSpuser = web.AllUsers[CCMUserName];
                   objSpuser.IsSiteAdmin = true;
                   SPSecurity.RunWithElevatedPrivileges(delegate()
                   {
                       web.AllowUnsafeUpdates = true;
                       objSpuser.Update();
                       web.AllowUnsafeUpdates = false;
                   });

               }
           }
           base.ItemAdded(properties);
       }

       /// <summary>
       /// An item was deleted.
       /// </summary>
       public override void ItemDeleted(SPItemEventProperties properties)
       {
           base.ItemDeleted(properties);
       }

    }
}

Thursday, 5 January 2012

Terms & Conditions in my link

using System;

using Microsoft.SharePoint;

using Microsoft.SharePoint.WebControls;

using System.Configuration;

namespace BPCLIntralinkCustomPages.Layouts.BPCLIntralinkCustomPages

{

public partial class MyLinkTermsAndConditions : LayoutsPageBase

{

string siteUrl = ConfigurationManager.AppSettings["MyLinkURL"];

string listMyLinkAuditName = ConfigurationManager.AppSettings["MyLinkEntryAuditListName"];

string AdminModuleUrl = ConfigurationManager.AppSettings["AdminModuleUrl"];

string CCMUserName = ConfigurationManager.AppSettings["CCMUserName"];

protected void Page_Load(object sender, EventArgs e)

{

}

protected void btnAgree_Click(object sender, EventArgs e)

{

siteUrl = "http://sp2010unv:10000/sites/Test";

listMyLinkAuditName = "MyLinkEntryAuditList";

SPUser user = null;

SPWeb spWeb = null;

string userName = "";

SPSite site = null;

SPList list = null;

try

{

user = SPContext.Current.Web.CurrentUser;

userName = user.LoginName;

SPSecurity.RunWithElevatedPrivileges(delegate()

{

var loginName = userName.Split('\\');

site = new SPSite(siteUrl);

spWeb = site.OpenWeb();

list = spWeb.GetList(string.Concat(siteUrl, "/Lists/", listMyLinkAuditName));

SPListItem newItem = list.AddItem();

newItem["UserName"] = loginName[1].ToString();

newItem["Status"] = btnAgree.Text.ToString();

spWeb.AllowUnsafeUpdates = true;

newItem.Update();

spWeb.AllowUnsafeUpdates = false;

if (loginName[1].ToLower()== CCMUserName.ToLower())

{

Response.Redirect("http://cochovtapp/sites/mylink/SitePages/BPCLAdminPage.aspx");

}

else

{

Response.Redirect("http://cochovtapp/sites/mylink/SitePages/MyLink.aspx");

}

});

}

catch (Exception ex)

{

throw ex;

}

finally

{

user = null;

spWeb = null;

userName = null;

site = null;

list = null;

}

protected void btnDisagree_Click(object sender, EventArgs e)

{

siteUrl = "http://sp2010unv:10000/sites/Test";

listMyLinkAuditName = "MyLinkEntryAuditList";

SPUser user = null;

SPWeb spWeb = null;

string userName = "";

SPSite site = null;

SPList list = null;

try

{

SPSecurity.RunWithElevatedPrivileges(delegate()

{

user = SPContext.Current.Web.CurrentUser;

userName = user.LoginName;

var loginName = userName.Split('\\');

site = new SPSite(siteUrl);

spWeb = site.OpenWeb();

list = spWeb.GetList(string.Concat(siteUrl, "/Lists/", listMyLinkAuditName));

SPListItem newItem = list.AddItem();

newItem["UserName"] = loginName[1].ToString();

newItem["Status"] = btnDisagree.Text.ToString();

spWeb.AllowUnsafeUpdates = true;

newItem.Update();

spWeb.AllowUnsafeUpdates = false;

});

}

catch (Exception ex)

{

throw ex;

}

finally

{

user = null;

spWeb = null;

userName = null;

site = null;

list = null;

}

Remove User who complete the Document

using System;

using System.Security.Permissions;

using Microsoft.SharePoint;

using Microsoft.SharePoint.Security;

using Microsoft.SharePoint.Utilities;

using Microsoft.SharePoint.Workflow;

using System.Configuration;

namespace SharePointProject_RemoveUser.EventReceiver_RemoveUser

{

/// <summary>

/// List Item Events

/// </summary>

public class EventReceiver_RemoveUser : SPItemEventReceiver

{

private string libname = ConfigurationManager.AppSettings["MyDocumentLibraryName"];

private string docstatus = ConfigurationManager.AppSettings["MyDocumentLibraryDocStatus"];

private string docsharedmembers = ConfigurationManager.AppSettings["MyDocumentLibrarySharedMembers"];

private string docAuthor = ConfigurationManager.AppSettings["MyDocumentAuthor"];

/// <summary>

/// An item was updated.

/// </summary>

public override void ItemUpdated(SPItemEventProperties properties)

{

try

{

if (properties.ListTitle.ToString() == libname)

{

SPListItem _currentItem = properties.ListItem; /// Gets Items from listitem.

if (!string.IsNullOrEmpty(_currentItem[docstatus].ToString())) /// Check DocStatus not Empty.

{

if (_currentItem[docstatus].ToString().ToLower() == "completed") //// Check DocStatus is Completed

{

SPUser user = properties.Web.CurrentUser; // Getting Current User

string fieldValue = _currentItem[docsharedmembers].ToString(); ///Getting Mutiple Users from Shared Member.

string Author = _currentItem[docAuthor].ToString(); ///Getting Created by User.

SPFieldUserValueCollection users = new SPFieldUserValueCollection(_currentItem.Web, fieldValue); ///Collect Multiple Users.

SPFieldUserValueCollection AuthorUser = new SPFieldUserValueCollection(_currentItem.Web, Author); ///Collect created by User.

SPFieldUserValueCollection values = new SPFieldUserValueCollection(); ///Use to Store the Filter Users

///Use this condition for clearing shared members field if Author completed the status

if (AuthorUser[0].User.LoginName.ToString().ToLower() == user.LoginName.ToString().ToLower() && users.Count >= 0)

{

users.Clear();

_currentItem[docstatus] = _currentItem[docstatus].ToString();

_currentItem[docsharedmembers] = users;

}

else

{

/// Use condition to Remove users from shared members field .

foreach (SPFieldUserValue uv in users)

{

if (uv.User.LoginName.ToLower() != user.LoginName.ToLower())

{

values.Add(new SPFieldUserValue(properties.Web, uv.User.ID, uv.User.Name));

}

_currentItem[docstatus] = ""; ///empty the status field

_currentItem[docsharedmembers] = values;

}

_currentItem.Update();

}

catch (Exception)

{

// throw;

}

base.ItemUpdated(properties);

}

Create a Workflow using Visual Studio 2010

2012-11-05T02:43:00.001-08:00

Introduction

In this article we can experiment with creating a Workflow using Microsoft Visual Studio 2010. Visual Studio along with SharePoint 2010 Extensions provides sophisticated development tools to enable Workflow development.

Types of Workflows

There are basically two types of workflows inside Visual Studio:

Sequential Workflow
State Machine Workflow

Sequential Workflow once invoked continues execution until it is completed.
State Machine Workflow will have states persisted in between. The state could be continued execution between machine restarts.
In this example we are trying to create a Workflow which on activation updates the null Address column of the Manager list. (You need to have a Contact template named Manager.)
Step 1: Create Sequential Workflow Project
For the time being, we can start with a Sequential Workflow. Start Visual Studio and create a new project from the template SharePoint > Sequential Workflow.

In the next screen select the option Site Workflow as shown below:

In the next screen, leave the default option saying the user manually starts the Workflow. Click the Finish button to create the project.

You will get the following screen once the project is created.

Step 2: Create Activity
We need to create an Activity to perform our job.

What is an Activity?

A Workflow consists of a series of Activities. We can add Activities using the Toolbox. There are different types of Activities like Code Activity, SendEmail, etc. For our example we are using the more functional Code Activity.

Drag and drop a Code Activity from the toolbox. You can locate this from the v3.0 group inside Toolbox.

Step 3: Add code for the Activity
Now we need to add code for this Activity. Double click on the codeActivity1 item shown above. Place the following code in the appearing code view.

Collapse | Copy Code

private void codeActivity1_ExecuteCode(object sender, EventArgs e)
{
    using (SPWeb web = SPContext.Current.Web)
    {
        SPList list = web.Lists["Manager"];
        foreach (SPListItem item in list.Items)
        {
            if (item["Address"] == null)
            {
                item["Address"] = "PLEASE SET THE ADDRESS!";

                item.Update();
            }
        }
    }
}

Step 4: Build and Deploy the Solution
Now we are ready to build and deploy the solution. Right click on the solution and use the Build and Deploy command.

Step 5: Execute the Workflow inside SharePoint
Now we are ready to test the Workflow inside SharePoint. As the Workflow was created as a Site Workflow it will be accessible for all the Lists and Libraries. You can click the Lists link inside the site.

Now click on the Site Workflows link. You will get the following screen.

Before executing the Workflow, you need to create a Manager item with Address not assigned.
Click on the highlighted button and your workflow gets executed. Wait for a while and you can see the invalid manager record is updated with the message.

This concludes our article on Workflow using Visual Studio.

SharePoint 2010: Programming with Business Data Connectivity Model Using Visual Studio 2010

2012-11-05T02:42:00.000-08:00

Abstract: In this article, we will be discussing integration between SharePoint 2010 web site and External Data Source using Visual Studio 2010 Business Data Connectivity Model project template

SharePoint as a web application platform is becoming popular amongst various domains of application development. There are several requirements for integrating a SharePoint 2010 Web Site with an external system which consumes data. If a developer has a strong programming background using Visual Studio 2010, the SharePoint 2010 Templates integrated with VS2010 prove useful to provide such an integrated solution.
In today’s scenario, where SharePoint 2010 based applications are used for automation purpose, similar integration requirements are going to popup every now and then. In VS 2010, the ‘Business Data Connectivity Model’ project template allows developers to design solutions for SharePoint 2010 for External Data Source integration.

In this article, we will be discussing integration between SharePoint 2010 web site and External Data Source using VS 2010 capabilities. You may be having some doubts about whether to use SharePoint 2010 Designer or Visual Studio 2010 for external content types, so here are some differences between them:

SharePoint Designer 2010 directly connects to the SharePoint 2010 site and external content type is directly written in the business data store. Unlike SPS 2010 Designer, VS2010, creates a model file with extension “.bdcm”. This file defines all external content types. This file then gets packaged into the project output assembly and then gets deployed as .WSP file in SharePoint 2010.
VS 2010 allows External Content Types (having data provided by .NET assemblies), which makes the code in the assembly as a proxy for External Data communication. Such an approach allows developer to add custom security code, additional business rules for working with more than one data source at a time.

For this application, I am using an already existing site ‘hxxp://win-v04rsve054t/sites/ss’. The SQL Server Database used here is ‘Company’ and the table is as shown below

Working with External Data Communication using VS 2010

Step 1: Open VS2010 and Create a new Empty SharePoint Project, name it as ‘SPS_ECM_ProductList’.

Make this project as deploy as farm solution as shown below:

Step 2: In this project, right click and add a new Business Data Connectivity Model, name it as ‘ProductModel:

Once you click OK, a model gets generated as shown below:

If you have worked with ADO.NET Entity Framework, you will find a similar type of entity generated. The reason behind this similar type of representation is because the BDCM is based upon ADO.NET EF. The Identifier1 represents the primary or Identity for the Item from the source. The ReadList method is designed to return collection type of data from the source and ReadItem is defined to return a single record from the source.
Step 3: For this demo, we are going to use LINQ to SQL for connecting to SQL Server database and its ProductInfo table. On the project, right click and add a new LINQ to SQL class as shown below and name it as ‘ProductInfoDataModel’:

Complete the Database connectivity Wizard.

Step 4: Once the DataModel is available with us, it’s time to configure the BCDM. Rename ‘Entity1’ to ‘ProductInfo’ and ‘Identity1’ to ‘ProductID’ and set its type to Int32 as shown below:

The final design will be as shown below:

Step 5: Now is the time for us to define operations (methods) for BCDM. Open BDC Explorer and rename ‘ReadList’ to ‘ReadProductList’, Expand ‘ReadProductList’ and rename the returnParameter from ‘Entity1List’ to ‘ProductList’ as shown below:

This is an out return type from the method. Now right-click on ‘ProductList’ and select ‘properties’, as shown below:

Click on Type Name

Select ‘ProductInfo’, as the method returns a List of ProductInfo and keep the ‘Is Enumerable’ checkbox checked, which indicates that the collection will be returned from the method.
Expand ProductInfo and you will find ‘Identifier1’ and ‘Message’ properties there, so change them to ‘ProductInfo’ properties. Right-Click on ‘ProductInfo’ and select ‘Add Type Descriptor’ and add ProductID, ProductName,Manifacturer and Price in it and set its data types. The final design will be as shown below:

Step 6: Now repeat similar steps for ‘ReadItem’ method and rename it to ‘ReadProduct’. To define ‘id’ and ‘return’ parameter, copy the ProductInfo from ‘ReadProductList’ and paste in ‘returnParameter’ of ‘ReadProduct’. Just click on ‘Yes’ in the message box that appears

Also copy ‘ProductID’ from the returnParameter of the ReadProductList and paste it in the ‘id’ of the ‘ReadProduct’ method. You will see a similar message as shown above for replacing Type Descriptor, just click ‘Yes’

Step 7: Click on ‘ProductInfo’ in BDCM designer, the method info will be as shown below:

Step 8: Now we need to add Create, Update and Delete method. So click on the ‘Add to Method’ at the bottom:

You will get a List of methods:

Add Creator, Updater and Deleter methods and rename them as ‘CreateProductInfo’, ‘UpdateProductInfo’ and ‘DeleteProductInfo’

Step 9: Now its time for us to write the code for database connectivity and implement Create, Read, ReadList, Update and Delete methods. Now the question is how to configure the Database ConnectionString to BDCM and access it in code. Go to the BDC Explorer and select ‘LocalSystemInstances’, rename ‘ProductModel’ to ‘productModelDBConnect’, go to the properties and select ‘Custom Properties’ and add a connection string as shown below:

In the project, add a reference to ‘Microsoft.BusinessData’ assembly from the following path:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI\Microsoft.BusinessData.dll
Step 9: Open ‘ProductInfoService.cs’ and write the following code which performs CRUD operations:
using System;
using System.Collections.Generic;
using System.Linq;
using SPS_ECM_ProductList;
using Microsoft.BusinessData.SystemSpecific;
namespace SPS_ECM_ProductList.ProductModel
{
/// <summary>
/// All the methods for retrieving, updating and deleting data are implemented in this class file.
/// The samples below show the finder and specific finder method for Entity1.
/// </summary>
public class ProductInfoService : IContextProperty
{
internal string AccessConnectionString()
{
Microsoft.BusinessData.MetadataModel.Collections.INamedPropertyDictionary dictionary =
this.LobSystemInstance.GetProperties();
if (dictionary.ContainsKey("CompanyConnStr"))
{
return dictionary["CompanyConnStr"].ToString();
}
return null;
}
/// <summary>
/// This is a sample specific finder method for Entity1.
/// If you want to delete or rename the method think about changing the xml in the BDC model file as well.
/// </summary>
/// <param name="id"></param>
/// <returns>Entity1</returns>
public ProductInfo ReadProduct(int id)
{
ProductInfoDataModelDataContext objContext =
new ProductInfoDataModelDataContext(AccessConnectionString());
ProductInfo Product = objContext.ProductInfos.Single(p => p.ProductID == id);
return Product;
}
/// <summary>
/// This is a sample finder method for Entity1.
/// If you want to delete or rename the method think about changing the xml in the BDC model file as well.
/// </summary>
/// <returns>IEnumerable of Entities</returns>
public IEnumerable<ProductInfo> ReadProductList()
{
ProductInfoDataModelDataContext objContext =
new ProductInfoDataModelDataContext(AccessConnectionString());
return objContext.ProductInfos.ToList();
}
public ProductInfo CreateProductInfo(ProductInfo newProductInfo)
{
ProductInfoDataModelDataContext objContext =
new ProductInfoDataModelDataContext(AccessConnectionString());
objContext.ProductInfos.InsertOnSubmit(newProductInfo);
objContext.SubmitChanges();

ProductInfo Product =
objContext.ProductInfos.Single(p => p.ProductID == newProductInfo.ProductID);
return Product;
}
public void UpdateProductInfo(ProductInfo productInfo)
{
ProductInfoDataModelDataContext objContext =
new ProductInfoDataModelDataContext(AccessConnectionString());
ProductInfo Product = objContext.ProductInfos.Single(p => p.ProductID == productInfo.ProductID);
Product.ProductName = productInfo.ProductName;
Product.Manifacturer = productInfo.Manifacturer;
Product.Price = productInfo.Price;
objContext.SubmitChanges();
}
public void DeleteProductInfo(int productID)
{
ProductInfoDataModelDataContext objContext =
new ProductInfoDataModelDataContext(AccessConnectionString());
ProductInfo Product = objContext.ProductInfos.Single(p => p.ProductID == productID);
objContext.ProductInfos.DeleteOnSubmit(Product);
objContext.SubmitChanges();
}
public Microsoft.BusinessData.Runtime.IExecutionContext ExecutionContext
{
get;
set;
}
public Microsoft.BusinessData.MetadataModel.ILobSystemInstance LobSystemInstance
{
get;
set;
}
public Microsoft.BusinessData.MetadataModel.IMethodInstance MethodInstance
{
get;
set;
}
}
}

The above code shows that an interface ‘IContextProperty’ is implemented which can access the Business Data Connectivity service. The method ‘AccessConnectionString’ reads the ConnectionString from the ‘LocSystemInstance’ properties collection using the Key of the Connection string set in Step 8.
Step 10: Open Feature1.Template.xml and add the following Xml which helps in deploying the application on the web site.
<Properties>
<Property Key="SiteUrl" Value="hxxp://MyServer/sites/ss"/>
</Properties>
Step 11: Deploy the application and using F5 to run it. This will start the SharePoint web site. To display the ProductInfo List on the Quick launch, click on ‘Site Actions’ on the top-left and select ‘More Options’ as shown below

This action will open the ‘Create’ window. Select ‘Data’ from Filter type and select ‘External List’ as shown below:

Click on the ‘Create’ button. A new Window will open where you need to set the Name of the List and also choose the External Content type to use as the Data source for the list:

This will open the ‘External Content Type Picker’ window. Select ‘ProductModelDBConnect’ and click on ’OK’:

This takes you back to the previous window where you Click on ‘Create’ and a new List will be created on the Quick Launch bar of the site.
Step 13: Now to set the access rights from the SharePoint Site to External Data Source, add the current login user from the List and set its access rights. You can do this using the ‘Central Administration Web Site’. Select ‘Application Management’ > Service Applications > Manage Service Applications > Business Data Connectivity Service. Here Select ‘ProductInfo’ checkbox and click on ‘Set Objects Permissions ’:

Add the User and set his/her rights as shown below :

This is required because the connection will be made from your Web Site hosted in IIS, to the External Data Source using Business Data Connectivity Web Service. So to authenticate and authorize the user, we need to set the access rights. Click on Ok.
Step 14: Return to the site and click on the ‘ProductInfoList’ (note: Your application in VS2010 must be running). A List Data appears:

Now you can test your Insert, Update and Delete operations.
Note: You must deploy the project assembly created in VS2010 in GAC so that it can be used by Web Site for performing CRUD operations.
Conclusion: Using VS 2010 SharePoint template, it is easy to design more controlled source code for Business Data Connectivity model using sophisticated programming methodology. Here a developer has complete freedom to implement domain specific logic to establish connectivity to an external data system from the SharePoint Web site.

SharePoint 2010: Change the “Add New Item”

2012-11-04T22:46:00.000-08:00

The Goal

To change from “Add new item”:

to “Click here to add team tasks”:

ID’s used by web parts

Each web part has a different ID and some share a common ID. You will need to modify the following code examples with the ID used by your list. Note that some lists share the same ID, like Tasks and KPIs.
Note: Many of these IDs have changed in 2010!
If the ID you need is not in this table, display the web page with the web part, use the browser’s View Page Source option and search for the message text. Then look backward in the <A> tag and find the ID.

Web Part	Default message	ID for “.getElementById” in the code below
Announcements	Add new announcement	“idHomePageNewAnnouncement” (changed in 2010)
Links	Add new link	"idHomePageNewLink"
Calendar	Add new event	"idHomePageNewEvent"
Picture Library	Add new picture	“idHomePageNewItem” * (changed in 2010)
KPI List	Add new item	"idHomePageNewItem" * (changed in 2010)
Tasks	Add new item	"idHomePageNewItem" * (changed in 2010)
Project Tasks	Add new item	"idHomePageNewItem" * (changed in 2010)
Document Library	Add new document	"idHomePageNewDocument" (changed in 2010)
Wiki	Add new Wiki page	"idHomePageNewWikiPage" (changed in 2010)
Discussion	Add new discussion	"idHomePageNewDiscussion" (changed in 2010)
Custom List	Add new item	“idHomePageNewItem” * (changed in 2010)

* = Shared with another list

If there is only one “Add new” message on a page

I.e. there is only one web part on the page that uses that ID then we can use this simple code:

<script>
  document.getElementById("idHomePageNewItem").innerHTML="your new text goes here"
</script>

But the IDs won’t always work!

SharePoint can build pages with multiple elements with the same ID. This is not proper HTML, but, they do it…
So we will need something a little more complex:

<script>
var ttnA = document.getElementsByTagName('A');
for (var j=0; j<ttnA.length; j++)
{
  if (ttnA[j].id == 'idHomePageNewItem')
  {
    ttnA[j].innerHTML='your new text goes here'
  }
}
</script>

This code runs through all of the Anchor (<A>) tags in the page looking for the ones with the ID we need and then changes the text as needed.
What if you only wanted to change the second web part that uses that ID to a new message? Then try this:

<script>
var ttnA = document.getElementsByTagName('A');
var ttnCounter = 0;
for (var j=0; j<ttnA.length; j++)
{
  if (ttnA[j].id == 'idHomePageNewItem')
  {
    ttnCounter ++;
    if (ttnCounter == 2)
      { ttnA[j].innerHTML='your new text goes here' }
  }
}
</script>

Where should you add the code?

Add the code to the page using SharePoint Designer

Edit the page using SharePoint Designer
Find the “<asp:content” tag for PlaceHolderMain and then find the matching end tag (“</asp:content>”)
Just before the end tag, add the JavaScript listed above

Or add a Content Editor Web Part to the page
This is the easiest for testing, and does not require SharePoint Designer. In SharePoint 2007 this worked equally well for web part pages and View pages. In SharePoint 2010, adding a web part to a View page causes the View selector dropdown to be hidden, so the SharePoint Designer approach might be better for View pages. The CEWP works just fine for web part pages and the new “wiki style” home pages. The only got’ya is that they have removed the Source Editor button from the CEWP. If you use the Edit HTML button in the Ribbon you may find that your HTML and JavaScript gets modified by their editor. Best practice with the 2010 CEWP is to store your HTML and JavaScript in a text file in a library and then use the CEWP’s link to a file option.

Create a text file with the JavaScript code and upload to a library
In the library right-click the file, click Properties and copy the URL of the file
Add an Content Editor Web Part (CEWP) below the web part you want to customize
From the CEWP click web part’s dropdown arrow and click Edit Web Part
Paste the URL you copied into the Content Link box

Hide the “+” image?

If you want to get rid of the little icon just before the “New Item” text then just add one more line of code after where you change the message:
     ttnA[j].innerHTML='Click here to add team tasks';
     ttnA[j].previousSibling.previousSibling.style.display='none';

Hide the entire message?

No tricks needed! Just edit the web part and change the “Toolbar Type” to “No Toolbar”. (The “New” link we’ve been working with is the “Summary Toolbar”.)

Deploying a custom master page

2012-11-04T22:39:00.001-08:00

Deploying a custom master page in SharePoint 2010

Lately I’ve been playing around with Visual Studio 2010 tools for SharePoint. I’ve been trying to come up with examples on how to use each of the available item templates.
Today I created a Module. A module can be used to deploy files to your SharePoint environment and the scenario I came up with was to use a module to deploy a master page.

I started out by creating an Empty SharePoint project. This can have any name you like and it can be both a farm and a sandboxed solution
Next add an new item to the project and choose a module
You can rename the module if you want to, I will leave the name at Module1
After the module is created it contains an elements.xml file and a sample.txt file. The sample.txt file can be renamed to sample.master.

Project structure after adding a module and renaming the sample file to sample.master
I’m not a designer, so I wasn’t interested in creating a brilliant new design (good job, because I wouldn’t be able to do that!).
For the purpose of this example I just took the standard SharePoint 2010 master page contents.

Open up SharePoint Designer and open the site you are working on
Choose Master Pages on the left side
Open v4.master

Don’t let SharePoint fool you. There is a default.master, but this is the old SharePoint 2007 master page that is used if you perform a visual upgrade. When creating a site in SharePoint 2010 the master page that will be used by default is v4.master. I know it’s a bit confusing, but if you have been working with SharePoint for a while you won’t be surprised by this.

Copy the contents of v4.master and past them in your sample.master file in Visual Studio. Make the changes you want to.
Note how the elements.xml file has changed to reference the sample.master rather than the sample.txt

The contents of the elements.xml file

Make sure the module is added to a feature in your project that is scoped at the site (= site collection) level

You could stop here and this solution will deploy your sample.master master page to the master page gallery of your site collection.
This will not apply the master page to the site collection when the feature gets activated though. It will only make it available for selection.

If you the master page to be applied when the feature gets activated you right click on the Feature1 and you add an event receiver. This will add a feature receiver file to the feature.
In this file we will add some code that will apply the sample.master master page when the feature gets activated and it will apply the v4.master when the feature gets deactivated.

[Update 10/12/2010]: Code updated because of improperly disposed SPSite and SPWeb objects. Thanks Donald Hessing and Rhys for pointing it out.

Code used in the feature receiver
Now if you activate the feature the code in the feature receiver will run and will apply sample.master to the site. As you can see we change both the MasterUrl and the CustomMasterUrl. The MasterUrl is used on all pages that are not publishing pages. This means it is used on the pages in the sitepages library and on the pages in the _layouts directory like the settings page for instance. The CustomMasterUrl is only used on pages that are stored in the Pages library. This library is created when the SharePoint Server Publishing Infrastructure features is activated on the site collection and the SharePoint Server Publishing feature is activated on the site.
You can also use the SharePoint user interface to apply a new master page. The Site Master Page is the equivalent of the CustomMasterUrl and the System Master Page is what the object model calls the MasterUrl.

Changing the master page using the SharePoint user interface

How to embed the “Connect to Outlook” link in a page

2012-11-04T22:29:00.002-08:00

I need to put a link to the "Connect to Outlook" script on a SharePoint 2010 page. I have built the stssync:// URL that triggers the Outlook sync: stssync://sts/?ver=1.1&type=discussions&cmd=add-folder&base-url=[MyServer]&list-url=[MyList]&guid=[MyGUID]&site-name=[MySiteName]&list-name=[MyListName]
Now the link works fine when pasted in IE address bar. However, I can't add it to a Sharepoint page - if I try to use the "insert hyperlink" button Sharepoint will complain about the stssynch:// protocol "URL must be in the form of http://" (or something to that effect).
I have tried to add a regular link that change the URL by editing the page's HTML. However, Sharepoint removes the link on saving the page.
How can I add the stssync:// link to a page? Is there any simple way to somehow "wrap" it in http or something?

Answer :

You can add the following code to a Content Editor webpart or directly onto the page. After adding the CEWP, in the ribbon use Editing Tools > Format Text > Edit HTML source.

Code:

<script src="http://code.jquery.com/jquery-1.6.1.min.js"></script>
<script language="javascript" type="text/javascript">
  function replaceURL() {
    $('#outlookLink').attr('href','stssync://sts/?ver=1.1&type=discussions&cmd=add-folder&base-url=[MyServer]&list-url=[MyList]&guid=[MyGUID]&site-name=[MySiteName]&list-name=[MyListName]');
  }

  _spBodyOnLoadFunctionNames.push("replaceURL");
</script>
<a id="outlookLink" href="#">Link to Outlook</a>

Here's what it is doing:

Includes a reference to the jQuery library, which you can either do as in this example or you can download it to your site and include a reference to that location on your site instead.
replaceURL() uses the jQuery .attr() method to change the href attribute of the anchor tag with the url that you want.
_spBodyOnLoadFunctionNames.push() will call your function as soon as the page loads.
Your link should have an id which you refer to in your function. The href can be anything, since it gets modified by your function as soon as the page loads.

NOTE: You could use straight javascript instead of jQuery, but the syntax is more complicated.

How Themes work in SharePoint 2010

2012-11-04T22:24:00.003-08:00

Sharepoint 2010 having a different concept of themes then Sharepoint 2007. Sharepoint 2010 having a new theme engine. You can do cool things such as create a theme in PowerPoint, export it and then import it into SharePoint 2010, click apply and you got a custom theme. One aspect that I could not find documented is the definition of when you choose a color for a particular element what is it really changing?

If you modify the theme for a site you can use the picker to choose a OOTB or custom theme. Or you have the ability to choose your own color scheme via the following elements.

My approach: Make each element white to start with and then one by one add color and document the results. Just for kicks here is what it looks like when it is completely white… (not a color scheme I would recommend…) I will be using a red color: #C12345 for testing.

Here are the details for each one of the elements above:

Text/Background- Dark 1 (41 Classes)

Page Title Hyperlink Text
Hover Text
VB Body Text
Site Action Menu Text
Left Navigation Links Text
Site Setting Page Text Headers

Text/Background - Light 1 (37 Classes)

Body Background
Toolbar Background
Quick Launch Borders
Web Part Header Background
Site Action Menu Background
Site Action/Welcome Text Color
Pop-Up Window Background

Text/Background - Dark 2 (43 Classes)

Top Banner Background
Left Navigation Header Text
Recycle Bin/View All Site Content Text
I Like/Tags Notes Text
Library Column Text
Site Action Drop Down Border
Breadcrumb Current Location Text
List Description Text

Text/Background - Light 2 (19 Classes)

Browse Tab and hover Background
Title Container Background
Top Links/Header 2 Background
Quick Launch Background
Web Part Adder Background

Accent 1 (10 Classes)

Quick Launch Hover Text
Top Link Selected Tab

Accent 2 (4 Classes)

.ms-error
Rich Text Colored Heading 2 Text Styles

Accent 3 (9 Classes)

Rich Text “Caption” Style Text Color

Accent 4 (5 Classes)

Border Under Web Part Selector

Accent 5 (3 Classes)

Rich Text Colored Heading 4 Text Styles

Accent 6 (3 Classes)

Rich Text Highlight background color

Hyperlink (12 Classes)

Toolbar Text Color
VB Body Hyperlink Text
a:link Class Text Color
Web Part Title Hyperlink Text (Not Visited)

Followed Hyperlink (2 Classes)

.ms-WPBody a:visited
a:visited

I hope this post will help you when you decide to create your own theme via the above elements. If you create your own theme you can simply view the source of the page and there will be a unique CSS style sheet reference “_themes/16/corev4-8digithex.css?ctag=#”.

How to use RDLC with Asp.net?

2012-08-30T21:34:00.001-07:00

I just passed thru a situation where my client does require 2 reports to be developed in SSRS ( SQL Server Reporting Service ). It was not good advise to spend extra money behind SSRS on shared hosting as his requirement was very small. I show some example of RDLC (Report Definition Language Client-side) to my client and he was very excited about that.

I thought it’s nice to share this with all my blog readers and my friends.

Introduction

Step : 1 Create a Parameterized Store Procedure.

(I have used table called ProjectDetail for this tutorial )

CREATE PROCEDURE [dbo].[ReportProjectDetail]

(

@ProjectID INT=NULL ,

@FromDate DATE=NULL,

@ToDate DATE=NULL

)

BEGIN

SET NOCOUNT ON;

BEGIN TRY

SELECT ProjectID,

ProjectName,

ClientName,

ProjectReqDate,

ProjectValue,

PartnerID,

PartnerType,

PartnerName,

PartnerEmail,

FundingID,

FundingStatus,

AmountRequested,

AmountRecieved,

SentFundTo,

FROM ProjectDetail

WHERE (@ProjectID =NULL or ProjectID=@ProjectID)

AND (@FromDate IS NULL OR CreatedOn BETWEEN @FromDate AND @ToDate)

END TRY

BEGIN CATCH

PRINT Error_Message()

DECLARE @msg VARCHAR(MAX)

SELECT @msg = ERROR_MESSAGE()

EXECUTE ERR_LogError

RAISERROR('Error in %s: %s', 16, 1, 'ReportProjectDetail',@msg)
END CATCH

END

Step : 2 Create a DataSet using the DataSet Designer

Start by running Visual Studio and select New Website from the Start page.
Add ASP.Net folder App_Code
In Solution Explorer Right Click on App_Code > Add new Item > DataSet
Now select DataSet & Give name. e.g. ds_ProjectDetail.xsd and Save.
Now Right Click anywhere in DataSet sceen and select Add from the context menu.
Select Table Adapter In to Wizard. Now create data table.
Now choose Existing Store procedures.

Step : 3 Create a report definition

In Soultion Explorer right click on & select > Add New Item > Reporting > Report
Now Given report name e.g. rptProjectDetail.rdlc Click Add to your project.
Now Drag a table from the report designer screen.
Now Dataset Properties has to be come in pop up now give your dataset name next choose your dataset next select available reports & last click OK.
The table has in three Bands, first header, second detail, & last footer bands.
After created your dataset, it will appear on your left panel in Website Data Source window.
Expand it and drag the file to the report designer page . For example, drag and place it in the Table Fields.
After you have assigned the attribute, now report creation is done.

Step : 4 Add Report Viewer control into your ASPX page

Step:-
- In Solution Explore Right click > Add new item >Web > Web Form now give name e.g. rdlcDemo.aspx and click on Add.
- Now Open your Left Side Toolbox and drag the Report Viewer control to your ASPX page (In Design mode).
- Once your have Drop n drag Control on aspx Webpage , select it and click on the arrow on the top right corner to choose your rdlcReport.rdlc report in dropdown list.
- Don’t Forget to add namespace Microsoft.Reporting.WebForms to be in your code-behind file.
using System;

using System.Configuration;

using System.Data;

using System.Data.Common;

using System.Web.UI;

using Microsoft.Practices.EnterpriseLibrary.Data;

using Microsoft.Practices.EnterpriseLibrary.Data.Sql;

using Microsoft.Reporting.WebForms;

using System.Collections.Generic;

using System.Linq;

using System.Web.UI.WebControls;

using System.Data;

using DataAccessLayer;

protected void GenerateReportButton_Click(object sender, EventArgs e)

{

ReportViewer1.Visible = true;
```
        string connectionString = ConfigurationManager.ConnectionStrings
```
```
["ConnectionStringName"].ConnectionString;
```
Database db = new SqlDatabase(connectionString);

DbCommand command = db.GetStoredProcCommand("ReportProjectDetail");

db.AddInParameter(command, "@ProjectID", DbType.String, ddlProject.SelectedValue);

if (calFromDate.Text.ToString() != "")

{

db.AddInParameter(command, "@FromDate", DbType.String, calFromDate.Text.ToString());

}

if (calToDate.Text.ToString() != "")

{

db.AddInParameter(command, "@ToDate", DbType.String, calToDate.Text.ToString());

}

DataSet dataset = db.ExecuteDataSet(command);

ReportDataSource datasource = new ReportDataSource("DataSet1", dataset.Tables[0]);

ReportViewer1.LocalReport.DataSources.Clear();

ReportViewer1.LocalReport.DataSources.Add(datasource);

ReportViewer1.LocalReport.Refresh();

}

}
Bind and Run The Report
```
Now  Press F5 to Run the .aspx page.
```
```
 
```

How to Create Custom SharePoint 2010 Page Layouts using SharePoint Designer 2010

2012-08-29T22:33:00.003-07:00

Scenario:

You’re working with the Enterprise Wiki Site Template and you don’t really like where the “Last modified…” information is located (above the content). You want to move that information to the bottom of the page.

Option 1: Modify the “EnterpriseWiki.aspx” Page Layout directly.

Option 2: Create a new Page Layout based on the original one and then modify that one.

We’ll go ahead and go with Option 2 since we don’t want to modify the out of the box template just in case we need it later on.

How To:

Step 1

Navigate to the top level site of the Site Collection > Site Actions > Site Settings > Master pages (Under the Galleries section). Then switch over to the Documents tab in the Ribbon and then click New > Page Layout.

Step 2

Select the Enterprise Wiki Page Content Type to associate with, give it a URL and Title. Note that there’s also a link on this page to create a new Content Type. You might be interested in doing this if you wanted to say, add more editing fields or metadata properties to the layout. For example if you wanted to add another Managed Metadata column to capture folksonomy aside from the already included “Wiki Categories” Managed Metadata column.

Step 3

SharePoint Designer time! Hover over your newly created Page Layout and “Edit in Microsoft SharePoint Designer.”

Step 4

Now you can choose to build your page manually by dragging your SharePoint Controls onto the page and laying them out as you’d like…

… Or you can copy and paste the OOB Enterprise Wiki Page Layout. I think I’ll do that.

Step 5

Alright, so you’ve copied the contents of the EnterpriseWiki.aspx Page Layout and now it’s time for some customizing. I found the control I want to move, so I’ll simply do a copy or cut/paste to the new spot.

Step 6

Check-in, publish, and approve the new Page Layout. Side note: I like to add the Check-In/Check-Out/Discard or Undo-Checkout buttons to all of my Office Applications’ Quick Access Toolbars for convenience.

Step 7

Almost there! Navigate to your publishing site, in this case the Enterprise Wiki Site, then go to Site Actions > Site Settings > Page layouts and site templates (Under Look and Feel). Here you’ll be able to make the new Page Layout available for use within the site.

Step 8

Go back to your site and edit the page that you’d like to change the layout for. On the Page tab of the Ribbon, click on Page Layout and select your custom Page Layout.

Et voila! You just created a custom Page Layout using SharePoint Designer 2010, re-arranged a SharePoint control and managed to plan for the future by not modifying the out of the box template. That was a really simple example but I hope it helped to give you some ideas on how else you can customize Page Layouts within SharePoint 2010!

Top 20 Examples of Creative Navigation within SharePoint

2012-08-29T22:04:00.001-07:00

With the launch of SharePoint 2010, I thought it might be fitting to start focusing on the design and branding element of SharePoint and show the world what can be done when you are thinking of being creating with the product.
Leading on from that I am doing to launch a series of Top 20′s ranging from search box examples , navigation examples and my favourite sites all based on the platform of SharePoint.
So to start the series off I am going to start with my Top 20 Examples of Creative Navigation, with a brief summary of why I like it. They are in no particular order and are the opinion of myself. Enjoy.
So then, let the showcase commence…
1. Carbon Trust

I really like the font they have used for starters and I think the hover state with the reverse colour is effective combined with the immediate show of the sub navigation, which has a subtle fade for the potential white-on-white scenario.
http://www.carbontrust.co.uk
————————————————————————————————————————————————
2. BSG Blog

I love this Silverlight navigation, orbiting around home/earth button is really cool. I always love the little touches of the shooting star, UFO that flies across and the twinkle of stars that happens every now and again. All in all and unique and very creative navigation that can be achieved with the combination of SharePoint and Silverlight.
http://blogs.bsg.co.uk
————————————————————————————————————————————————
3. Linklaters

I really like big and bold navigation as it is one of most important elements of any website – clear navigation. Looking at it now as a little picture your eyes are drawn to the logo and navigation instantly. This navigation uses drop down menu functionality with combined with the purple arrow and purple text in hover state just polishes is clean and simple example.
http://www.linklaters.com
————————————————————————————————————————————————
4. Central Ohio Technical College

One good way to gain your users attention is the use of animation. Too much can be overpowering and annoying but used subtly it can be a great way to get them clicking. This navigation I like because I did just that, I was hovering over all the menu options over and over, the animation is smooth and colourful.
http://www.cotc.edu
————————————————————————————————————————————————
5. Hyder Consulting

Something a bit different in terms of layout, on top of a large photo, which sometimes can make navigations lost within the background. One way to counter this is using a large navigation which I this site does well, combined with white text in hover state in the line of sight with the logo and search area, this site navigation works.
http://www.hyderconsulting.com
————————————————————————————————————————————————
6. Victorinox

The use of the burgundy background with the white navigation as well as the capitalisation of lettering works really effectively and even more so when reversed on the hover state. Leading on from this, the sub menu and the active menu state still using the reverse color of white background and burgundy hover state on the submenu polishes off this example perfectly.
http://www.victorinox.com
————————————————————————————————————————————————
7. Arts & Auto

I really like colour-categorised navigation, it is a simple way to break up and easily identify content within sections on your website. Not only have they done this and have incorporated a dropdown / sub menu with some navigation, in which when cooked together they’ve baked a nice piece of animation with a nice design.
http://www.artsenauto.nl
————————————————————————————————————————————————
8. Hyro

Sometimes when you have a clean site you don’t need to use a graphically heavy navigation. Also using a clean and crisp navigation can really complement a design, which this site does and does well. Not over the top, no animation just simple text with a simple hover state that of an underline. Simples
http://www.hyro.com
————————————————————————————————————————————————
9. Sdu Uitgever

Not my favourite of navigation examples but I think it is important to demonstrate something different and with that I respect. One thing all creative designers should be looking to do is think outside of the box and this navigation does.
http://www.sdu.nl
————————————————————————————————————————————————
10. SharePoint HQ

What I particularly like about this is the combination of colour palette (I love those blues), the animation and the bottom-right gradient they have used. Also what I think is good to recognise is the contrast of the menu with the background it sits on, creating enough contrast to make the user experience seamless without looking out of place.
http://www.sharepointhq.com
————————————————————————————————————————————————
11. Lutron

Having a site with a large navigation structure can be tricky to present in a clean and clear way, which isn’t busy and cluttered. This site does this perfectly! It is well presented and even incorporates a little bit of content in the sub menu pane. The only thing I think ruins, what could be a lovely example, is the animation for the sub menu pane, I think it very ‘choppy’ and quite violent on the eyes going from a brown palette in their photography then to be presented with a white background instantly. My opinion is that a nice piece of fade in/out animation would be perfect here.
http://www.lutron.com
————————————————————————————————————————————————
12. Central Ohio Technical College

Similar to Central Ohio Technical College further up, this is animating up instead of to the right, BUT with a little twist not only does this navigation animated up it also changes the image below based on what you option you have decided to hover over. Although it is flash and I think that it is cheating to use a flash menu on a SharePoint site, I like it and it is my blog so I will include! but this will be the only one I promise! I would like to think that CCB have used flash to tap into a list to power their navigation, if they have then then I suppose that’s a decent compromise.
http://www.ccb.pt
————————————————————————————————————————————————
13. Ferrari

If there is one colour that goes with a strong and vibrant color like red it is grey and in particular gun metal grey, one of my favourites. What I think makes this navigation really cool is that use of imagery on the drop down boxes to emphasis the area you are in and could head over to, I also like the animation that is used just tops off the whole navigation.
http://www.ferrari.com
————————————————————————————————————————————————
14. Safe Network

First thing I noticed on this navigation was the shadow that is used on the right/bottom of the drop down which really gives the sub menu definition. With a site that used big, bold colours the navigation supports this really well. I also like the way the top header and navigation sit on top of the image slider/view that is used behind the site.
http://www.safenetwork.org.uk
————————————————————————————————————————————————
15. Rado

Sometimes you just need to go back to the basics! The brand for this site is clearly black and white, using this they have kept their navigation simple, but with a twist. Using the sub menu they have added the functionality of when you hover over the different options you are presented with a visual representation, in this case a picture of the watch based on the what model you hover on. A perfect example of simplicity works.
http://www.rado.com
————————————————————————————————————————————————
16. Goodman

One thing I like is trying something different! Clever navigation based on their logo the ‘+’ (plus) sign really works well. Instantly identifiable with the logo you cant help but notice that Goodman use a + as there logo. Going back to the navigation you are clearly presented with 5 options which takes you to various areas. Once in those areas they use a standard navigation you see everywhere, shame really as their initial navigation is cool.
http://www.goodman.com
————————————————————————————————————————————————
17. Cox

This is a common trend I have seen where people use the navigation to tell people the sections they will be clicking on them and underneath what the section is about. It can be used really effectively sometimes but also can become a very busy as well on the flip side. Just wish they had a mute button for the woman…
http://www.coxhelpcenter.com
————————————————————————————————————————————————
18. Embark

Sometimes you didn’t even need to use the conventional horizontal or vertical navigation. This site shows us you can use a search interface to get around your site however I will always put my money on that people prefer the normal way of navigation as that is what people are used to. But I think it is a good example of what can be done especially with the search capabilities within SharePoint.
http://www.embark.com
————————————————————————————————————————————————
19. Neudesic

What I want you to focus on here is the use of the ‘house’ icon for the home button. First time I have seen this on a SharePoint site and it is a really good way to free up a bit of space if needed and is instantly recognisable as the button to click to go ‘home’.
http://www.neudesic.com
————————————————————————————————————————————————
20. 1 By Youth

Another example of pushing the boundaries of navigation with SharePoint is using the overwhelming power of CSS. Using the hover state and mixed with an image for the background you can instantly create a unique hover experience for your navigation as demonstrated here.
http://www.1byyouth.com
————————————————————————————————————————————————
Well there you have it! Some great examples of all the different possibilities of what can be achieved with SharePoint. I

Customizing SharePoint List New/Edit/Display Forms individually in InfoPath 2010

2012-08-29T21:47:00.000-07:00

Summary: Customizing list forms is very easy with infopath 2010. A “Customize Form” option is provided along with the list properties as shown below. Now the problem is the editing performed on the form is reflected same in the entire three list forms (new/edit/display). Sometime the requirement can be to have different kinds of forms for new/edit/display fields. The steps described below provides a solution to this problem.

Applies to: Microsoft InfoPath 2010, Microsoft SharePoint Server 2010, SharePoint Designer 2010
Contents

Introduction
Customize list forms
Create views in InfoPath
Associate views with list forms using SP Designer

Introduction
The basic knowledge of following things are required to perform this activity:

InfoPath 2010
SharePoint Server 2010
SharePoint designer 2010

Before you start, set up a list with required number of columns on SharePoint site. The list will be having the OOB new/edit/display pages. These pages are to be individually modified using InfoPath 2010. Open the list as shown below.

Customize the list form

On the List tools, click List. You will see a Customize Form option on the right(highlighted in red)
Click on it, the edit form page will be opened in InfoPath
You can modify the form here, but the change will be reflected in all the 3 forms of the list
But here we need to individually modify each form. To achieve this we need to create separate views for each form

Create views in InfoPath

On InfoPath, click on Page Design tab on the top ribbon
You would see option to create New View as shown above.
You already will be having an edit view (default). You need to create two more views for new and display options.

Click on New View, You will get an option to specify the name as shown below. Specify the name of the view (ex:- New View) and click ok to create the view for new page.
Similarly we need to create one more view for display page. (Name :- Display View)

The three views will be available on the Views drop down list (Highlighted in green)
These three views can be individually modified. You can change page layouts, hide fields or add rules or validations. But still views are not associated with the list views. To do that, we need help of SharePoint designer.
Click on the publish icon to publish the changes made so far.(highlighted below)

Associate views with the list forms
Open the list in SharePoint designer. The list forms would be displayed as shown below.(Highlighted in Green)

Click and open each list item. Right click as shown below and select Properties.

In Properties list, you will see an option “Default View”. Type the View names which you have created in this space. Associate forms with views properly as shown below.

NewForm – NewView
EditForm – EditView
DisplayForm – DisplayView

SharePoint 2010: Howto start customize list form (New/Edit/View) using InfoPath Designer 2010

2012-08-29T21:38:00.002-07:00

In SharePoint 2010 there we have more option to customize list form. For instance, you can use SharePoint Designer 2010 or InfoPath Designer 2010. Since modifying list form using SPD is already exist in previous version. I will just show you how to customize list form using InfoPath Designer 2010.
When customizing list form using InfoPath Designer 2010, you will get all form designer benefit. For example, you can define the field validation rules, parent-child relation etc. And bet what, the process is straight forward. In this very basic how-to, I will demonstrate how to start customize list form using InfoPath Designer 2010. I will create an Book List with “Title” – “Author” – “Status” column. In the New form, I will only show “Title” and “Author” – while in Edit form, “Title” and “Author” will be readonly, but “Status” is editable.
How to customize list form using InfoPath Designer 2010.

Prepare the custom list.

Prepare custom “Book List” with 3 columns: “Title” – “Author” – “Status”. “Status” field is choice “Available” – “In Used” – “Missing”. After creating the list and preparing columns, we can start to use the list and add a new item in this form.
Start InfoPath Designer
Start InfoPath Designer and select to design SharePoint List form.

Type in the SharePoint site URL

And then select the Book List from the list of available data.

Finally, click on Finish.
When the form editor open , you can start to edit the New form. I add a title “Book List Entry” and delete the “Status” row.

And here is the result:
Add “Edit Form” view in the designer, and set Title and Author as readonly.

Type-in the view title.

Design the form – add “Status” column in the form.

Set “Title” and “Author” textbox property to “ReadOnly”
Publish the form to the list.
Configure the “Book List” to use designated form.
Open the list setting page, and expand context menu for the Forms.

Since the first view will be the default – our interest is only to the “(Item) Edit Form”. Click on (Item) Edit Form link, and change the Form view.
You will realize that now you are seeing form services in web part.

Click on Web Parts Tools tab, and then click on Web Part Properties.

In the Web Part Properties, select the designated view.
And here we go with the custom “New Form” and “Edit Form” for the list.
New Form.

Edit Form.

Happy design

SharePoint 2010: Howto start customize list form (New/Edit/View) using InfoPath Designer 2010

2012-08-29T21:37:00.003-07:00

Prepare the custom list.

Prepare custom “Book List” with 3 columns: “Title” – “Author” – “Status”. “Status” field is choice “Available” – “In Used” – “Missing”. After creating the list and preparing columns, we can start to use the list and add a new item in this form.
Start InfoPath Designer
Start InfoPath Designer and select to design SharePoint List form.

Type in the SharePoint site URL

And then select the Book List from the list of available data.

Finally, click on Finish.
When the form editor open , you can start to edit the New form. I add a title “Book List Entry” and delete the “Status” row.

And here is the result:
Add “Edit Form” view in the designer, and set Title and Author as readonly.

Type-in the view title.

Design the form – add “Status” column in the form.

Set “Title” and “Author” textbox property to “ReadOnly”
Publish the form to the list.
Configure the “Book List” to use designated form.
Open the list setting page, and expand context menu for the Forms.

Since the first view will be the default – our interest is only to the “(Item) Edit Form”. Click on (Item) Edit Form link, and change the Form view.
You will realize that now you are seeing form services in web part.

Click on Web Parts Tools tab, and then click on Web Part Properties.

In the Web Part Properties, select the designated view.
And here we go with the custom “New Form” and “Edit Form” for the list.
New Form.

Edit Form.

Happy design.
[Update: Follow the InfoPath and SharePoint 2010 Productivity Series]

LINQ to SharePoint 2010

2012-08-28T03:16:00.000-07:00

Wow! LINQ to SharePoint 2010 is awesome! You have to work with it to see how it simplifies development tasks. I especially love the ability to see what underlying CAML that’s generated on the fly and passed to the server for execution. With LINQ to SharePoint, I believe, we need to have our business logic in place and know how to design “efficient queries” to get our job done! No more worries about missing a “ or confusion as to whether it’s ‘ or “ and so on…
So, I worked on a simple scenario very recently. And I used LINQ to SharePoint to achieve that task. The scenario is I have 2 lists. One of those list looks up the other list along with a few “project fields” (new in SharePoint 2010). I had to write a sample to extract data from these joined lists and to add new items to the list that looks up the other list. Confusing?? Well, read the above again and it might be clearer :)
This is my “Courses” list

This is my “Students” list

The students list uses the course title from courses list and also uses duration & credit points as projected fields. A quick screenshot on how to setup projected fields below.

First step is to generate the entity class file for the site using SPMetal.exe (should be located at: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN).

Add it to the VS2010 project and below is the code that helps achieving this task.

     static void Main(string[] args)
        {
            using (EntityDataContext dataContext =
                new EntityDataContext("http://spdevdemo"))
            {
                var query = from c in dataContext.Students
                            orderby c.Course.Title
                            where c.Course.Duration.Value.Equals(6)
                            select new
                            {
                                StudentName = c.Title,
                                Course = c.Course.Title,
                                Duration = c.Course.Duration,
                                CreditPoints = c.Course.CreditPoints
                            };
// what's the equivalent CAML for this???
                dataContext.Log = Console.Out;
 
                foreach (var student in query)
                    Console.WriteLine("{0} - {1} - {2} - {3}",
                        student.StudentName, student.Course, student.Duration, student.CreditPoints);
// adding sample
 
                // first we create an instance of coursesitem in our entity file 
                // and assign values we need to be present in the lookup field
                
                // there obviously could be a better way to do this instead of hardcoding values
                // will this post a little later on how that's done
 
                CoursesItem newCourseItem = new CoursesItem()
                {
                    Title = "History",
                    CreditPoints = 100,
                    Duration = 4,
                    Id = 7                    
                };
 
                // first attach this object to the data context
 
                dataContext.Courses.Attach(newCourseItem);
 
                // now create an instance of studentsitem
 
                StudentsItem newItem = new StudentsItem()
                {
                    Title = "Student101",
                    Course = newCourseItem
                };
 
                // Call InsertOnSubmit() and then SubmitChanges() to commit
 
                dataContext.Students.InsertOnSubmit(newItem);
                dataContext.SubmitChanges();
 
                Console.WriteLine("Wrote new record successfully!");
    }
}

The output of this code below:

Notice the CAML dump which fires in the background. Obviously, we can appreciate the power of LINQ to SharePoint 2010 after seeing the huge CAML block that we’ll need to otherwise construct and do this simple task. I personally feel LINQ to SharePoint 2010 will be highly leveraged by developers because of its ease of use and enhanced developer productivity. Hope this post was useful and stay tuned for more.

SharePoint 2013 – The new “Digital Asset Content Types” (Audio, Video, Image and more..)

2012-08-27T21:48:00.000-07:00

In SharePoint 2013 MS has introduced a new set of content types called “Digital Asset Content Types” for better use of Audio, Video, Images as Web content. These content types can be added to any library and be used as a one of the items\files. Although I would recommend to use Site Asserts library to add a Video (see procedure in my post How to add a Video to SharePoint 2013 site) these content types can be used in any of the libraries.

Navigate to Site Settings -> Site Content Types and you would find “Digital Asset Content Types”.

Once added these in a Documents library these content types can be added to display in the “New Documents” button.

In addition to this Option you can Drag and drop the Video,music and other files as well.

If you click on a particular Content type in Site Content types you would ahve an option to Hide or show few default fields like “Show download link” or “embed Code link” etc.
Here is the columns and properties of “Video” content type.

Notice the Option “Document Set settings” this allows you to specify if the Videos can be a part of document set.A great way to use the Video in a Document Set would be to use them as an Introduction Video to the document’s of document set.

SharePoint 2013 – The New “Result Sources” for Search Results

2012-08-27T21:47:00.001-07:00

n SharePoint 2013 the “Scopes” are replaced by a new thing called “Result Sources”. By replaced I mean you cannot Create or use the Search scopes anymore. No more displaying a custom search scope in a Drop-down next to search box. Only two system Search scopes All Sites and People will be available at search results page.
What happen to Search Scopes – They are depericated or rather are integrated in Federated Search to create advanced version of these Scopes.
What are Result Sources – Result Sources are actually the combination of Federated Search and Search Scopes. In SharePoint 2013 you can Create a new Result Source and specify the “Protocol” (to search Local SharePoint or Remote SharePoint farm etc..) and can specify the “Query Transformation”.

Pros –

Result sources make it easier to search remote sources including other SharePoint farms.
You can create complex Search queries to restrict results to a subset of content.
There is a new query builder to help build a “Query Transformation. With Query builder you can now define any type of managed property inclusion or exclusion.
Query builer also lets you add Custom Sorting for your results
You can test the results for your Query from the query builder itself

Cons -

You cannot add a Result Source in in a Drop-down next to search box.
Users cannot quickly add Rules to create a Search scope

SharePoint 2013 – New Event Receiver for Groups,Users,Roles,Inheritance

2012-08-27T21:44:00.000-07:00

SharePoint 2013 has Introduced a New and much needed Event Receiver class “SPSecurityEventReceiver”. Using this class you can add Event Handlers around SharePoint Groups, Users, Roles and Permission Inheritance.
Here is the list of events that you can handle in SharePoint 2013 Preview.
You can Handle the following SharePoint Group Events -

GroupAdded
GroupAdding
GroupDeleted
GroupDeleting
GroupUpdated
GroupUpdating

You can Handle the following SharePoint User Events -

GroupUserAdded
GroupUserAdding
GroupUserDeleted
GroupUserDeleting
RoleAssignmentAdded
RoleAssignmentAdding
RoleAssignmentDeleted
RoleAssignmentDeleting
RoleDefinitionAdded
RoleDefinitionAdding
RoleDefinitionDeleted
RoleDefinitionDeleting
RoleDefinitionUpdated
RoleDefinitionUpdating

You can Handle the following Inheritance Events -

InheritanceBreaking
InheritanceBroken
InheritanceReset
InheritanceResetting

Custom Rss feed webpart in Sharepoint 2010

2012-08-27T21:38:00.001-07:00

Here are the steps and the code snippet for creating a custom webpart to display items or news via rss feed.
1. Open the VS and add a new blank solution.
2. Now in your Solution say “RssFeedPackage” add a new item then choose add a webpart. Lets name it as RSSFeedWebPart.
Please note : You can directly create a webpart solution and do not necessarily have to add it as an item. I did this because I wanted to add some more features in the same solution.
3. Next, you need to add some logic to the RSSWebPart WebPart. Edit the RSSWebPart.cs class to include the code below. I have added a custom property to receive the Rss feed url for the webpart.
Code goes like this :
using System;
using System.ComponentModel;
using System.Runtime.InteropServices;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
namespace RssFeedPackage
{
[ToolboxItemAttribute(false)]
public class RSSFeedWebPart: WebPart
{
[WebBrowsable(true)] [Personalizable(PersonalizationScope.Shared)]
public string RSSUrl
{
get; set;
}
protected override void RenderContents(HtmlTextWriter writer)
{
RSSFeed feed = new RSSFeed(RSSUrl);
HyperLink newLink = new HyperLink();
foreach (RSSItem singleRssItem in feed)
{
newLink.Text = singleRssItem.Title;
newLink.NavigateUrl = singleRssItem.Href;
newLink.Target = “rssSite”;
newLink.RenderControl(writer);
writer.WriteBreak();
}
base.RenderContents(writer);
}
}
}
//Code for RSSFeed class
internal class RSSFeed : List
{
internal RSSFeed(string RssURL)
{
try
{
XmlDocument rssDoc = new XmlDocument();
XmlTextReader xRead = new XmlTextReader(RssURL);
rssDoc.Load(xRead);
XmlNodeList xNodes = rssDoc.SelectNodes(“./rss/channel/item”);
foreach (XmlNode xNode in xNodes)
{
this.Add(new RSSItem(xNode)) ;
}
}
catch (Exception)
{
this.Add(new RSSItem());
}
}
}
//Code for RSSItem
internal class RSSItem
{
public string Title { get; internal set; }
public string Href { get; internal set; }
internal RSSItem()
{
Title = “Feed not available at this time” ;
Href = “~” ;
}
internal RSSItem(XmlNode xNode)
{
Title = xNode.SelectSingleNode(“./title”).InnerText;
Href = xNode.SelectSingleNode(“./link”).InnerText;
}
}
4. Now build and deploy the webpart.
5. Finally, Insert the webpart in your webpart page and specify the Rssurl in Edit this WebPart -> RssUrl box

Custom Rss Feed WebPart

2012-08-27T21:37:00.002-07:00

I created a WebPart where RSS feed form a SharePoint Blog Posts list was consumed and modified to display, the two recently updated blog posts. Also, the post opens up in a new window on Click of the Post title.

"rss_text" in the below code will return your feed (two recently updated posts).

So here is the code to extract data from feed.

First,
1. Create a WebPart.
2. In CreateChildControls Call the Below method DisplayRSS() and pass the Posts list Rss Feed url( Get the RSS feed link from "View RSS" option in the Posts lists).

protected string DisplayRSS(string ListRssUrl)
{
try
{
string rss_text = "";
string title = "";
string link = "";
string description = "";

XPathDocument doc = new XPathDocument(ListRssUrl);
XPathNavigator nav = doc.CreateNavigator();
XPathNodeIterator items = nav.Select("//item");

int items_to_show = 2;
int count = 0;
while (items.MoveNext() && count < items_to_show)
{
XPathNavigator navCurrent = items.Current;

try
{
title = navCurrent.SelectSingleNode("title").InnerXml;
link = navCurrent.SelectSingleNode("link").InnerXml;
description = navCurrent.SelectSingleNode("description").InnerXml;

}
catch{ }

CleanUp(ref title,ref description); // Calling a FeedClean Function

if (description != "")
{
description = "- " + description;
description += "...";
}

rss_text += "<a href='" + link + "' target='_blank'>" + title + "</a> " + description;

if (count < items_to_show - 1)
rss_text += "<br/><br/>";

rss_text += "</div>";

count++;
}
return rss_text;
}
catch
{ }
}

protected void CleanUp(ref string title,ref string description)
{
title = title.Replace("\n", " ");
title = title.Replace("\r", " ");

description = description.Replace("<", "<");
description = description.Replace(">", ">");

description = Regex.Replace(hover_description, @"<(.\n)*?>", string.Empty); // To Remove all the html tags from the RSS feed.

title = title.Trim();
description = description.Trim();
}

Workflows in Sharepoint 2010

2012-08-24T00:21:00.000-07:00

Introduction

Based natively on the Workflow Foundation engine, Sharepoint 2007 was the first version of SharePoint that made usage of workflows quite popular among Microsoft end users and .Net developers.
With SharePoint 2010, Microsoft has privileged robustness by choosing to use the .Net framework 3.5 sp1 (and thus Workflow Foundation 3.5), even if a new version of Workflow Foundation 4.0 (with an improved architecture and designer) is provided with .Net 4.
Despite this, SharePoint 2010 provides a set of welcome improvements. These include workflows that can be associated to web sites (and not just to lists); new options in “out of the box” workflows; the possibility to create workflows with Visio 2010, , as well as a new version of SharePoint Designer 2010 that can create real professional workflows which can then be used out of the box. Furthermore, it is now possible to generate workflow forms in Visual Studio 2010 to allow for a better and more flexible communication channel between the workflow and the outside world.
Site workflows

Previous versions of SharePoint did not allow for the association of a workflow to a specific list or indirectly to one or several lists via a content type. With SharePoint 2010 we can now associate one or several workflows to a SharePoint web site, which is pretty handy if the workflow needs to monitor actions happening in several places across the site.

What’s new in the “Out Of the Box” new features

Compared to SharePoint 2007, a number of important improvements have been added. For instance in the new version of the Approval workflow or of the Collect feedback workflow, it is possible to assign tasks by stages, or even to assign tasks to all members of a SharePoint group. As can be seen in the example below, illustrated in figure 1, two tasks can be assigned to users Amy Alberts and Brian Cox in serial; two other approval tasks are assigned in parallel to Alan Brewer and Alan Steiner ; and in the next step , all members of the “Devoteam Managers” group will be assigned a task .

Figure 1.Assigning tasks by stages and to all members of a group

Authoring workflows with Visio 2010

Visio 2010 has now a set of workflow shapes and can easily generate workflows .
An information worker can therefore author a workflow with Visio 2010 before giving it to a developer who will customize it; this can be done in both 2 directions: from SharePoint Designer 2010 to Visio 2010 and from Visio 2010 to SharePoint Designer 2010 (don’t forget that SharePoint Designer is free!).
This is illustrated in figure 2, where we see how an expense report approval process can quickly be designed in Visio 2010.

Figure 2. Creation of a SharePoint workflow with Visio 2010.

Visio 2010 goes beyond the workflow design: it also generates real workflow code (xoml) that can be reused and customized in a tool like SharePoint Designer 2010. In fact, Visio 2010 can export the design into a file with a .vwi format (Visio Workflow Interchange) which is actually a zip file containing files recognized by Workflow Foundation (.xoml and .rules files), but also a .vdx file for the pure Visio part (shape layouts).

Figure 3.Workflow files generated by Visio 2010

Creating a workflow with Sharepoint Designer 2010: what’s new

The 2010 version of Microsoft SharePoint Designer has now become an essential tool for a wide range of users like business analysts, designers and SharePoint developers. We strongly suggest investing time in becoming familiarized with it.

Let’s take a look at the new and improved workflow features of SharePoint Designer 2010.

1. Importing a Visio generated workflow is straightforward and allows for customization by a designer or a developer

Figure 4.Importing a Visio 2010 generated workflow

The workflow designer illustrated in the next picture is also more intuitive than in the previous version. The annotations provided in Visio 2010 (like “Expense Report too expensive” and “Approve it”) can be retrieved in SharePoint Designer 2010 as illustrated in the next figure :

Figure 5.SharePoint Designer Edition of a Visio 2010 workflow.

2.       Reusing and customizing “out of the box” workflows
Out of the box workflows, like Collect Feedback and Approval, can be reused in customized workflows : it is a functionality we made use of in Visio 2010 (see figure 2) under the label “Assign item for approval”. Given that most custom collaborative workflows will use some kind of approval functionality, which is sometimes very complicated to program even for skilled Workflow Foundation .Net developers, this is a major improvement.

3.       The Office task brings a touch of flexibility in the behavior of the out of the box workflow tasks; it allows us to assign specific behavior to individual tasks, or to the whole approval session. For instance, we can implement the following requirements:
a.       If 50% of users approved, the system approves the item
b.      If the user is not available, assign the task to his manager
c.       As soon as an approval starts or completes, start a specific action (like sending an e-mail for instance)
d.      As soon as when a task is assigned to a user or is complete, start a specific action.

4.       Content types & site workflows

Probably the weakest feature of SharePoint designer 2007 workflows is that they had to be associated with specific lists and couldn’t be reused. This is a thing of the past: workflows generated with SharePoint Designer 2010 can now be associated with Content Types (which is generally considered as good practice) , or can be associated with a site.
As illustrated in figure 6, it is possible to create 3 types of workflows in SharePoint Designer 2010:

·         Workflows associated to a specific list
·         Workflows associated to a content type
·         Workflows associated to a site

Figure 6.SharePoint Designer can create 3 types of workflows.

5. Security : Impersonation Step
Other improvements have been made to security. Previously, declarative workflows generated by SharePoint Designer 2007 were based on the identity of the user who initiated the workflow, which could be a problem if we wanted to access some unauthorized resources; on the other hand, workflows created with Visual Studio 2010 run in full trust mode (with the application pool user identity).
With SharePoint Designer 2010 we now have a kind of hybrid mode: we can run part of the workflow with the identity of the user who published the workflow (typically the Designer) by using the Impersonation step action as illustrated in figure 7.

Figure 7.Impersonation Step

6. Infopath workflow forms

Workflows forms for SharePoint Designer 2010 workflows are now Infopath forms by default (they were aspx forms in the previous version); they can therefore be visualized in the Office2007 or 2010 rich client and can easily be customized with the Infopath 2010 Designer.

7. Workflow visualisation

Thanks to the new Visio services built in SharePoint 2010, we can now visualize the state of our workflows Figure 8 illustrates an approval process where Brian Cox has completed his task and the system is waiting for Amy Alberts to take action before assigning a task to Alan Steiner.

Figure 8.Visualisation of a workflow

8.       Sandbox
Workflows authored with SharePoint Designer 2010 can run in a protected environment called the sandbox where they cannot put the farm in danger; workflows generated with Visual Studio must run in the farm mode, but not in a sandbox environment.

Missing features in Sharepoint Designer 2010

Just as it was the case in Sharepoint Designer 2007, it is not possible to author state machine workflows as it is done in Visual Studio; even if most workflows are sequential workflows, there are some situations where we need to be able to move back to previous steps in the workflow. In that case, forget Sharepoint Designer 2010 and move to Visual Studio 2010!

Another missing feature is that lack of the looping mechanism in Sharepoint Designer workflows: for instance, we cannot loop through several list items without having to rely on (.Net) custom activities created with Visual Studio.

Creating Sharepoint workflows with Visual Studio 2010: what’s new

1.       Creating workflows with Visual Studio 2010 is far easier than before thanks to the new Feature Designer (for managing SharePoint features), the new Package Designer (for managing SharePoint solutions packages) and the automatic debugging experience: by clicking F5 the debugger is automatically attached to the corresponding worker process.

2.       Like before, we have 2 workflow projects templates: Sequential Workflow or State Machine Workflow (question from Ronnie, if this is like before, why is it mentioned here?)

Figure 9.Templates for creating workflows in Visual Studio 2010.

3.       No sandbox
Unlike declarative workflows authored with Sharepoint Designer, workflows created with Visual studio cannot run in a sandbox but only in full trusted “Farm Mode”; this is a serious limitation to take into account if we want to move our customizations to Sharepoint Online in the future.

4.       Still the old Designer
Since workflow Foundation 3.5 is the workflow engine (version 4.0 with the new Designer is not supported), we still have to use the old designer which is quite slow when we need to display many activities.

5.       Importing from SharePoint Designer : irreversible
It is now possible to easily import SharePoint designer 2010 generated workflow into Visual Studio 2010; however, the process is irreversible, contrary to going from Visio 2010 to Sharepoint 2010.

6.       List or site workflows
We can create workflows linked to a list or to a site.

7.       Workflow events
We can now handle events generated when a list workflow is starting, is started, is postponed, or is completed; this is also true for declarative workflows

Figure 10.Creating an event handler to listen to Workflow events

8. Workflow association and initiation forms

Creating workflow association forms and initiation forms is now very easy thanks to two new templates that generate aspx pages, as well as code that provides an exchange mechanism between the forms and the workflow.

Figure 11.Creating association and initiation forms in Visual Studio 2010

The developer only needs to add specific controls into the aspx forms and must implement 2 methods: GetAssociationData and GetInitiationData().
Unfortunately there is no template provided to generate workflow tasks forms and workflow modification forms.

9. Communication with the outside world

One of the biggest improvement in SharePoint 2010 workflows is the possibility to create Pluggable Workflow Services which is an efficient way for workflows to communicate asynchronously with the outside world: for instance a workflow might needs to invoke an external line of business application (“lob”)) like SAP; the answer coming from the lob might take 1 second, but also one hour, one day or much more.

What was the problem in Sharepoint 2007?

A typical scenario in Sharepoint workflows is to communicate with end users by creating tasks and by listening to any task action performed by the users. In this specific case, the tasks are created by using the CreateTask activity that calls the Sharepoint api; we can make the workflow listen to the tasks changes by using the OnTaskChanged activity, which like all activities with a name starting with “On”, are event based activities. When a workflow runs an event based activity he becomes idle.
An important feature of idle workflows is to be automatically suspended , removed from the host process (“dehydrated”) and serialized in a media (like the Sharepoint content database) and to be “rehydrated” when the event comes up.
The benefit of using event based activities is that since workflows lie dormant in the SharePoint content database when they wait for an event, we can therefore run thousands of workflows in parallel and achieve great scalability.

Figure 12.Event based workflow activities (in green)

In SharePoint 2007 however, we can only use a limited number of event based activities provided by Microsoft: that makes asynchronously calling LOB (Line of Business Applications like SAP) quite shaky by having to create tasks and by asking the LOB to communicate with the workflow by changing the tasks.

In Sharepoint 2010

Today it is no longer necessary to follow this complex pattern ; instead it is now possible to listen to any custom event and to use the HandleExternalEvent activity provided with Workflow Foundation 3.0 (see figure 12) and well known by .Net developers!

Figure 13.calling an external system

However, to achieve it it is still necessary to create a pluggable service by creating a custom class derived from the new SPWorkflowExternalDataExchangeService ; this custom class must be declared in the web.config.

Conclusions

Even though the workflow aspect of SharePoint 2010 is not revolutionary, it is now much, much easier to create workflows.
Sharepoint Designer and Visio 2010 provide major added value: workflows created with Sharepoint Designer can be reused, it is possible to customize and reuse out of the box workflows, and there is a better and scalable communication channel between Sharepoint and the outside world.

Create Content Sources in SharePoint 2010 using PowerShell

2012-08-23T23:51:00.001-07:00

Automating the Content Source creation in SharePoint 2010

We can create Content Sources for Enterprise Search Service Application in SharePoint 2010 from Central Administration.
Go to Central Administration => Application Management => Manage Service Applications => Enterprise Search Service Application.

On the Quick Launch Menu, go to Crawling and then click on Content Sources.

You could be able to see the Content Sources. By clicking on New Content Source link we can create a new Content Source.

Another way is we can create the content sources for Search Service Application using SharePoint Object Model.

Here we will be seeing about automating the content source creation using powershell script.

Steps Involved:

1. Create the input xml file which contains the inputs for content source creation.
2. Create ps1 file which contains the script for content source creation.

CreateContentSources.xml

<?xml version="1.0" encoding="utf-8" ?>

<ContentSources>


<SSAName>EnterPrise Search Service Application</SSAName>

<ContentSource Name="Sample1 SharePoint Sites" />

<ContentSource Name="Sample2 SharePoint Sites" />

<ContentSource Name="Sample3 SharePoint Sites" />
</ContentSources>

CreateContentSources.ps1

#----------------Get the xml file---------------------------------------------------------------

[xml]$xmlData=Get-Content "C:\Users\Desktop\ContentSources\CreateContentSources.xml"

#----------------Create New Content Source function---------------------------------------------

function CreateNewContentSource

{


$flag=0 

$ssa=Get-SPEnterPriseSearchServiceApplication -Identity $xmlData.SSAName

$ssaContent = new-object Microsoft.Office.Server.Search.Administration.Content($ssa)

$xmlData.ContentSources.ContentSource | ForEach-Object {


$contentSourceName=$_.Name

foreach ($availableContentSource in $ssaContent.ContentSources)

{


if ($availablecontentSource.Name.ToString() -eq $contentSourceName)

{


write-host -f Yellow $contentSourceName "content source already exists" 

write-host -f Yellow Deleting $contentSourceName content source 

$availablecontentSource.Delete()

write-host -f Green $contentSourceName content source is deleted successfully

write-host -f yellow Creating $contentSourceName 

$ssaContent.ContentSources.Create([Microsoft.Office.Server.Search.Administration.SharePointContentSource], $contentSourceName)

write-host -f green $contentSourceName "content source is added successfully"

$Flag=1break
}
}

if($Flag -eq 0)

{


write-host -f yellow Creating $contentSourceName 

$ssaContent.ContentSources.Create([Microsoft.Office.Server.Search.Administration.SharePointContentSource], $contentSourceName)

write-host -f green $contentSourceName "content source is added successfully"
}
}
}

#----------------Calling the function---------------------------------------------

CreateNewContentSource

Run the Script:

1. Go to Start.
2. Click on All Programs.
3. Click on Microsoft SharePoint 2010 Products and then click on SharePoint 2010 Management Shell.
4. Run the C:\Users\Desktop\ContentSources\CreateContentSources.ps1

Output:

And in the Central Administration you could see the newly added content sources as shown in the following

Thanks for reading.

Hope this article was useful, keep reading my forthcoming article of this series

INFOPATH

2012-08-23T23:48:00.003-07:00

I have created a custom list named “Custom” which has the following columns

For this list I am going to create an InfoPath form which will be used as New/Edit form in the list. New form for the list looks like the following

Note: None of the columns is mandatory in Custom list

Create an InfoPath form:

1. Open Microsoft InfoPath Designer 2010.
2. Go to File =>New => Click on SharePoint List from Available Form Templates

3. Data Connection Wizard will popup, enter the site URL.

4. Click on Next.
5. Select Customize an existing SharePoint list and then select Custom which is a custom list.

6. Click on Finish.

7. You could see the InfoPath form with the following columns

Publish the InfoPath form to SharePoint:

1. Go to File =>Info and then click on Quick Publish.

2. Publishing...

3. Form template is successfully published.

InfoPath form in SharePoint Edit or New form:

1. Open the SharePoint Site.
2. Go to Custom List and add a new item.
3. New form will be an InfoPath form as shown in the following.

How to use the Default SharePoint form:

1. Go to List Settings.
2. In the General Settings, click on Form Settings.

3. You can select the Default SharePoint form or you can modify the existing InfoPath form.

Thanks for reading.
Hope this article was useful, keep reading my forthcoming article of this series.

Creating a Custom SharePoint Form using SharePoint Designer

2012-08-23T23:45:00.001-07:00

Create a custom list with the necessary fields
Open SharePoint designer and navigate to the site hosting this custom list
Expand the lists folder until you see your list and the DispForm.asxp, EditForm.aspx, and NewForm.aspx.

Create a new ASPX page

Add the SharePoint Custom List Form control (Warning! Don’t mix this form up with the List Form Control

Choose the proper list (Warning! If you don’t see the content type you didn’t follow the instructions, look at the step I show above!!!)

Your form will appear as it does below

SharePoint 2010: Howto start customize list form (New/Edit/View) using InfoPath Designer 2010

2012-08-23T23:39:00.001-07:00

Prepare the custom list.

Prepare custom “Book List” with 3 columns: “Title” – “Author” – “Status”. “Status” field is choice “Available” – “In Used” – “Missing”. After creating the list and preparing columns, we can start to use the list and add a new item in this form.
Start InfoPath Designer
Start InfoPath Designer and select to design SharePoint List form.

Type in the SharePoint site URL

And then select the Book List from the list of available data.

Finally, click on Finish.
When the form editor open , you can start to edit the New form. I add a title “Book List Entry” and delete the “Status” row.

And here is the result:
Add “Edit Form” view in the designer, and set Title and Author as readonly.

Type-in the view title.

Design the form – add “Status” column in the form.

Set “Title” and “Author” textbox property to “ReadOnly”
Publish the form to the list.
Configure the “Book List” to use designated form.
Open the list setting page, and expand context menu for the Forms.

Since the first view will be the default – our interest is only to the “(Item) Edit Form”. Click on (Item) Edit Form link, and change the Form view.
You will realize that now you are seeing form services in web part.

Click on Web Parts Tools tab, and then click on Web Part Properties.

In the Web Part Properties, select the designated view.
And here we go with the custom “New Form” and “Edit Form” for the list.
New Form.

Edit Form.

SharePoint 2010 - SharePoint Object Model

2012-08-22T23:52:00.001-07:00

For programming against the SharePoint items, we need to retrieve the properties and the methods to operate on them. The SharePoint Object Model provides various classes to accomplish this. In this article we can discuss the Object Model with the core classes involved with little amount of coding.

Please note that there are 2 Object Models in SharePoint 2010:

Server Object Model
Client Object Model

Here we are discussing only about the Server Object Model. Server Object Model classes are used for server-side programming and will be executed on the SharePoint Server Farm.

Namespace

The Server Object Model classes are residing in the Microsoft.SharePoint assembly. The general classes are available in the Microsoft.SharePoint namespace and the administration classes inside the Microsoft.SharePoint.Administration namespace.

Core Classes

Following are the important classes and their corresponding SharePoint items.

Class	SharePoint Item
SPFarm	Farm
SPServer	Server
SPSite	Site Collection
SPWeb	Web site
SPControl	Control
SPList	List
SPDocumentLibrary	Document Library
SPContentType	Content Type
SPUser	User
SPException	SharePoint Exception

Programming

Now we can start experimenting with some of the above classes. To begin we can create a SharePoint Console Application. Use the New Project > SharePoint > Console Application project item.

Accessing the List Items in a List

For proceeding with this example, create a list derived from the Contacts template and name it as "My Contacts".

Add some items inside it with the First Name and Last Name set.

Use the following code inside the Console application and execute it.
using (SPSite site = new SPSite("http://appes-pc/my/personal/dotnet")) // Site Collection{
    using (SPWeb web = site.OpenWeb()) // Site    {
        SPList list = web.Lists["My Contacts"]; // List        int i = 1;
        foreach (SPListItem item in list.Items)
        {
            Console.WriteLine("Item: " + (i++).ToString());

            Console.WriteLine(item.Name);
            Console.WriteLine(item.Title);
            Console.WriteLine(item.GetFormattedValue("First Name"));
            Console.WriteLine(item.GetFormattedValue("Last Name"));

            Console.WriteLine(string.Empty);
        }
    }
}

Console.ReadKey(false);

If you receive any build errors regarding a namespace, change the Project Properties > Target to .Net Framework 3.5.

Now try building the application and it should work fine. You will see the following output.

Please note the use of Title and Name properties and the GetFormattedValue() method.

Accessing the items in a Library

Now we can proceed with accessing the document library items programmatically. For proceeding you need to create a document library inheriting from the Document Library template and name it "My Docs". Upload one or two documents into it. We are proceeding to get the file name and length in this example.

Enter the following code in the console application.
using (SPSite site = new SPSite("http://appes-pc/my/personal/dotnet")) // Site Collection{
    using (SPWeb web = site.OpenWeb())                    // Site    {
        SPDocumentLibrary library = web.Lists["My Docs"] as SPDocumentLibrary; // Library        int i = 1;
        foreach (SPListItem item in library.Items)
        {
            Console.WriteLine("Item: " + (i++).ToString());

Console.WriteLine(item.File.Name);
Console.WriteLine(item.File.Length);

            Console.WriteLine(string.Empty);
        }
    }
}

Executing the application, you will see the following results.

SPControl

The SPControl class acts as the base class while developing server controls. It reseides in the namespace Microsoft.SharePoint.WebControls.

SPControl provides static methods that returns reference to the current site, web, web application, module. The methods are:
SPControl.GetContextSite()SPControl.GetContextWeb()SPControl.GetContextWebApplication()SPControl.GetContextModule()

SPException

The SPException class can be used to handle an exception in a try catch block. It represents the exceptions thrown by the server object model.
try{
    // Code here}catch (SPException ex)
{
    // Handle Exception}

SPUser

The SPUser class can be used to access user information for a SharePoint site. Enter the following code to get the number of users and their names.
using (SPSite site = new SPSite("http://appes-pc/my/personal/dotnet"))
{
    using (SPWeb web = site.OpenWeb())
    {
        foreach (SPUser user in web.AllUsers)
            Console.WriteLine("User: " + user.Name);
    }
}

On running the code you will see the results based on your machine users.

Note

You can add a new list item or library item using the Items.Add() method. For updating and deleting use the item.Update() and item.Delete() methods respectively. More code coverage on these areas will be provided later.

References

http://msdn.microsoft.com/en-us/library/ms473633.aspx
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.webcontrols.spcontrol.aspx
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spuser.aspx

Summary

In this article we have explored the SharePoint Object Model and some basic coding examples with List and Library. The advanced coding examples will be provided at a later point of time.

VIVEK KUMAR PANDEY

Programming in Sharepoint 2010

Move Item and Document

Tuesday, 28 February 2012

Use to add or remove user from site collection Administrator in c# in sharepoint

Thursday, 5 January 2012

Terms & Conditions in my link

Remove User who complete the Document

Create a Workflow using Visual Studio 2010

Introduction

Types of Workflows

What is an Activity?

SharePoint 2010: Programming with Business Data Connectivity Model Using Visual Studio 2010

Working with External Data Communication using VS 2010

SharePoint 2010: Change the “Add New Item”

The Goal

ID’s used by web parts

If there is only one “Add new” message on a page

But the IDs won’t always work!

Where should you add the code?

Hide the “+” image?

Hide the entire message?

Deploying a custom master page

Deploying a custom master page in SharePoint 2010

How to embed the “Connect to Outlook” link in a page

How Themes work in SharePoint 2010

How to use RDLC with Asp.net?

Step:-

How to Create Custom SharePoint 2010 Page Layouts using SharePoint Designer 2010

Scenario:

How To:

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Top 20 Examples of Creative Navigation within SharePoint

Customizing SharePoint List New/Edit/Display Forms individually in InfoPath 2010

SharePoint 2010: Howto start customize list form (New/Edit/View) using InfoPath Designer 2010

SharePoint 2010: Howto start customize list form (New/Edit/View) using InfoPath Designer 2010

LINQ to SharePoint 2010

SharePoint 2013 – The new “Digital Asset Content Types” (Audio, Video, Image and more..)

SharePoint 2013 – The New “Result Sources” for Search Results

SharePoint 2013 – New Event Receiver for Groups,Users,Roles,Inheritance

Custom Rss feed webpart in Sharepoint 2010

Custom Rss Feed WebPart

Workflows in Sharepoint 2010

Introduction

Create Content Sources in SharePoint 2010 using PowerShell

Automating the Content Source creation in SharePoint 2010

Steps Involved:

CreateContentSources.xml

CreateContentSources.ps1

#----------------Create New Content Source function---------------------------------------------

Run the Script:

Output:

INFOPATH

Create an InfoPath form:

Publish the InfoPath form to SharePoint:

InfoPath form in SharePoint Edit or New form:

How to use the Default SharePoint form:

Creating a Custom SharePoint Form using SharePoint Designer

SharePoint 2010: Howto start customize list form (New/Edit/View) using InfoPath Designer 2010

SharePoint 2010 - SharePoint Object Model