How to use PowerShell to uninstall a feature by GUID in SharePoint 2013

 it is quite handy and quick to uninstall a Farm Solution Feature in sharePoint 2013


Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction "SilentlyContinue"

#Get-SPFeature  to find the feature that we need to uninstall from the server
Get-SPFeature -Limit ALL | Where-Object {$_.DisplayName -like "*Wing*"}

DisplayName                    Id                                                       CompatibilityLevel Scope                        
-----------                    --                                       ------------------   -----                        
WingTipToys_WingTipsContact... fe80d321-83a0-4d7d-92ce-e7b84e6ef428     15 

# uninstall the feature using the GUID id
                                              
Uninstall-SPFeature -id "fe80d321-83a0-4d7d-92ce-e7b84e6ef428"

the beauty of Sharepoint 2013 Deveoper Dashboard

Microsoft introduced the developer Dashboard in SharePoint 2010, it is embedded in the page. which will help the developer trouble shooting the issue on the SharePoint page. the Developer DashBoard still is available in the SharePoint 2013 but with great improvement. The Developer DashBoard will be popup into
a separated page.

here is the screen of the SharePoint 2013 Developer DashBoard





Unfortunately it had been turn off by default. we must use the powershell script to turn it on


$DevDashboardSettings = [Microsoft.SharePoint.Administration.SPWebService]:: ` ContentService.DeveloperDashboardSettings
$DevDashboardSettings.DisplayLevel = 'On'
$DevDashboardsettings.Update()

after you execute the powershell script, then lauch the sharepoint web site, you should be able to spot an icon to launch the Developer DashBoard (I already circled the icon in red)

Very Handy PowerShell Command

I recently get involved in the development with Power Shell.  I found that some of power shell  command is

quite helpful for debug purpose.


Read-Host  will keep the power shell console window open when you right the power shell script and execute it by launching the Power Shell window. we can see the outcome of the script execution.


pause will  keep power shell console window open when you run the ps by using the windows batch file.


Set-Location will change the folder where the script stored.

-C put this in front of the comparison operator will solve the power shell case intensive issue in string comparison

(`) will add a line break to chop a long script into multiple lines