One Linner Concept Of Share Point 2010

             Single Signing in SharePoint

When a user signs in to SharePoint Server, the user's token is validated and then used to sign in to SharePoint. The user's token is a security token issued by a claims provider.

1.     Windows claims mode sign-in

2.     SAML passive sign-in mode

3.     ASP.NET membership and role passive sign-in

4.     Windows classic mode sign-in

5.     Anonymous access

Claims-Based Single Sign-On for Microsoft SharePoint 2010

Microsoft Office SharePoint Server 2007 provides a default single sign-on (SSO) service for the storage and mapping of credentials for use in connecting with third-party or back-end systems. Many companies already have developed an in-house credential storage system or use a solution other than Microsoft Single Sign-On. Instead of maintaining credential mapping in two places, Office SharePoint Server 2007 provides a mechanism, pluggable SSO, to specify an alternate SSO Provider to the standard SSO Provider in Office SharePoint Server 2007.

           Metadata cache in SharePoint

Metadata cache management

“Metadata Cache Management” reports the use of the metadata caches that store information about the three types of metadata caches: objects, indexes, and databases. This section also reports the number of object, index and database descriptors that were active during the sample interval, and the maximum number of descriptors that have been used since the server was last started. It also reports spinlock contention for the object and index metadata caches.

SPSecurity.RunWithElevatedPrivileges Method

RunWithElevatedPrivileges Method:

Executes the specified method with Full Control rights even if the user does not otherwise have Full Control.
A delegate method that is to run with elevated rights. This method runs under the Application Pool identity, which has site collection administrator privileges on all site collections hosted by that application pool.

SPSecurity.RunWithElevatedPrivileges(delegate()

{

    using (SPSite site = new SPSite(web.Site.ID))

    {

    // implementation details omitted

    }

});

                                            Client Object Model

Microsoft SharePoint 2010 Software Development Kit (SDK) introduces three new client APIs that allow you to interact with SharePoint sites from script that executes in the browser

1.      . from code (no earlier than Microsoft .NET Framework 3.5) that executes in a .NET managed application, or   

2.      from code that executes in a Microsoft Silverlight 2.0 application. 

3.      The new ECMAScript (JavaScript, JScript),

Timer Jobs

1.      Timer Jobs can be scheduled for automating jobs inside SharePoint 2010

2.      SPJobDefinition is the base class for Timer Job

3.      Create Event Receiver Feature to create or delete the timer job

4.      SPFeatureReceiver is the base class for the event receiver

5.      The feature gets deployed in the 14hive folder

6.      OWSTIMER.EXE is the process executing Timer Jobs

Wsp Solution file add,Install,Update,Uninstall,Remove using with Powershell

To Add the Solution in Sharepoint

Add-SPSolution C:\YourFolder\SampleWebPart.wsp

To Install the Solution to your Sharepoint

Install-SPSolution -identity SampleWebPart.wsp -WebApplication http://yoursharepointserver –GACDeployment

To Update your Solution in Sharepoint
you will need this if you want to update the Webpart that is already installed

Update-SPSolution –Identity SampleWebPart.wsp –LiteralPath C:\YourFolder\SampleWebPart.wsp –GACDeployment

Now if something went horribly wrong or you just want to uninstall it you have to run this two commands

To Uninstall a Solution in Sharepoint

Uninstall-SPSolution –Identity SampleWebPart.wsp –WebApplication http://yoursharepointserver

Then

Remove a solution from Sharepoint

Remove-SPSolution –Identity SampleWebPart.wsp

 SharePoint  Server Object Model Structure

SPFarm -> SPServer -> SPServices - >SPWebServices  ->SPWebApplication  ->SPSite Collection     -> SPWeb  ->SPList  ->SPField  ->SPItem ->SPFile ->SPFolder

                      WebMethod

The WebMethod Attribute

The WebMethod attribute, first used in Example 2-1, tells .NET that a particular public method should be exposed as a web-callable method. The WebMethod attribute has six associated properties to document and change the behavior of your web method. They are:

1.      Description

2.      MessageName

3.      EnableSession

4.      CacheDuration

5.      TransactionOption

6.      BufferResponse

The first two properties are used to document a web method, while the others affect its behavior. In the following sections, we'll introduce each briefly.