Narasimha SharePoint 2010

This script will delete site collections from the SharePoint server completely. But we need to provide the site collection names to the Power Shell Script as a ";" separated values. Power Shell Script: Ex: $SiteCollection =  "http://SP-S2010/sites/TeamSite1;http://SP-S2010/sites/TeamSite2"  $SiteCollection = "http://SP-S2010/sites/TeamSite1;http://SP-S2010/sites/TeamSite2"  $SiteArray = $SiteCollection.Split(";") foreach($Site in $SiteArray)  {       Remove-SPSite –Identity $Site –GradualDelete –Confirm:$False }

Understanding the Client Object Model Understanding how the Client Object Model works will help you be more effective across all three versions. As shown in Figure 13-1, the Client Object Model fundamentally is a new Windows Communication Foundation (WCF) SharePoint service called Client.svc and three proxies: .NET CLR, Silverlight, and JavaScript. You program against the client proxies just as you do with any service. Calls to and from the server are sent in batches to increase network efficiency. Figure 1. Client Object Model Architecture Client Object Model architecture

Feature stapling is an interesting concept in the SharePoint world, that allows you to associate a feature with any site definition. This feature will be activated automatically when a new site is created  from the associated site definition. Feature stapling consists of two elements : --“Stapler” – the feature that specifies what features to be associated with site definitions <Elements xmlns=" http://schemas.microsoft.com/sharepoint/ "> <FeatureSiteTemplateAssociation Id="{Guid of the staplee feature}" TemplateName="SPSPERS#2" /> <FeatureSiteTemplateAssociation Id="{Guid of the another staplee feature}" TemplateName="SPSPERS#2" /> </Elements>  This example associates two features with the personal site definition in SharePoint 2013 ( in SharePoint 2010 the TemplateName would be SPSPERS#0 ) --“Staplee” – the feature associated with a site definition or the feature that applies the customi...