Replaced By App Solution :).

• Intro
• Performance
• Planning
• Installation, Removal, Configuration, and Operation
• Deployment
• Virtualization
• Real Life Usage
• Backup and Recovery
• Development
• Search
• Upgrade and Migration
• Extranet Environments
• Farms
• Top 10 Blogs to Follow
• Top 5 SharePoint Books
• Top 10 SharePoint Tools

Intro

Best practices are, and rightfully so, always a much sought-after topic. There are various kinds of best practices:

• Microsoft best practices. In real life, these are the most important ones to know, as most companies implementing SharePoint best practices have a tendency to follow as much of these as possibly can. Independent consultants doing architecture and code reviews will certainly take a look at these as well. In general, you can safely say that best practices endorsed by Microsoft have an added bonus and it will be mentioned whenever this is the case.
• Best practices. These practices are patterns that have proven themselves over and over again as a way to achieve a high quality of your solutions, and it's completely irrelevant who proposed them. Often MS best practices will also fall in this category. In real life, these practices should be the most important ones to follow.
• Practices. These are just approaches that are reused over and over again, but not necessarily the best ones. Wiki's are a great way to discern best practices from practices. It's certainly possible that this page refers to these "Practices of the 3rd kind", but hopefully, the SharePoint community will eventually filter them out. Therefore, everybody is invited and encouraged to actively participate in the various best practices discussions.

This Wiki page contains an overview of SharePoint 2010 Best Practices of all kinds, divided by categories.

On one of my current projects I have had cause to ensure that no special characters are in the Title field of a SharePoint 2010 list form.

This is because we are using the Title field as the Plan Name in a Project Create process in Project Server 2010.  As a result we need to ensure that the Event Handler we are creating has validated data that the PS2010 PSI Web Service can accept for the Plan Name.

I created the following script to validate the data being entered into the Title field of the list form as it is being entered.

I manipulate the Save Buttons in the ribbon and the list form to ensure that the user cannot enter invalid data into the form.

To ensure a good user experience, I add an extra

element next to the Title field to notify the user of what is going on.

Greate Article by Giles Hamson

Reference http://spandps.com/2011/01/19/using-jquery-to-attach-regular-expression-validation-to-a-sharepoint-list-form-field-sp2010-ps2010-projectserver-in/

SharePoint 2013 applicaiton model is very strong approach for developer to leverage there skil and developer wornderful apps except using any sever side code. as we know Sandbox solution is deprecating in sharePoint 2013 because of so many ressones. but SharePoint 2013 open new door for developer to develop,market,earm Apps.

•  Easy install,buy from App Market.
•  Easy to sale and market on App Store.
•  Safe SP Extentions for admin. easy Upgrads and deployments.
•  use non sharepoint progamining skills like qjuery,html5,mvc to create beautiful app.
•  use cross-platform standards (HTML, REST, OData, JavaScript, and OAuth_. 
•  leverage SharePoint Cross Domain js libaries and sharepoint Data with oAuth. SharePoint rest/OData     Service. to use sharePoint Objects like Site,list,libaries.
•  They maximize your flexibility in developing future upgrades.

Reference http://msdn.microsoft.com/en-us/library/jj163902(v=office.15).aspx

WebPart Zone Render As Html Div

A Claims Provider in SharePoint 2010 issue claims and pakages claims into securty tokens. how claim wok. first user get the token from claim provider in sp then login into SharePoint 2010. mostly it use for to augment claims and provide name resolution.
Claims augmentation start after user login to Claims Authentication Site. to remeber that the user is running on claim in authentication sharepoint 2010 site.it can be

1 widdows (NTLM(Out of box default.) or Kerberos Protocol)

2 form-Based Auth (by using ASpnet membership role provider framework)

3 Security Assertions Markup Language (SAML) claims (when you log on by using a security token service (STS), such as Active Directory Federation Services (AD FS) 2.0)

like most commonly problem in share point 2010 with search resolve in People Picker for trusted Login Providers. for example if your typing in Seach of public picker to validate user and its not resolving. to solve this Problem in sp2010  you have two ways.
 Custom Claim Provider
http://blogs.technet.com/b/speschka/archive/2010/03/13/writing-a-custom-claims-provider-for-sharepoint-2010-part-1.aspx
Replace the Dfault Claims Provider with your own.

$trusted = Get-SPTrustedIdentityTokenIssuer -Identity "Trusted Login Provider Name Goes Here"
$trusted.ClaimProviderName = “name of your custom claim provider”  //in your claim provider you need to override the SPClaimProvider.Name; use that value here
$trusted.Update();



Reference
http://msdn.microsoft.com/en-us/library/gg251994.aspx
Writte Code for claim  Provider Walkthrough
http://msdn.microsoft.com/en-us/library/ff699494.aspx
Creating Custom Claim Provider
http://msdn.microsoft.com/en-us/library/gg615945.aspx
Case Study
http://technet.microsoft.com/en-us/library/hh427307.aspx
Claim Based Architecture
http://msdn.microsoft.com/en-us/library/hh394901.aspx
http://msdn.microsoft.com/en-us/library/gg552609.aspx
sample
http://blogs.technet.com/b/speschka/archive/2010/03/13/writing-a-custom-claims-provider-for-sharepoint-2010-part-1.aspx