SharePoint 2010 Best Practices (en-US)


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.

Advertisements

Using #jQuery to attach regular expression validation to a #SharePoint list form field>SP2010 >PS2010 >ProjectServer >in

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

SharePoint 2013 App Model advantages

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

Claims Provider in SharePoint 2010

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

The SharePoint 2013 Preview platform New APIs Set

The SharePoint 2013 Preview platform come with allot of type and development option with so much cool sets of APIs.
You have deferent type Applications for unlimited possibilities with you existing skills. Now this time you exclusive categories for SharePoint App. WebPart, SharePoint Page,SL App with in iframe. And also leverage for Client Devices  and Computers. By using Framework application you can exposed Asp.net,MVC Application. Also Power shell script and timer job available on SharePoint server.
For SharePoint 2013 you don’t need to learn SharePoint Programing you directly start development with you existing skill.
  SharePoint  APIs Impalement.
  • More Web Standards (Odata,Oauth)
  • More Client Side Support 
  • Improved Rest Model and EndPoint
  • Odata URL base Query Engine 
  • OAuth Web base identity system. 
  • Mobile Templates. 

  Type of APIs this SharePoint comes.
·         JavaScript (Browser base Client site programing with jquery)
·         Strong Support of javascript Client object Model with inline script and js.file.
·         All functionality is available for javascript same as like .net Framework and Silverlight client object model.
·         By using SharePoint 2013 Javascript Api  you can also do Custom.  It’s really help for developer for creating  sharepoint app with JavaScript SharePoint API because they can use Custom which is not allowed in server side coding.
·          
ASP.NET  (for Sever side Programing include you try MVC this time)
REST/OData  (More web standard for Developer play with SharePoint object in their application with rest endpoint which exposed by  Wcf dataservice. With OData standards and strong Brower base querys synx   )
WFC Data Service Reference
Example
Rest vs OOP
Feature
.NET Framework or Silverlight object models
JavaScript object model
REST/OData endpoints called from a Windows platform or JavaScript
Object-oriented programming
Yes
Yes
No
Batch processing
Yes
Yes
No
APIs for conditional processing and exception handling
Yes
No
No
Availability of LINQ syntax
Yes
No
No
Combining list data from different SharePoint web applications
Yes
No
Yes
Familiarity to experienced REST/OData developers
No
No
Yes
Similarity to non-Windows programming or JavaScript programming
No
Yes
Yes
Strong typing for list item fields
No (except with LINQ)
No
Yes, from Windows platform
No, from JavaScript
Leveraging jQuery, Knockout, and other JavaScript libraries
No
Yes
No, from Windows platform
Yes, from JavaScript
Reference
.NET Framework (strong Object Model with the Power of C#,vb.net,linq)
Windows Phone(out of the Box Support with new Template ,Push notification)
Rest OData and OAuth Support.
Silverlight (end to end Application Support with  Client OBJECT Model API. )
Windows PowerShell (for automation and administrative tasks for Server help for sp admins)

SharePoint Server 2013 Preview Installation for Standalone Machine (dev)

My First Installtion for SharePoint Server 2013 Preview for Development environment. But i have few issue like similar to sharepoint 2010 Beta. show i would like to Share and hope you can also same time. 
Per installation Check:
Hardware 

Software (not Required except SQL SERVER BUT FOR DEVELOPMENT I INSTALL VS2012)
Check Server Role
Developer will love to .net 4.5 feature in SharePoint 2013 so its Important 🙂
Runt SharePoint 2013 Perrequisiteinstaller.exe
Per-requisite Software has been installed and Configured

Run SharePoint 2013 Setup.exe
After the of Completion of basic installation 
SharePoint Product Configuration started 
Chose  New Server Option
If Configuration Failed on Creation and Configuration of database and Give Error some like that.
 Failed to connect to the configuration database.
An exception of type System.Management.Automation.CmdletInvocationException was thrown.  Additional exception information: ErrorCode:SubStatus:Service running under Network Service account in workgroup environment is not supported.​ 
If you running Application without AD or Stand Alone might you will received that error.
Solution 
   Go to Sql Server Management Studio
 >loacl/SharePoint (Instance)>security>Login>Administrator>Properties>ServerRole> and Check setadmin.
then go to Startmenu>SharePoint Power Shell>Execute this Command blow to for psconfig to
AppFabric Caching Service and Sql Server Agent to on these server on server.

command:
psconfig.exe -cmd Configdb Create SkipRegisterAsDistributedCacheHost
Then Run Again the SharePoint Product Configuration.
Error No 2
Might be You got another Error 
 Failed to connect to the configuration database.
An exception of type System.Management.Automation.CmdletInvocationException was thrown.  Additional exception information: ErrorCode:SubStatus:Service running under Network Service account in workgroup environment is not supported.​ 
SEARCH Application Service Error like SharePoint 2010 Beta 

but you see new instance of SharePoint Administration is working fine.

to See the error that you face in Product config. check Centeral Administration Services >Applications> Search Service Applicaiton you can see its stoped and show error.

First Time Ruining SharePoint 2013 Root Site(Team Site)

Hope you this article will help you install SharePoint 2013 it quit bit same experience like i had in SharePoint 2010 beta. enjoy SharePoint keep SharePointing…………………
Reference Link
Prepare for installation
more Reference 

By Usama Wahab Khan.