Cool SharePoint

Q. What has Changed in SharePoint 2010 Object model? Ans.   Microsoft has replaced the “12 hive” structure that we had in SharePoint 2007 with “14 Hive” structure in 2010. It has apparently added four new folders to its hive. The Folders are : * Policy * UserCode * WebClients * WebServices Q. How would you deploy WebPart Using Windows PowerShell? Ans.   At the Windows PowerShell command prompt (PS C:\>), type the below command : Install -SPWebPartPack -LiteralPath “FullPathofCabFile” -Name “Nameof WebPart” Q. How would you re-deploy the old custom solutions in SharePoint 2010.What Changes are needed to the old Solution files. Ans.   SharePoint 2010 object model contains many changes and enhancements, but our custom code will still compile and, will run as expected. You should however, rewrite and recompile any code that refers to files and resources in “12 hive”. For Details See : SharePoint Object Model – Backward Compatibility Q. How would you add a link in the Ribbon? Ans.

Stsadm will still be functional in SharePoint 2010. Powershell is not DOS based. Its .NET based. Windows PowerShell™ is the new command-line interface and scripting language specifically designed for system administrators that will be used for Microsoft® SharePoint® Server 2010 administration. Although both Cmd.exe and Stsadm.exe environments will be maintained for backward compatibility, SharePoint Server 2010 command-line administration will use Windows PowerShell. For practical purposes, you can view Windows PowerShell as complementing Cmd.exe in the Windows administration context and superseding Stsadm.exe for SharePoint administration. You might ask yourself, What’s so unique about Windows PowerShell? Well, unlike most command-line systems that accept and return text, Windows PowerShell supports and uses XML and objects. XML and object support is a pretty major change that brings entirely new tools and methods to greatly improve control, efficiency, and produc