Basic PowerShell for SharePoint and the Equivalent STSADM used in Earlier Version

This is a simple list down of basic PowerShell commands used in command line deployments in SharePoint. [SP 2010 and 2013]  &
The equivalent STSADM commands used in SharePoint 2007 ... back in the day ;)


1. Adding a new WSP to farm solution

SP 2010/2013 PowerShell	Add-SPSolution -LiteralPath "C:\FolderName\Solution.wsp"
SP 2007  Stsadm	stsadm -o addsolution -filename "Solution.wsp" [Assuming command runs from the correct folder location]

2. Deploy WSP 

SP 2010/2013 PowerShell

Install-SPSolution -Identity "Solution.wsp" -WebApplication "http://WebSiteUrl" -CASPolicies -GACDeployment -Local -Force AllWebApplications vs WebApplication - All allows the wsp to be deployed in all SP web applocations. WebApplication - allows the wsp to be deployed to a target web app CASPolicies - Allows Code Access Security Policies to be deployed [optional] GACDeployment - Allows DLL installation in the global assembly cache [optional] Force [optional] Local - Deploys only in the current server [optional]

SP 2007  Stsadm

stsadm -o deploysolution -name "SolutionName" -url "Site URL" -immediate -allowgacdeployment -allowcaspolicies -force instead of -url, you can use -allcontenturls  instead of -immediate, you can use -time "time to deploy" GACDeployment - Allows DLL installation in the global assembly cache [optional]

3. Activate feature

SP 2010/2013 PowerShell	Enable-SPFeature –identity "FeatureName" -URL http://WebSiteUrl
SP 2007  Stsadm	stsadm -o activatefeature -id feature_ID -url http://WebSiteUrl -force [Instead of -Id, you can use -filename or -name with appropriate values]

4. De-activate feature

SP 2010/2013 PowerShell	Disable-SPFeature –identity "FeatureName" -URL http://WebSiteUrl
SP 2007  Stsadm	stsadm -o deactivatefeature -id feature_ID -url http://WebSiteUrl [Instead of -Id, you can use -filename or -name with appropriate values]

5. Retract WSP 

SP 2010/2013 PowerShell	Uninstall-SPSolution -Identity "Solution.wsp" -WebApplication http://WebSiteUrl
SP 2007  Stsadm	stsadm -o retractsolution -name "Solution.wsp" -url http://WebSiteUrl -immediate  [Instead of -immediate, you can use -time "TimeToRun"]

6. Remove WSP from SharePoint farm

SP 2010/2013 PowerShell	Remove-SPSolution -Identity "Solution.wsp"
SP 2007  Stsadm	stsadm -o deletesolution -name "Solution.wsp"

This version of Visual Studio does not have the following project types installed or does not support them

You might come across instances where you get the below message when opening SharePoint solutions in Visual Studio 2012.

"This version of Visual Studio does not have the following project types installed or does not support them"

1) The immediate remedy that pops into mind is to update the Visual Studio 2012 version.

The latest update for Visual Studio 2012, as of now is Update 4 (Released: November 13, 2013). Could get it from the link:  Visual Studio 2012 Update

2) Once that's done, you might get the following message on project load.

"An error occurred while trying to load some required components. Please ensure that prerequisite components are installed"

• Microsoft Web Developer Tools
• Microsoft Exchange Web Services

Possibilities are that either

  You don't have the "Microsoft Office Developer Tools for Visual Studio 2012" OR

  The installed tool is not complete.

Solution:

• If the tool is already installed, uninstall through Control panel,
• Download  Web Platform Installer   
• Use the Web Platform Installer to install the tool.