Zoom In Sharepoint

Client Object Model Part -5

noreply@blogger.com (Unknown) — Tue, 03 Apr 2012 14:33:00 +0000

We are continuing from the last post where we created some examples using Managed COM. Please read post from Part -1 to Part - 4 to see all the examples.

In this post we will create the folders inside a list or document library using COM.

Create Folders In List :

using (ClientContext clientContext = new ClientContext(SiteURL))

{

Web currentWeb = clientContext.Web;

List list = currentWeb.Lists.GetByTitle("NewList");

list.EnableFolderCreation = true;

FolderCollection folderColl = list.RootFolder.Folders;

clientContext.Load(currentWeb);

clientContext.Load(list);

clientContext.Load(folderColl);

clientContext.ExecuteQuery();

string folderName = "Folder1";

string newFolderUrl = list.Title + "/" + folderName;

Folder existingFolder = null;

string relativURL = currentWeb.ServerRelativeUrl;

//Check if folder exists in the list

if (list != null)

{

//Create the exact folder URL.

String folderUrl = String.Format("{0}{1}/{2}", currentWeb.ServerRelativeUrl, list.Title, folderName);

//If it is a pulishing site then

//String folderUrl = String.Format("{0}{1}{2}/{3}", currentWeb.ServerRelativeUrl, "Lists/", list.Title, folderName);

IEnumerable<Folder> existingFolders = clientContext.LoadQuery<Folder>

(folderColl.Where(folder => folder.ServerRelativeUrl == folderUrl));

clientContext.ExecuteQuery();

existingFolder = existingFolders.FirstOrDefault();

}

if (existingFolder == null)

{

//Get the collection of content types.

ContentTypeCollection listContentTypes = list.ContentTypes;

clientContext.Load(listContentTypes, types => types.Include

(type => type.Id, type => type.Name,

type => type.Parent));

//Get the Folder content type.

var result = clientContext.LoadQuery(listContentTypes.Where

(c => c.Name == "Folder"));

clientContext.ExecuteQuery();

ContentType folderContentType = result.FirstOrDefault();

ListItemCreationInformation newItemInfo = new ListItemCreationInformation();

newItemInfo.UnderlyingObjectType = FileSystemObjectType.Folder;

newItemInfo.LeafName = folderName;

ListItem newListItem = list.AddItem(newItemInfo);

newListItem["ContentTypeId"] = folderContentType.Id.ToString();

newListItem["Title"] = folderName;

newListItem.Update();

clientContext.Load(list);

clientContext.ExecuteQuery();

}

};

In this following points are important to understand :

1) 1) Get the folders collection of the list using FolderCollection

<!2 Check if the folder you are about to create already exists or not .

Note : If it is a publishing site then use folder URL as

ServerRelative URL + “/Lists/” + ListTitle + folderName

//String folderUrl = String.Format("{0}{1}{2}/{3}", currentWeb.ServerRelativeUrl, "Lists/", list.Title, folderName);

<!3)Get the folder content type and finally create the item and assign the folder content type to the newly created item.

4) This will create folder in the list.

Check if List exists in the site :

When we try to access a list using GetListByTitle() , we are required to pass the list name as parameter, In this case if List does not exists then this throws exception, So it is always recommended to check if list exists in the site before doing any operation on the list.

Below code snippet will return List object if it exists otherwise it will return null.

private static List CheckIfListExists()

{

String listTitle = "NewList";

using (ClientContext clientContext = new ClientContext(SiteURL))

{

List existingList;

Web web = clientContext.Web;

ListCollection lists = web.Lists;

IEnumerable<List> existingLists = clientContext.LoadQuery(

lists.Where(

list => list.Title == listTitle)

);

clientContext.ExecuteQuery();

existingList = existingLists.FirstOrDefault();

return existingList;

}

Happy coding :)

Client Object Model Part -4

noreply@blogger.com (Unknown) — Tue, 03 Apr 2012 14:27:00 +0000

We will continue from the last post where we were doing operations on list using managed Client object model.Please read Post from Part -1 to Part -3 to go through all the examples of COM

Here we will retrieve the items from the list using CAML query.

Retrieve Items from List using CAML query:

Code Snippet:

using (ClientContext clientContext = new ClientContext(SiteURL))

{

//To retrieve collection of items from the list based on CAML query.

List lst = clientContext.Web.Lists.GetByTitle("NewList");

string titleName = "abc";

CamlQuery query = new CamlQuery();

query.ViewXml = "<View><Query><Where><Eq><FieldRef Name='Title'/><Value Type='Text'>" + titleName + "</Value></Eq></Where></Query></View>";

ListItemCollection coll = lst.GetItems(query);

clientContext.Load(coll);

clientContext.ExecuteQuery();

}

In this we are retrieving items based on the title field of the list. We can use any of the field of the list for filtering the results.

Retrieve all the items from the List/Documents library including folders and subfolders :

Objective is to retrieve all the items from the list including folders and subfolders.

Code Snippet :

//To retrieve all the items from a list/document library including folders and subfolders

List lst1 = clientContext.Web.Lists.GetByTitle("NewList");

CamlQuery camlQuery = new CamlQuery();

camlQuery.ViewXml = @"<View Scope='Recursive'/>";

ListItemCollection coll1 = lst1.GetItems(camlQuery);

clientContext.Load(coll1);

clientContext.ExecuteQuery();

Important :

camlQuery.ViewXml = @"<View Scope='Recursive'/>";

This query will retrieve all the items from the list.

Happy Coding J

Continue reading Part -5

Client Object Model Part -3

noreply@blogger.com (Unknown) — Tue, 03 Apr 2012 14:23:00 +0000

In the last post we created the sample for creating the web using various available templates Part -2 .

I will recommend you to go through Part -1 to Part -2 and then continue reading to have a better understanding.

In this post we will create list using managed client object model.

Create List :

To try this sample code , you can create a console application and then create a method CreateList and pass SiteURL where you want to create the list.

using (ClientContext clientContext = new ClientContext(SiteURL))

{

List targetList = null;

ListCreationInformation NewListInfo = new ListCreationInformation

{

//Can set the list template here.

TemplateType = (int)ListTemplateType.GenericList,

Title = "NewList",

Url = "NewList",

QuickLaunchOption = QuickLaunchOptions.On // to set the quick launch property of the list.

};

targetList = clientContext.Web.Lists.Add(NewListInfo);

clientContext.Load(clientContext.Web.Lists);

clientContext.ExecuteQuery();

}

Important : For creating the List we need to use the ListCreationInformation object and set the properties.

And finally load the newly created list and call Execute query method of the client context. Until this execute query method is called changes will not be updated on the site. This executeQuery method bundles all the request and executes them on the server. This reduces the server round trip.

This will create the list in the site and this list will be available on the quick launch menu of the site.

Add fields in the List :

Objective is to add fields in the list. In this code snippet we are creating fields of type text,Number,URL, You can create fields with other available types as well .

using (ClientContext clientContext = new ClientContext(SiteURL))

{

//To retrieve collection of items from the list based on CAML query.

List lst = clientContext.Web.Lists.GetByTitle("NewList");

FieldCollection fields = lst.Fields;

//Add column of type Text

FieldType fieldType = FieldType.Text;

fields.AddFieldAsXml(

String.Format("<Field DisplayName='{0}' Type='{1}'></Field>", "Name",

fieldType), true, AddFieldOptions.DefaultValue);

//Add column of type Number

FieldType fieldType1 = FieldType.Number;

fields.AddFieldAsXml(String.Format("<Field DisplayName='{0}' Type='{1}'></Field>", "ProductCount",

fieldType1), true, AddFieldOptions.DefaultValue);

//Add column of type Number

FieldType fieldType2 = FieldType.URL;

fields.AddFieldAsXml(String.Format("<Field DisplayName='{0}' Type='{1}'></Field>", "SiteLink",

fieldType2), true, AddFieldOptions.DefaultValue);

lst.Update();

clientContext.ExecuteQuery();

}

Create List Item :

Our objective is to add items in the newly created list. Right now this list has only one default field Title, so we will add item in the list and set value for that field only.

using (ClientContext clientContext = new ClientContext(SiteURL))

{

List lst = clientContext.Web.Lists.GetByTitle("NewList");

ListItemCreationInformation newItemInfo = new ListItemCreationInformation();

ListItem newListItem = lst.AddItem(newItemInfo);

newListItem["Title"] = "abc";

newListItem.Update();

clientContext.Load(newListItem);

clientContext.ExecuteQuery();

}

Important : For creating the List we need to use the ListItemCreationInformation object and set the properties.

And finally load the newly created item and call Execute query method of the client context. Until this execute query method is called changes will not be updated on the server. This executeQuery method bundles all the request and executes them on the server. This reduces the server round trip.

Update Item in the List :

Our objective is to update the item in the list. For this first we need to access the list , then we need to access the list item. Every list item has unique auto incrementing integer value which can be used to retrieve the particular item and then update the field of the ListItem.

using (ClientContext clientContext = new ClientContext(SiteURL))

{

ListItem lstItem = clientContext.Web.Lists.GetByTitle("NewList").GetItemById(2);

lstItem["Title"] = "UpdateTitle";

lstItem.Update();

clientContext.ExecuteQuery();

}

Important :

<!1) For updating the field of type HyperIink use this code snippet

FieldUrlValue link = new FieldUrlValue();

link.Url = "http://microsoft.com";

link.Description = "World of Microsoft Technologies";

lstItem["URL"] = link;

lstItem.Update();

clientContext.ExecuteQuery();

<!2) For updating the field of type “Person or Group “ use this code snippet

User user = null;

FieldUserValue fldUserValue = new FieldUserValue();

user = clientContext.Web.EnsureUser("domain\\userId");

clientContext.Load(user);

clientContext.ExecuteQuery();

fldUserValue.LookupId = user.Id;

lstItem["User"] = fldUserValue;

lstItem.Update();

clientContext.ExecuteQuery();

This way we can update the specific item from the list based on the auto incrementing ID.

Happy Coding J

Continue reading Part -4

Client Object Model Part -2

noreply@blogger.com (Unknown) — Tue, 03 Apr 2012 09:20:00 +0000

In this post we will create some examples using Managed Client Object model. Our objective here is to create the Web, List, Add Items, Update Items, Delete Items etc using the Managed COM. Please go through the Part -1 for understanding the basics of COM

Create Web :

//Create web in the root site.

using (ClientContext clientContext = new ClientContext(SiteURL))

{

WebCollection webColl = clientContext.Web.Webs;

WebCreationInformation newWebCreationInfo = new WebCreationInformation();

newWebCreationInfo.Title = "New web site";

newWebCreationInfo.Description = "Here goes the description ";

newWebCreationInfo.Language = 1033;

newWebCreationInfo.Url = "NewWeb1";

newWebCreationInfo.UseSamePermissionsAsParentSite = true;

//This template is for team site

newWebCreationInfo.WebTemplate = "STS#0";

Web oNewWebsite = webColl.Add(newWebCreationInfo);

clientContext.ExecuteQuery();

}

So this code snippet will create the web (Team site)inside a site collection. We can create any site by specifying the required WebTemplate type. Here is the list of available templates.

List of Web Templates :

Template ID Template Name

GLOBAL#0 Global template

STS#0 Team Site

STS#1 Blank Site

STS#2 Document Workspace

MPS#0 Basic Meeting Workspace

MPS#1 Blank Meeting Workspace

MPS#2 Decision Meeting Workspace

MPS#3 Social Meeting Workspace

MPS#4 Multipage Meeting Workspace

CENTRALADMIN#0 Central Admin Site

WIKI#0 Wiki Site

BLOG#0 Blog

SGS#0 Group Work Site

TENANTADMIN#0 Tenant Admin Site

ACCSRV#0 Access Services Site

ACCSRV#1 Assets Web Database

ACCSRV#3 Charitable Contributions Web Database

ACCSRV#4 Contacts Web Database

ACCSRV#6 Issues Web Database

ACCSRV#5 Projects Web Database

BDR#0 Document Center

OFFILE#0 (obsolete) Records Center

OFFILE#1 Records Center

OSRV#0 Shared Services Administration Site

PPSMASite#0 PerformancePoint

BICenterSite#0 Business Intelligence Center

SPS#0 SharePoint Portal Server Site

SPSPERS#0 SharePoint Portal Server Personal Space

SPSMSITE#0 Personalization Site

SPSTOC#0 Contents area Template

SPSTOPIC#0 Topic area template

SPSNEWS#0 News Site

CMSPUBLISHING#0 Publishing Site

BLANKINTERNET#0 Publishing Site

BLANKINTERNET#1 Press Releases Site

BLANKINTERNET#2 Publishing Site with Workflow

SPSNHOME#0 News Site

SPSSITES#0 Site Directory

SPSCOMMU#0 Community area template

SPSREPORTCENTER#0 Report Center

SPSPORTAL#0 Collaboration Portal

SRCHCEN#0 Enterprise Search Center

PROFILES#0 Profiles

BLANKINTERNETCONT... Publishing Portal

SPSMSITEHOST#0 My Site Host

ENTERWIKI#0 Enterprise Wiki

SRCHCENTERLITE#0 Basic Search Center

SRCHCENTERLITE#1 Basic Search Center

SRCHCENTERFAST#0 FAST Search Center

visprus#0 Visio Process Repository

Note: For creating publishing webs, make sure publishing features are enabled on the parent site.

Happy Coding J

Continue reading Part -3

Client Object Model Part -1

noreply@blogger.com (Unknown) — Tue, 03 Apr 2012 09:16:00 +0000

Here I am starting a series of posts on Client Object model.

Sharepoint 2010 has introduced three types of COM (Client Object Model )

1) Managed Client Object Model -Implemented in .NET CLR

2) ECMA script

3) Silverlight Client object model.

Client APIs allows you to interact with SharePoint sites from script that executes in the browser i.e. it is not mandatory to install Sharepoint on the client machine where application is being run and it can communicate with Sharepoint server remotely.

.NET managed, and Silverlight client object models provides a subset of the server object model that is defined in Microsoft.SharePoint.dll, including objects that correspond to major objects at the site-collection level or lower in the SharePoint Foundation hierarchy.

The great advantage of it is that syntax is like the SharePoint Object Model.

Syntax of two types of object model when compared looks like this.

Server side syntax	Client side syntax
SPContext	ClientContext
SPSite	Site
SPWeb	Web
SPList	List

Now to implement the client object model in the solution we need to refer the dlls required for each type of Cilent object model.

1) Managed Client Object Model:

Dlls required -

a) Microsoft.SharePoint.Client.dll,

b) Microsoft.SharePoint.Client.Runtime.dll.

Location : 14/ISAPI folder. Usually, the location would be at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI".

b) Microsoft.SharePoint.Client.Silverlight.Runtime.dll.

Location : "C:\Program Files\Common Files\Microsoft Shared\Web Server\Extensions\14\Template\LAYOUTS\ClientBin

So from the next post will start some samples of implementation of three types of client object model.

Continue reading Part -2 .

Customization Ribbon – Opening a sharepoint modal pop window from Ribbon control - Part 4

noreply@blogger.com (Unknown) — Thu, 22 Mar 2012 08:14:00 +0000

Objective : In the earlier posts we have already explained , how to add a custom control in the Ribbon of a sharepoint list or document library. We have also explained about the CommandUIHandlers tag and its working. So whatever custom action you want to perform when user selects any item from the Flyout anchor or when user clicks on button can be defined in the CommandUIHandlers tag.

Please read Part 1 – Part 3 for basics of Ribbon customization.

Now we have a standard flyout anchor menu and on selection of any item, we want to open a sharepoint dialog view which in turns hosts an .aspx page. This “.aspx” page is deployed in the layouts folder of the file system.

Note : Important point to remember is that application pages will be supported only by Farm Solutions and not the SandBox solution. So when you are adding application pages always create FarmSolution

Steps :

1) Create Empty sharepoint solution (Farm Solution)

2) Add Feature in it (FlyoutAnchorElementFeature

3) Add Empty element file and name it FlyoutAnchorManifest

4) Add Mapped Layout folder and add an application Page (DemoPage.aspx)

Solution structure will look like this.

Inside DemoPage.aspx , copy the below code snippet inside “PlaceHolderMain” placeholder.

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

<table>

<tr>

<td>

<asp:Label ID="lblHeaderName" runat="server" Text="Welcome to world of Microsoft technologies..."></asp:Label>

</td>

</tr>

</table>

</asp:Content>

This can be customized as per the requirement.

Now paste the below mentioned code in your element file.

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

<CommandUIDefinition

Location="Ribbon.Library.Share.Controls._children">

<FlyoutAnchor

Id="Ribbon.Library.Share.FlyoutAnchor"

Sequence="20"

LabelText="Profiles"

Image32by32="_layouts/1033/images/formatmap32x32.png"

TemplateAlias="o1">

<Button

Id="Ribbon.Library.Share.FlyoutAnchor.Menu.MenuSection.MyButton1"

Sequence="0"

Command="AppleCommand"

LabelText="Apple Profile"

TemplateAlias="o1"/>

</Controls>

</MenuSection>

<Button Id="Ribbon.Library.FlyoutAnchor.Menu.MenuSection1.MyButton2"

Sequence="0" Command="MicrosoftCommand" LabelText="Microsoft Profile" TemplateAlias="o1" />

</Controls>

</MenuSection>

</Menu>

</FlyoutAnchor>

</CommandUIDefinition>

</CommandUIDefinitions>

<CommandUIHandler

Command="AppleCommand"

CommandAction="JavaScript:

var options = {

url: '/_Layouts/DemoSharePoint/DemoPage.aspx'};

SP.UI.ModalDialog.showModalDialog(options);"/>

<CommandUIHandler

Command="MicrosoftCommand"

CommandAction="JavaScript:

var options = {

url: '/_Layouts/DemoSharePoint/DemoPage.aspx'};

SP.UI.ModalDialog.showModalDialog(options);"/>

</CommandUIHandlers>

</CommandUIExtension>

</CustomAction>

</Elements>

In this important points to look for is

<CommandUIHandler

Command="AppleCommand"

CommandAction="JavaScript:

var options = {

url: '/_Layouts/DemoSharePoint/DemoPage.aspx'};

SP.UI.ModalDialog.showModalDialog(options);"/>

While opening the page, you can pass values through query string as well and for getting the current site context and current page details, you need to write ECMA script . Will explain more about the ECMA script in coming posts.

So this pop window will like this

As you can see in the URL section we have given the path of our demo page. So this will open the demo page as the pop up dialog window.

Your job is done J

Customization Ribbon – Adding a Flyout anchor in the Ribbon - Part 3

noreply@blogger.com (Unknown) — Wed, 21 Mar 2012 06:01:00 +0000

Please go through the Part -1 and Part -2 for understanding the basics of Ribbon architecture and adding a button in the Ribbon.

In this article we will add Flyout anchor in the Ribbon of a list.

Steps : For creating the solution structure please refer part -2 of the series where I have explained the steps needed to set up the solution and creating the feature.

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

<CommandUIDefinition

Location="Ribbon.Library.Share.Controls._children">

<FlyoutAnchor

Id="Ribbon.Library.Share.FlyoutAnchor"

Sequence="20"

LabelText="Notifications"

Image32by32="_Layouts/NotificationImages/Notification.png"

TemplateAlias="o1">

<Button

Id="Ribbon.Library.Share.FlyoutAnchor.Menu.MenuSection.MyButton"

Sequence="0"

Command="AppleProfileCommand"

LabelText="Apple Profile"

TemplateAlias="o1"/>

</Controls>

</MenuSection>

<Button Id="Ribbon.Library.FlyoutAnchor.Menu.MenuSection1.EditNotification″"

Sequence="0" Command="MicrosoftPageCommand" LabelText="Microsoft Profile" TemplateAlias="o1" />

</Controls>

</MenuSection>

</Menu>

</CommandUIDefinitions>

<CommandUIHandler

Command="AppleProfileCommand"

CommandAction="javascript:alert('Hello Steve jobs !!!');"

<CommandUIHandler

Command="MicrosoftPageCommand"

CommandAction="javascript:alert('Hello Bill Gates !!!');"

</CommandUIHandlers>

</CommandUIExtension>

</CustomAction>

</Elements>

On Deploying the solution – flyout anchor will appear like this in the document library.

And on click of any of the items, a javascript method will fire as we have defined in the CommandUIHandlerExtension tag. In this case a simple javascript method will be called.

Your Job is done J

Continue reading for further posts on Customizing Ribbon

Customizing Ribbon in Sharepoint 2010 – Add a button in the Ribbon - Part -2

noreply@blogger.com (Unknown) — Fri, 16 Mar 2012 16:35:00 +0000

Here we will add a button in the Ribbon section of a Generic list in Sharepoint 2010. If you want to go through the basics of Ribbon control architecture, please read Part -1.
Steps :
1) Create an empty sharepoint solution (DemoSol).
2) Add a feature “DemoRibbonControlFeature” .
3) Add an empty element in the project which will be the element manifest file for the feature created above.

Solution structure will look like this.

4) Open Elements.xml file and paste the below code.

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

<CustomAction

Id="AlertButton"

RegistrationType="List"

RegistrationId="101"

Location="CommandUI.Ribbon">

<CommandUIDefinition

Location="Ribbon.Documents.New.Controls._children">

<Button

Id="Ribbon.Documents.New.Controls.AlertButton"

Alt="Alert"

Sequence="10"

Image32by32="/_Layouts/AlertImages/Alert.png"

Command="AlertCommand"

LabelText="Alert"

TemplateAlias="o2"/>

</CommandUIDefinition>

</CommandUIDefinitions>

<CommandUIHandler

Command="AlertCommand"

CommandAction="javascript:alert('You have done it !!!');" />

</CommandUIHandlers>

</CommandUIExtension>

</CustomAction>

</Elements>

Now we will go through the tags used in the element xml :

CustomAction : This is element that tell sharepoint that we want to add custom element in sharepoint.

RegistrationType : This tells where the custom element should be visible. In this case it is List.

RegistrationId : Registration ID tells which type of list you want to target to displaying the custom element . In this case we have used “101” for document library.

DocumentLib – 101 ,AnnouncementList : 104 Etc…

Location : It tells that the custome element should go to the Ribbon control of the list

CommandUIExtension : It contains the actual controls and actions that are to be taken with our custom action.

CommandUIDefinitions : Contains the definition of the control

Location: Location tag inside the CommandUIDefinitions tells where exactly this control should appear inside Ribbon. For more information here is the MSDN link.

Command: This tells the button which action to call when it's clicked. Command Action will be specified in CommandUIHandler element. Command name should be same at both the places

TemplateAlias: Can specify the size and styling of the button.

Sequence: This tag decides in which order buttons show up in inside the group.

Will call the simple alert message to on click of button.

<CommandUIHandler

Command="AlertCommand"

CommandAction="javascript:alert('You have done it !!!');" />

</CommandUIHandlers>

Your job is done J

Continue Reading Part -3

Customizing Ribbon in Sharepoint 2010 - Part -1

noreply@blogger.com (Unknown) — Fri, 16 Mar 2012 16:31:00 +0000

Sharepoint 2010 has come with a new Ribbon User Interface which is in line with the Microsoft other products like MS word and excel . In this post we will try to understand the Customization of Ribbon interface and also its architecture.

So the architecture of the Ribbon control is like

Ribbon -> Tab -> Group-> controls within the group.

These controls can be enabled or disabled but there visibility cannot be changed, they will always be visible.

Custom controls cannot be used inside Ribbon. Only following controls are permitted inside it are (1) button (2) Checkbox (3) Color Picker (4) Combo Box (5) Dropdown (6)Textbox (7)Toggle Button(8) split button,(9)spinner(10) fly out anchor.

Earlier in MOSS 2007 custom tag was used in the element manifest file to add a new element in the Site Actions menu or ECB menu. Same CustomAction tag will be used to add controls in the Ribbon.

Continue reading Part -2

How to access the Sharepoint control from Silverlight module through javascript

noreply@blogger.com (Unknown) — Fri, 02 Apr 2010 13:26:00 +0000

In the Previous post we accessed the public method inside the SIlverlight module from an .aspx page ,In this we are doing vice versa.

As per our objective we have a control inside a master page of a sharepoint site and a Silverlight control is hosted inside the webpart of a sharepoint page.So we need to access the sharepoint control when we click any button inside the Silverlight module through javascript.

So here are objective is to first access the control and then append a span tag to display some text inside the control on click of some button inside Silverlight control.

Followed Approach:

· Go to the Page load event and include the below code snippet

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

HtmlPage.RegisterScriptableObject("page", this);

HtmlDocument doc = HtmlPage.Document;

strControlInnerHTMLGlobal = doc.GetElementById("SharepointControlID").GetProperty("innerHTML");

strControlInnerHTML = strControlInnerHTMLGlobal + "<span >></span><span >Added in Sharepoint control through Silverlight button click </span>";

doc.GetElementById("SharepointControlID").SetProperty("innerHTML", strControlInnerHTML);

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

In above code snippet "SharepointControlID” is the ClientId of sharepoint control.

We are taking the object of control through its ClientId and then getting the innerHTML of the control which is in the form ‘span’ tags, and then we are appending the required span tag in the control.

Note: Here we are using GetProperty and SetProperty method through which we get the innerHTML of the control and then we can change the value as per our requirement.

Happy Coding J

How to access the silverlight method through javascript

noreply@blogger.com (Unknown) — Fri, 02 Apr 2010 13:07:00 +0000

Fisrt time I am writing anything about Silverlight part .

Here scenario is that we need to access a control inside silverlight application and then need to execute some operation on that control through javascript which is written outside the silverlight application ,now consider it inside the hosting .aspx page.

Since directly we cannot access the silverlight control in the javascript as on rendering of page ,silverlight control does not come in the viewsource of the page. So the approach to expose the control is to access the public method inside silverlight application and then perform the required operation.

To achieve this functionality we are following the below approach

In the Loaded event or the constructor of the page we have to make call to the ( RegisterScriptableObject) method. It accepts two parameters:

A name, which is used to make calls to the application.
An object, which will be called.

Code snippet which is required to be added in the loaded event of the

HtmlPage.RegisterScriptableObject("page", this);

Note: Here ‘this’ is the page object.

We can call only public methods in Silverlight application from javascript . If we want a method to be accessed from JavaScript, you have to add the ‘ScriptableMember’ attribute before the method declaration. Code Snippet which is to be added inside the xaml.cs of the control :

[ScriptableMember]

public void Start()

{

// Do Something

}

Now to access this public method from javascript .write this javascript method inside the .aspx page or the place from where you want to call the javascript.

function CallSilverLight() {

var slControl = document.getElementById("_slControl");

slControl.Content.page.Start();

}

</script>

1) Here id is the control ID of Silverlight control .

2) In this statement slControl.Content.page.Start();

‘page’ is the name which we have given while registering the Scriptable control in the loaded event of the page

HtmlPage.RegisterScriptableObject("page", this);

3) ‘Start’ is the name of the public method which is used to select the tab on click of breadcrumb menu which is inside sharepoint

And finally call this javascript from any control or on page load as per the requirement.

Initially this seems to be bit tricky ,but this is very usefull approach for interaction between Silverlight and .aspx page.

Please write to me if you face any problem while implementing it or if there is any other better approach.

Happy Coding J

Modifying Web.config programmatically using SPWebConfigModification class

noreply@blogger.com (Unknown) — Fri, 02 Apr 2010 12:43:00 +0000

Modifying Web.config programmatically

Often we need to add entries in web.config either for Webparts , Http Module ,Connection string or for any other module.For this either we need to add entries manually or we can automate this process using code.We can provide the user an option of On/Off for adding/removing the entries from the web.config . This can be done using feature and associating the feature receiver which will add the entries on Feature Activated and removes the entries on Deactivation of feature.

For this we will use the “SPWebConfigModification” class which will access the web.config of the web application through object model.

Objective: We will insert the HttpModule entries in the Web.config under the ‘HttpModule’ section

Steps are follows as:

Create a feature With scope as WebApplication/Site/Web. Here we will create the feature with scope as WebApplication.

In the Feature.xml

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

<Feature Id="{}"

Title="HTTP Module Configuration"

Description="This feature modifies the Web Application web.config to insert the HTTP Module entries."

Scope="WebApplication"

ReceiverAssembly="’AssemblyName’, Version=1.0.0.0, Culture=Neutral, PublicKeyToken= "

ReceiverClass="’ClassName’"

xmlns="http://schemas.microsoft.com/sharepoint/">

</Feature>

Note: Add the feature Receiver class reference in the feature.xml

FeatureReceiver Class code: FeatureActivated method

In this method we will add the entries in the Web.config

public override void FeatureActivated(SPFeatureReceiverProperties properties)

{

var oWebApp = properties.Feature.Parent as SPWebApplication;

try

{

if (!oWebApp.IsAdministrationWebApplication)

{

ModifyWebConfigEntries(oWebApp);

}

catch (Exception ex)

{

}

‘ModifyWebConfigEntries’ Method Code :

public void ModifyWebConfigEntries(SPWebApplication oWebApp)

{

#region Http Module Section

webConfigModifications = new SPWebConfigModification();

webConfigModifications.Path = "configuration/system.web/httpModules";

webConfigModifications.Name = "add[@name='CustomHttpModule']";

webConfigModifications.Sequence = 0;

webConfigModifications.Owner = "addCustomModule";

webConfigModifications.Type = SPWebConfigModification.SPWebConfigModificationType.EnsureChildNode;

webConfigModifications.Value = @"<add name='CustomHttpModule' type='ClassName,AssemblyName, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cfba5cfbc4661d2d' />";

oWebApp.WebConfigModifications.Add(webConfigModifications);

#endregion

SPWebService.ContentService.WebApplications[oWebApp.Id].Update();

//Applies the web config settings in all the web application in the farm

SPWebService.ContentService.WebApplications[oWebApp.Id].WebService.ApplyWebConfigModifications();

}

Note : This ApplyWebConfigModifications() method applies changes in all the web.config which are under the same farm.

Few things to note :

Path : This is the node under which we need to add the entry

Name : Name property is very useful because while retrieving from the database this entry should be in correct format.

Owner : This property is used while deleting the entries from the web.config programmatically

Now we have added the entries in the web.config programmatically.we need to remove these entries also when the feature is no longer in use.

While removing the entries we will take all the entries based on the owner property and delete the required entries.

var oWebApp = properties.Feature.Parent as SPWebApplication;

try

{

if (!oWebApp.IsAdministrationWebApplication)

{

// Web application is not central administration. Configuration changes are different.

DeleteWebConfigEntries(oWebApp);

}

catch (Exception ex)

{

}

‘DeleteWebConfigEntries’ Method :

public void DeleteWebConfigEntries(SPWebApplication oWebApp)

{

Collection<SPWebConfigModification> oCollection = oWebApp.WebConfigModifications;

int iStartCount = oCollection.Count;

for (int c = iStartCount - 1; c >= 0; c--)

{

SPWebConfigModification oModification = oCollection[c];

if (oModification.Owner == "addCustomModule")

oCollection.Remove(oModification);

}

if (iStartCount > oCollection.Count)

{

oWebApp.Update();

//Applies the web config settings in all the web application in the farm

SPFarm.Local.Services.GetValue<SPWebService>().ApplyWebConfigModifications();

}

Note :Here We are deleting the entries based on the owner property of the Modified entry.

First we take the collection of all the modifications in the Web.config through WebConfigModification method and then remove these entries.

So your job is done

Important thing to remember is that if we are adding the entries in the web.config programmatically then we should delete those entries progrmmatically only because while adding entries throug object model ,entries goes into the content DB of the site and on removing those entries manually this can cause conflict in the version which exist in the file structure and the version in the content DB.

Here is very good article from MSDN which explain this class in detail.

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.administration.spwebconfigmodification.aspx

Happy coding J

Function to write the cookies in the browser for infinite time in javascript

noreply@blogger.com (Unknown) — Mon, 05 Oct 2009 17:32:00 +0000

in this post our objective is to write the cookies through javascript for infinite time period(here we have given the time period as 100 days)ie.cookies never expires.In this javascript we have also accessed the textbox value and SPContext.Current.Web.CurrentUser.LoginName value .

Write this function inside the "Script" tag of the javascript.

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

function WriteCookies() {

//This is the way to access the value of controls in aspx page through javascript

var chk = ddocument.getElementById(<% SPHttpUtility.AddQuote(SPHttpUtility.NoEncode(txtBox.ClientID),Response.Output); %>);

//Way to access the current logged in user name from SPContext in javascript

var userLoginName =<% SPHttpUtility.AddQuote(SPHttpUtility.NoEncode(SPContext.Current.Web.CurrentUser.LoginName),Response.Output); %>;

if(chk!=null) {

if (chk.checked) {

value = 'TRUE';

} else {

value = 'FALSE';

}

name = 'KeyName'+'_'+userLoginName;

//To make the expiry if cookie as infinite

//Currently we have set the expiry date for 100 days.

var days = 100;

if (days) {

var date = new Date();

date.setTime(date.getTime() + (days * 24 * 60 * 60 * 1000));

var expires = "; expires=" + date.toGMTString();

}

else var expires = "";

document.cookie = name + "=" + value + expires + "; path=/";

}

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

So your job is done

Enjoy!!!

Reading the cookies from the browser in javascript

noreply@blogger.com (Unknown) — Mon, 05 Oct 2009 17:15:00 +0000

Here objective is to read the cookies value in javascript. Here is the function which needs to placed inside the "script" of the javascript.This function will read the cookie value from the available cookies in the browser based on the key passed for the cookie.

Here the function is called on page load
-------------------------------------------------------------------

function OnLoadFuntion() {

name = 'KeyName';

readCookie(name);

function readCookie(name) {

var nameEQ = name + "=";

var ca = document.cookie.split(';');

for (var i = 0; i < ca.length; i++) {

var c = ca[i];

while (c.charAt(0) == ' ') c = c.substring(1, c.length);

if (c.indexOf(nameEQ) == 0) {

if (c.substring(nameEQ.length, c.length) == 'TRUE') {

//Write functionality

}

return null;

}

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

So your job is done

Enjoy!!!

Using SharePoint:SPSecurityTrimmedControl to control the visibility of SiteActions

noreply@blogger.com (Unknown) — Mon, 05 Oct 2009 16:43:00 +0000

Here the objective is to control the behavior of SiteActions.We can hide these based on the current logged in user permissions.We can hide the control from all the users accept the SiteAdmin who is having SiteCollection Administrator rights.

For this we do not require any custom coding , Only thing is we have to modify the Master page. Modifying the default master page is not advisable ,so create your custom master page.For deploying master page as a feature in the site follow this link

Now follow these steps to hide SiteActions :

1) Open the custom master page in visual studio or notepad

2) Search for <SharePoint:SiteActions

3) Wrap this SiteActions control with

SharePoint:SPSecurityTrimmedControl ID="SPSecurityTrimmedControl" runat="server" PermissionsString="ManageSubwebs">

“<SharePoint:SiteActions>”

See the image below

Here we have to set certain parameters like “PermissionString”.This defines if the current logged in user is having this permissions set is able to view the “SiteAction” control. Since ManageWeb is the highest level of permission set ,so this will be available to SiteAdmin only.

To remove the control from Anonymous user use this

PermissionsString="BrowseDirectories"

We can also give the permission level in concatenated fashion also ..like comma(‘,’) way. These permissions work in ‘OR’ manner.

To view the SPBasePermission Enumeration follow this MSDN Link

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spbasepermissions.aspx

Similarly we can control the behavior of other controls like ViewAll Site Content

For this find <SharePoint:SPLinkButton in the master pagee

This control is already wrapped in SharePoint:SPSecurityTrimmedControl and is having Permission string as “ViewFormPages”.So We can set the permission string here as well based on our requirement.

See the code below present in the master page.

<SharePoint:SPSecurityTrimmedControl runat="server" permissionsstring="ViewFormPages">

<SharePoint:SPLinkButton id="idNavLinkViewAll" runat="server"

NavigateUrl="~site/_layouts/viewlsts.aspx" Text=""

AccessKey="" />

SharePoint:SPSecurityTrimmedControl>

So your Job is done.If you face any problem then do let me know.

Enjoy!!!

Creating a Custom Toolpart for webpart

noreply@blogger.com (Unknown) — Fri, 02 Oct 2009 10:35:00 +0000

Webpart comes with a default tool part which contains the configuration settings for the webpart. But often we have requirement to create the custom toolpart for the webpart having certain .net controls like dropdown list ,treeview etc which fetches data from the list or any other source and performs certain functionality based on the logic.

Webpart will look like this

Here is step by step process for creating webpart with custom toolpart:

1) Open visual studio

2) Create a new project with type class library

3) Inherit the class with Microsoft.SharePoint.WebPartPages.WebPart class

Below is the code for the webpart class

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

using System;

using System.ComponentModel;

using System.Runtime.InteropServices;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Xml.Serialization;

using Microsoft.SharePoint;

using Microsoft.SharePoint.WebPartPages;

namespace CustomToolPartWP

{

public class CustomWebPart : Microsoft.SharePoint.WebPartPages.WebPart

{

private string ddlvalue = string.Empty;

[Browsable(false), Category("Miscellaneous"),

WebPartStorage(Storage.Personal),

FriendlyName("ListValue"), Description("Text Property")]

public string DropDownListValue

{

get

{

return ddlvalue;

}

set

{

ddlvalue = value;

}

// Gets the custom tool parts for this Web Part by

/// overriding the GetToolParts method of the WebPart

/// base class. You must implement custom tool parts in

/// a separate class that derives from

/// Microsoft.SharePoint.WebPartPages.ToolPart.

///

/// An array of references to ToolPart objects.

///

public override ToolPart[] GetToolParts()

{

ToolPart[] toolparts = new ToolPart[3];

WebPartToolPart wptp = new WebPartToolPart();

CustomPropertyToolPart custom = new CustomPropertyToolPart();

toolparts[0] = custom;

toolparts[1] = wptp;

// This is the custom ToolPart.

toolparts[2] = new CustomToolPartWP.CustomToolPart();

return toolparts;

}

/// Render this Web Part to the output parameter specified.

/// The HTML writer to write out to

protected override void Render(HtmlTextWriter writer)

{

base.Render(writer);

writer.Write("Value Selected from dropdown is " + this.ddlvalue +

");

}

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

Lets discuss some important features of the webpart .Here we have declared one “DropDownListValue” ,it has some attributes like

a) Browsable : To appear this property in the wepart

b) Category: It shows the label name under which our custom control should render

c) WebPartStorage : There are two types of storage .One is personal ,this means that the value stored are specific to the logged in user ,other is shared ,in this saved value will be visible to all the users.

Once the webpart is done we need to add the class for toolpart which contains the code for custom toolpart. Follow these steps:

1) Add class to the solution

2) Inherit this class with Microsoft.SharePoint.WebPartPages.ToolPart

This is the sample code for the Toolpart which renders once dropdown list and selecting some value and clicking on Apply or Ok sets the value in the webpart.
------------------------------------------------------------------------

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Web.UI;

using System.Web.UI.WebControls;

using Microsoft.SharePoint;

using Microsoft.SharePoint.WebPartPages;

namespace CustomToolPartWP

{

///

/// Description of the toolpart. Override the GetToolParts method

/// in your Web Part class to invoke this toolpart. To establish

/// a reference to the Web Part the user has selected, use the

/// ParentToolPane.SelectedWebPart property.

class CustomToolPart : Microsoft.SharePoint.WebPartPages.ToolPart

{

private string inputname;

DropDownList dropdownList;

// an event handler for the Init event

private void CustomToolPart_Init(object sender,

System.EventArgs e )

{

inputname = this.UniqueID + "message";

}

///

/// Constructor for the class. A great place to set Set

/// default values for additional base class properties

/// here.

///

public CustomToolPart()

{

// Set default properties

this.Title="Select Value";

this.Init += new EventHandler(CustomToolPart_Init);

}

/// Called by the tool pane to apply property changes to

/// the selected Web Part.

public override void ApplyChanges()

{

CustomWebPart customWP = (CustomWebPart)

this.ParentToolPane.SelectedWebPart;

// Send the custom text to the Web Part.

customWP.DropDownListValue = dropdownList.SelectedItem.Value;

}

protected override void CreateChildControls()

{

//base.CreateChildControls();

dropdownList = new DropDownList();

dropdownList.Items.Add("item1");

dropdownList.Items.Add("item2");

dropdownList.Items.Add("item3");

dropdownList.Items.Add("item4");

CustomWebPart customWP = (CustomWebPart)

this.ParentToolPane.SelectedWebPart;

dropdownList.Items.FindByText(customWP.DropDownListValue).Selected = true;

this.Controls.Add(dropdownList);

}

/// If the ApplyChanges method succeeds, this method is

/// called by the tool pane to refresh the specified

/// property values in the toolpart user interface.

public override void SyncChanges()

{

// sync with the new property changes here

CustomWebPart customWP = (CustomWebPart)

this.ParentToolPane.SelectedWebPart;

customWP.DropDownListValue = dropdownList.SelectedItem.Value;

}

/// Called by the tool pane if the user discards changes

/// to the selected Web Part.

public override void CancelChanges()

{

}

/// Render this Tool part to the output parameter

/// specified.

/// The HTML writer to write out to

protected override void RenderToolPart(HtmlTextWriter output)

{

// Establish a reference to the Web Part.

CustomWebPart customWebPart = (CustomWebPart)

this.ParentToolPane.SelectedWebPart;

output.Write("Select value from drop down: ");

dropdownList.RenderControl(output);

}

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

After this compile the solution and deploy the webpart and put the dll in GAC or the bin folder of the webapplication

And your webpart is ready to use with custom toolpart.

There is a very good artilce on MSDN to create custom toolpart.

http://msdn.microsoft.com/en-us/library/dd584178(office.11).aspx

If you have queries than do post.

Your job is done J

Enjoy!!!

How to access the Content Place Holder and Control placed inside some place holder in master page programmatically

noreply@blogger.com (Unknown) — Tue, 29 Sep 2009 17:26:00 +0000

There is requirement to access the control placed inside the PlaceHolderMain in the master page.

We can place this code inside the CreateChild Control method:

Control customControl = this.Page.Master.FindControl("ControlName");

Similarly to access the Content Place inside CreateChildControl method of webpart use this code snippet :

ContentPlaceHolder contentPlaceHolder = (ContentPlaceHolder)Page.Master.FindControl("ContentPlaceHolderName");

So now your job is done J

If you have any queries then please let me know

Enjoy!!!

Exploring “Location” object in javascript

noreply@blogger.com (Unknown) — Sat, 26 Sep 2009 04:58:00 +0000

Javascript location object is the property of the window property.

Properties

hash - The URL anchor part including the leading hash mark if one exists This is the part of the URL that is used to point to point to a particular part of a page where a named anchor is. The hash is the part containing the # sign that points to the particular page location.
host - The URL hostname and port. The URL http://spvm:1234/pages/default.aspx has the host value of http://spvm:1234. The colon and port is only included when specified. The URL http://spvm:1234/pages/default.aspx has the host value spvm:1234.
hostname - The URL hostname section
href - The entire URL. The following code will load the home default page:

location.href = "http spvm:1234.com/"

The following code will display the URL of the current page:

document.write(location.href)

pathname - The URL pathname section
port - The URL port section.

protocol - The URL protocol section including the colon after the protocol name. The values are normally http: or file

search - The URL query string section. This is the section after and including the question mark.

target - The URL link's target name.

Methods

reload() - The current window document is reloaded. If a value of true is passed to the reload function, the reload is forced to do an HTTP GET of the document. This is not normally done but is useful when you think the server contents may be different from your cache.

replace(URL) - Requires a URL as a parameter. It loads the document at the URL on top of the current document. A new entry is not placed in the history object.

Calling javascript from the XSLT on page load.

noreply@blogger.com (Unknown) — Sat, 26 Sep 2009 04:48:00 +0000

This is the first article in exploring the power of javascript when called from XSLT.

XSLT is basically used to render the xml in specified format.Here the requirement is to call some javascript function when xslt is rendering the xml.

In this article we are calling javascript on page load .

Scenario : On page load we want to fill some value in text box coming coming from the property defined in the xml .So first we need to access the property value inside javascript and then on page load need to fill the value inside the textbox.

Here is the sample javascript to be used inside the sample.xsl file

<xsl:template name="picture">

function myFunction()

{

var url = ']]><xsl:value-of select="substring-before(@PictureUrl, ',')" />';

var txtBox = document.getElementById('textBox');

txtBox.value = url;

}

_spBodyOnLoadFunctionNames.push("myFunction");

]]>

script>

xsl:template>

Keep watching this space for more in javascript and XSLT.If you have done something then please share.

How to attach a process when activating or deactivating features from command prompt.

noreply@blogger.com (Unknown) — Sat, 26 Sep 2009 04:43:00 +0000

This is bit tricky one as often we have some feature receiver class with the feature and we want to debug it .

When we activate the feature through UI (ie from the site features) we attach the w3p process and debug the feature receiver code but this does not happen while doing the same from command prompt

So for this follow these steps :

1) Type the command to activate the feature in command prompt :

Stsadm –o activatefeature –name “feature name” –url

2) As soon u press enter , press Pause button from the keyboard.

There should not be any delay in these two actions as this is very fast process .

3) Now go to the solution in visual studio and attach the “stsadm” process from attach process tab

4) Now come to command prompt and press any key to resume the process.

Now you can debug the feature receiver code

So your job is done.

Enjoy!!!

How to get the Date Time from the regional settings of the page

noreply@blogger.com (Unknown) — Sat, 26 Sep 2009 04:41:00 +0000

To get the Date Time related information from the site’s Regional settings ,here is the sample code snippet.

SPSite site = new SPSite("http://spvm:1234/");

SPWeb web = site.OpenWeb();

DateTime dt = web.RegionalSettings.TimeZone.LocalTimeToUTC((DateTime.Now));

This way we can get the current time zone settings like which time zone we are using and date and time

So your job is done

Enjoy !!!

Add custom groups in the quicklaunch of the site

noreply@blogger.com (Unknown) — Sun, 20 Sep 2009 04:40:00 +0000

Objective is to add the custom created group in the quick launch of the site.I tried to explore the web and site object to get the handle of the people and group quick launch,but directoly it does not exposes anything..then i get this property to access the quicklaunch..

Here is the code sample..

site.AllProperties["vti_associategroups"] += ";" + oGroup.ID;
add custom group in the quicklaunch collection in the following way..

happy coding..

How to get the SP User ‘Owner” object of the site

noreply@blogger.com (Unknown) — Sun, 20 Sep 2009 04:39:00 +0000

Objective was create the custom group,and while creating custom group we need to specify the owner of the group,So we accessed the SPUser object of the owner in this way.This is the best way as there is no need of specifying any hard coded values.

SPUser owner =null;
owner = subSite.SiteGroups.GetByID(int.Parse(subSite.Properties["vti_associateownergroup"]));

Similarly Members group and visitor group can be accessed
SPUser member =null;
owner = subSite.SiteGroups.GetByID(int.Parse(subSite.Properties["vti_associatemembersgroup"]));

SPUser visitor =null;
owner = subSite.SiteGroups.GetByID(int.Parse(subSite.Properties["vti_associatevisitorgroup"]));

Apply custom master page on the application pages(Branding of Sharepoint Site)

noreply@blogger.com (Unknown) — Sun, 20 Sep 2009 04:39:00 +0000

Purpose : To apply custom master page on the application pages apart from the custom pages.
Normally in a sharepoint site ,we find that look and feel of the site is not consistent through out the site, there may be application pages which are different from the home page of the site.Now the problem is that since these are admin pages , so we cannot do much modification on these pages, and moreover if we go in sharepoint designer and changes the page from there than these changes will appear at farm level. So there is another way branding these admin pages is through HTTP Module, which will change the master page of a particular admin page at run time without effecting any thing on the page. This way we can have consistent look and feel through out the site.

Steps :
1) Open visual studio
2) Create a new project of type class library
3) Add sharepoint reference to it
4) Inherit the class from “IHttpModule” class

Follow this code:
namespace MyModule
{
public class LogoutModule : IHttpModule //inherit from the class
{
public void Init(HttpApplication app)
{
// Create a event handler to execute the process
app.PreRequestHandlerExecute += new EventHandler(app_PreRequestHandlerExecute);
}

void app_PreRequestHandlerExecute(object sender, EventArgs e)
{
HttpContext context = HttpContext.Current; // Get the current context of the pagee
Page page = context.CurrentHandler as Page;
if(page!=null)
{
page.PreInit +=new EventHandler(page_PreInit);
}
}
// Application master page can be changed only on the PreInit method of the page only
void page_PreInit(object sender, EventArgs e)
{
Page page = sender as Page;
if (page != null)
{
if (page.MasterPageFile.Contains("application.master"))
{
page.MasterPageFile = @"\_LAYOUTS\CustomApplicationMaster\Customapplication.master";
}
}
}
public void Dispose()
{
}
}
}

Your job is done..

Enjoy!!!

Redirect the page using HTTP module

noreply@blogger.com (Unknown) — Sun, 20 Sep 2009 04:38:00 +0000

Many times we need to redirect the page to some custom page based on some processing,this custom page can be some error page or any other page.So to achieve this we are using HttpModule and HttpHandler.

Steps :

Steps :
1) Open visual studio
2) Create a new project of type class library
3) Add sharepoint reference to it
4) Inherit the class from “IHttpModule” class

Follow this code:

---------------------------------------------
namespace MyModule
{
public class LogoutModule : IHttpModule //inherit from the class
{
public void Init(HttpApplication context)
{
// Create a event handler to execute the process
context.EndRequest += new EventHandler(context_EndRequest);
}

void context_EndRequest(object sender, EventArgs e)

{

Page page = HttpContext.Current.CurrentHandler as Page;

if (HttpContext.Current.Request.Url.Equals("http://spvm:1212/Pages/Default.aspx"))

{

HttpContext.Current.Response.Redirect("http://spvm:1212/sites/dms/Pages/Default.aspx");

}

}

}

}

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

To execute the HttpModule it should be registered in the Web.Config file of site and dll in the GAC.

This is the entry in the web.config file

Under <httpModules>tag Section

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

<add type="ClassName,AssemblyName, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9f4da00116c38ec5" />

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

Your job is done..

Enjoy!!!