Tuesday, February 22, 2011

Powershell Script for Setting SharePoint's Developer Dashboard

Here's a script that can be used to enable, disable or allow toggle of the Developer Dashboard in SharePoint 2010. Note that if using the V3 interface, you can customize the master page to add the dashboard control so that it will render:
<SharePoint:DeveloperDashboard runat="server" />



$choiceOnDemand = New-Object System.Management.Automation.Host.ChoiceDescription `
        "On &Demand","Dashboard can be toggled via icon near Welcome Menu"
$choiceOn = New-Object System.Management.Automation.Host.ChoiceDescription `
        "&On","Dashboard is on for all pages"
$choiceOff = New-Object System.Management.Automation.Host.ChoiceDescription `
        "O&ff","Dashboard is off"

$choices = [System.Management.Automation.Host.ChoiceDescription[]]($choiceOnDemand, $choiceOn, $choiceOff)
$caption = "Specify Developer Dashboard Setting for Farm"
$message = "Current the dashboard is: $($ddsetting.DisplayLevel)"
$result = $Host.UI.PromptForChoice($caption,$message,$choices,0)

switch ($result) {
    0 { Write-Host 'Dashboard is now On Demand, toggle via icon near Welcome Menu'
    1 { Write-Host 'Dashboard is now On'  
    2 { Write-Host "Dashboard is now Off"
    default { throw "Developer Error"}

if ($result -ne 2) {
  $ddsetting.TraceEnabled = $true
  Write-Host @"
  Trace was also enabled.
  Note: v3 interface requires this on the master page for the Dashboard to render:
     <SharePoint:DeveloperDashboard runat="server" />
} else {
    $ddsetting.TraceEnabled = $false;
    Write-Host "Trace was also disabled."

$ddsetting.RequiredPermissions = 'EmptyMask'


It also turns on trace, so it can be handy to find hard to debug problems.
In my case, it was helpful to find out why a delegate control wasn't rendering:
Tag(8e1n) Failed to create a user control from virtual path '/_controltemplates/CustomSearch.ascx': 
'Microsoft.SharePoint.WebControls.SearchArea, Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c' 
is not allowed here because it does not extend class 'System.Web.UI.UserControl'.

Based on approach from Praveen Battula's blog


Wim said...

Hi Thanks for posting this. I run into the same error on the searcharea control after upgrading to sp2010 could you tell me what was the problem by you and how did you solved it?


Clark Updike said...

I believe the problem is caused by using a SharePoint 2007 user control in SharePoint 2010. I haven't tried it, but I assumed the fix was to re-implement the user control by extending the System.Web.UI.UserControl in 2010. Have you tried that?

Praveen Battula said...

Hi Clark,
Please update the link to the right url:

Right now it's pointing to the wrong one.