Follow in Twitter & Facebook


Like in Facebook

Powered By Blogger Widgets

Free Download

FREE Tools


Monday, January 30, 2012

Change Time Zone in SharePoint 2010 site

- No comments
We will discuss here how we can change the time zone in a SharePoint 2010 site. To change the time zone user should have admin access, so that he can able to access the Site Settings page.

Step-1: Go to your Site Actions -> then site settings as shown in the figure below.
Step-2: From the Site Settings page Navigate to the Site Administration section and click on

Regional settings as shown in the figure below.

Step-3: This will open your Regional Settings page which page is used for Use this page to set regional settings such as the locale and time zone.

In that page navigate to the Time Zone section and change your required time zone from your drop down list as shown in the figure below.


Then click on OK, Your new time zone will be saved.

Thursday, January 26, 2012

Feature Receiver in SharePoint 2010.

- No comments
We can also able to add a Feture Receiver to a Feture defination to extend the functionality of  the feature definition in SharePoint 2010.

A Feature Receiver allows you to write event handlers in a managed programming language such as C# or VB.These event handlers are executed during feature-specific events such as feature activation and feature deactivation.

For example, you can write an event handler that fires during feature activation and performs routine initialization tasks such as creating new lists and adding list items, adding pages, navigation links and Web Part instances.

To create a Feature Receiver, you start by adding a new class to your project that inherits from  the SPFeatureReceiver class defined in the Microsoft.SharePoint namespace. Next, you override methods defined in SPFeatureReceiver, such as FeatureActivated and FeatureDeactivating.

Monday, January 23, 2012

Feature Definition in SharePoint 2010.

- No comments
A feature definition provides a mechanism for adding elements to a target site or site collection through a process known as feature activation. The types of elements that can be added to a site include menu commands,link commands, page templates, page instances, list definitions, list instances, event handlers, and workflows.

Physically, a feature definition is implemented with a set of files that are deployed within a dedicated directory created inside the FEATURES directory. More specifically, a feature’s directory contains one or more XML-based files that contain Collaborative Application Markup Language (CAML). The only file required for every feature definition is the feature manifest file, which must be named feature.xml and must be placed at the root of the feature’s directory.

A feature definition often contains one or more XML files known as element manifests that define the elements that make up the feature definition.

The directory for a feature definition can also contain several other types of files for elements such as list definitions and page templates as well as other kinds of resources, such as image files, Cascading Style Sheets (CSS) files, and JavaScript files.

Sunday, January 22, 2012

Add Remove Site Collection Administrators in SharePoint 2010

- 1 comment
Site collection administrators are very much important because they have full control over all the web sites in the site collection in SharePoint 2010. You can add or remove site administrators easily.

To add site collection administrator go to Site Actions -> Site Permissions as shown in the figure below.


It will open the pemissions page where you can create groups, can give permissions to users. In the ribbon click on Site Collection Administrators as shown in the figure below.

This will open the Add remove Site collection Administrators dialog box. There you can add users whom you want to make site collection administrators separated by commas and also you can remove users from the Site Administrators group also as shown in the figure below.


Also you can visit this link for more information.

Friday, January 20, 2012

SharePoint Server Object Model.

- No comments
In 2007,SharePoint provided only Object model , it is not termed as SharePoint server object Model.
Here in SP 2010,it is known as SharePoint 2010 provides different object models like Client Object Model, Server object model, object model for silverlight application and object model for JScript application.

Enable Developer Dashboard Property in SharePoint 2010.

- No comments
The Developer Dashboard is a user interface component built into SharePoint 2010 Foundation that displays diagnostic information that can be useful to developers and to farm administrators in diagnosing problems with the farm.

By default, the Developer Dashboard is disabled.

A way to enable and disable the Developer Dashboard is by writing a console application that configures a few farm-wide properties through the server-side object model. follow the below line of code.

using System;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Administration;
namespace EnableDeveloperDashboard
{
class Program
{
static void Main()
{
SPDeveloperDashboardSettings settings =
SPWebService.ContentService.DeveloperDashboardSettings;
settings.DisplayLevel = SPDeveloperDashboardLevel.On;
settings.TraceEnabled = true;
settings.Update();
}
}
}

To disable the Dashboard property chang the following line of code

settings.DisplayLevel = SPDeveloperDashboardLevel.Off;

You can also check some SharePoint 2010 Articles and SharePoint 2010 and Asp.Net Jobs.

Friday, January 13, 2012

SharePoint server 2010 Workflows:

- No comments
Introduction:
In this article we will discuss what are the out of workflow presented in SharePoint 2010. Also you can read this article on how to create a sequential workflow using Visual Studio 2010?

Description:
Previously SharePoint Foundation ships with only one generic workflow template, the three-state workflow template that can be used across multiple scenarios. On the other hand, SharePoint Server contains additional workflow templates, such as the following:

(1)Approval: SharePoint 2010 approval workflow Provides an approval mechanism for documents.

(2)Collect Feedback: It Provides a feedback mechanism for documents.

(3)Collect Signatures: It Provides a mechanism for collecting digital signatures for completing a document.

(4)Disposition Approval: It Provides an expiration and retention mechanism that allows you to decide whether to retain or delete expired documents. This workflow can be started only by using the browser.

(5)Group Approval: It Similar to the Approval workflow; however, it is available only in East Asian versions of SharePoint Server.

(6)Translation Management: It Provides a mechanism for document translation by creating copies of documents to be translated and also assigns tasks to translators.
This workflow is available only when you create the SharePoint Server Translation
Management library.

You can also check some SharePoint 2010 workflow articles.

Sunday, January 8, 2012

Benefits of Using InfoPath 2010 with SharePoint 2010

- No comments
SharePoint libraries known as form libraries is responsible for storing and managing infopath forms. So we will get benifits of the workflow, columns and user defined views.

Reporting and Business Intelligence capabilities in SharePoint 2010 help you extract the data from your forms and present it to business users.

The InfoPath data can be “promoted” to populate SharePoint columns, and thus numerous
opportunities exist to reuse the information, including Key Performance Indicators (KPIs), Business Intelligence dashboards/reports, and more.

InfoPath supports integration of data to many data source types, including web services, XML files, and databases.

You can also check SharePoint Infopath 2010 Video tutorial.

Wednesday, January 4, 2012

Three ways to view the Survey data.

- No comments
SharePoint 2010 Foundation provides three ways to display a quick summary of the survey data:

1- Overview:
 This view displays the survey’s name, description, date, and time of creation, as well as the number of responses.

2- Graphical Summary:
 This view displays the response data for each survey question in the form of a graph. The number of responses is displayed as a value and as a percentage of the total number of responses received.

3- All Responses:
 This view displays a list of each survey response, the date and time the response was last modified, whether the user completed the survey, and the name of the user who created it, if applicable.