Dhurjati

The steps to configure the Enterprise Search Center are as follows: Firstly go to Central Admin and create a web application Once the web application has been created, create a site and from the template section choose the template as " Enterprise - Enterprise Search Center " Under the section " My Site Settings " click on the option " Setup My Site " set the " Preferred Search Center ", here you need to provide the URL of the newly created site Reference:  http://sharepointgeorge.com/2010/configuring-enterprise-search-sharepoint-2010/

In order to setup and configure the My Site in SharePoint 2010, the steps to be followed are as follows: Logon to the Central Admin with the Admin credentials and create a new Web Application in the desired port Once the web application has been created, create a Site, while creating the site choose the site template as " Enterprise - My Site Host " After site has been created go to " Central Admin - Application Management - Service Applications - Manage Service Applications - User Profile Service Application " In the page that opens up click on the link " My Site Settings - Setup My Site " Under the section " My Site Host " provide the URL of the site that has been created in the steps above Go to " Central Admin - Application Management - Web Applications - Manage Web Application " and select the site created for My Site and make sure that the option " Self-Service Site Collection Management " has been set to " ...

Farm solution installation in Microsoft SharePoint is a system that enables developers to package custom farm solutions and administrators to deploy those farm solutions in a straightforward, safe and consistent manner. Specifically, installation refers to the process of uploading and unpacking solution packages (.wsp files) to front-end web servers and deploying the contents. Web Solution Package is a cabinet file that contains assemblies, resource files, features, images, application pages, site definitions etc. into single file. When the solution is being added it is stored in the Farm Solution Store table in the farm's configuration database. When adding a farm solution to the store, the contents of the solution file are validated against an .xsd file to verify that the files contained in it comply with the SharePoint Foundation schemas. If the verification fails, an error message is returned. If the verification succeeds, the process of adding the farm solution cont...

The .ddf (Data Directive File) is the file which contains the details of the files and where it needs to be deployed. It is used when the WSP file is being created, it is sent as a parameter to the MAKECAB.EXE file to generate the WSP file.

The steps to take a IIS backup in SharePoint are as follows: Start - Administrative Tools - IIS Manager Right click on the Computer Name - All Tasks - Back/Restore Click on the button "Restore" Provide a name and password for the backup created, this will create a backup The backup will be available under the path " C:\WINDOWS\system32\inetsrv\MetaBack ", the extension of the file would ".MDO"

Event Receivers are custom methods that are written to handle certain events within a list or document library. There are basically two types of event receivers, which are as follows: Synchronous Events - these events are like "ItemAdding" or "Uploading" Asynchronous Events - these events are like "ItemAdded" or "Uploaded"  The Event Receivers are either derived from the base class "SPListEventReceiver" or "SPItemEventReceiver".

STSADM is a command line tool provided by SharePoint to deploy, install and uninstall the features with a SharePoint Farm. To run the stsadm command the user needs to be part of the user group "WSS_ADMIN_WPG" and also to the administrator group. The executable file is location in the "bin" folder. Once the solution is ready for deploying in the server, one needs to run the following commands in the server: Adding the Solution : stsadm -o addsolution -filename C:\MHM.MainEmpDirListingCode.wsp Deploying the Solution : stsadm -o deploysolution -name MHM.MainEmpDirListingCode.wsp -url http://172.16.20.150:1975 -allowGacDeployment -immediate Retracting the Solution : stsadm -o retractsolution -name MHM.MainEmpDirListingCode.wsp -allcontenturls -immediate Removing the Solution : stsadm -o deletesolution -name MHM.MainEmpDirListingCode.wsp -override

Content Type is a collection of Site Columns that can be used throughout the site. Where as a site column is a predefined column, for e.g. it can be a single line of text, multiple lines etc.

The different types of authentication available in SharePoint are as follows: Classic Mode Authentication - uses NT authentication types such as Kerberos, NTLM, Basic, Digest and Anonymous Claims Based Authentication - uses claims identity against a trusted provider Windows Authentication - Form Based Authentication -

The difference between a list and a document library is as follows: Document Library is used to store documents where lists are used to store data in the form of rows and columns In a document library you can create documents as Word, Excel, PowerPoint, but in a list you cannot create a document but instead one can attach a document to a list item.

Previously the only way to access data from outside the SharePoint environment was through web services, now there is another way to access the data using the Client Object Model. There are three ways by which one can access the data from the SharePoint environment, which are as follows: .NET Managed Code Assembly In order to access the data the user needs to add a referecne to the following two DLLs from the ISAPI folder: Microsoft.SharePoint.Client Microsoft.SharePoint.Client.Runtime Silverlight Application Assembly In order to access the data the user needs to add a referecne to the following two DLLs from the ClientBin folder: Microsoft.SharePoint.Client.Silverlight Microsoft.SharePoint.Client.Silverlight.Runtime JavaScript For accessing data one needs to add a reference to the SP.js file, which will in turn call the SP.Runtime.js Client Object Model Architecture All the calls that are made from the client object model are in the form of an XML file which is f...

SharePoint has a 3 tier architecture which is as follows: Web Server Front End In this layer SharePoint is loaded and configured, the web sites resides in the IIS and we have 14-hive structure. Application Layer SharePoint provides various types of services, these services like the my site hosting, search, user profile and properties are hosted in this layer. Each of these services can be hosted in a separate machine if the need be. Database Layer This is the layer where we have the database resides.

CAML (Collaborative Application Markup Language) is a custom XML language provided by SharePoint which is used to manipulate the data stored within SharePoint.

A Site Collection is a collection of web sites under a web application. Under each site collection there will be a top level site and under that there can be multiple child sites. It is represented as "SPSite" in the object model and each web site under each of the site collection is represented as "SPWeb" in the object model.

A Web Application is a site in the IIS of the server, the web application can be created from within the Central Administration and has a content database associated with it. It can have multiple sites under it and can be accessed by the different zones within SharePoint. It is represented by the "SPWebApplication" object model.

A farm is a collection of SharePoint Servers sharing the same configuration database. The configuration database holds all the information needed to run the servers within the farm and is configured and controlled from the Central Administration.

Zones are separate logical paths mapping of the same application, the different zones that are available are as follows: Default Internet Intranet Extranet Custom

There are basically three types of pages in SharePoint for which we have a corresponding master page, which are as follows: Publishing Pages - these are those pages that are there in the Site Pages document library for e.g. default.aspx --- so we have the Site Master for these kinds of pages. Forms and Views Pages - these are the pages used to view the data stored in the lists and document libraries for e.g. AllItems.aspx --- so we have System Master for these kinds of pages. Application Pages - these are the pages that are stored in the _layouts folder in the server, these are the pages that are used for settings etc. --- so we have Application Master for these kinds of pages. The different types of master pages that are available in SharePoint 2010 are as follows: v4.master - this is the default master page default.master - this is a master page that provides backward compatibility with MOSS 2007 minimal.master -  simple.master - this is used for the accessdenie...

The reason we are using the properties.current.web in the event receiver is because it is not directly accessible over the browser. Since a normal custom application is accessible over the browser we can use the SPContext.Current.Web.

The steps to be followed to debug are as follows: Build and deploy the application Set the breakpoint in application Open up the Debug menu and view all the processes that are running For SharePoint Applications attach the process "w3wp.exe" and for SharePoint Timer job attach the process "OWSTIMER.exe" For SharePoint Application just refresh the application and for the timer jobs just run the job from the list

A workflow allows you to attach a business process to items in Microsoft SharePoint Foundation 2010. This process can control almost any aspect of an item in SharePoint Foundation 2010, including the life cycle of that item. For example, you could create a simple workflow that routes a document to a series of users for approval. Workflows can be as simple or complex as your business processes require. You can create workflows that the user initiates, or workflows that SharePoint Foundation 2010 automatically initiate based on some event, such as when an item is created or changed. SharePoint Foundation 2010 workflows are made available to end-users at the list or document-library level. Workflows can be added to documents or list items. Workflow can also be added to content types. Multiple workflows may be available for a given item. Multiple workflows can run simultaneously on the same item, but only one instance of a specific workflow can run on a specific item at any given time...

"AllowUnsafeUpdates" allows the user to make changes to the content database bypassing the security validation. When the update is being done this needs to be set to True and after the update is complete it has to be set to False.

URI (Uniform Resource Identifier) identifies a resource with by its location or by its name. It has two parts which are as follows: URL (Uniform Resource Locator) The URL identifies the location of the resource along with the ways to access the resource. URN (Uniform Resource Name) The URN identifies a resource by its name in a given namespace, but it does not provide the actual location of the resource and as to how it can accessed.