SPSherm.MyBlog » Reference

Deleting a SharePoint List using Powershell

Sherman — Wed, 24 Aug 2011 17:10:41 +0000

When I’m doing development tasks, there are times I need to quickly create and delete SharePoint content. Lists are one of those. Documenting a few different ways to delete a SharePoint 2010 list using Powershell.

Two lines:

$w = Get-SPWeb "http://sps2010"
$w.Lists.Delete([System.Guid]$w.Lists["My Custom List"].ID)

One line:

Get-SPWeb "http://sps2010" | Where-Object { $_.Lists.Delete([System.Guid]$_.Lists["My Custom List"].ID) }

Get-SPWeb "http://sps2010" | % { $_.Lists.Delete([System.Guid]$_.Lists["My Custom List"].ID) }

Event Receivers

Sherman — Tue, 26 Jan 2010 17:44:13 +0000

Two excellent resources for ramping up on SharePoint 2007 event receivers.

IIS7 Application Pool Reset

Sherman — Thu, 14 Jan 2010 21:21:16 +0000

In IIS6 on Windows Server 2003, we could recyle the application pool that hosted our SharePoint site in order to force the web application to perform a JIT compile. This would then reload any DLLs it required. This saved a considerable amount of time over an IISRESET.

That command is:

C:\windows\system32\IISApp.vbs /a "SP Site App Pool" /r

(Note that the first time you run IISAPP.vbs, you’ll get a few confirmation prompts.)

This VBS script does not exist in IIS7 on Windows Server 2008, but the good news is there is an even better command:

c:\windows\system32\inetsrv\AppCmd Recycle AppPool "SP Site App Pool"

Type “AppCmd /?” for a list of all the useful actions you might want perform against your IIS7 installation.

PortalSiteMapProvider Properties: IncludePages, DynamicChildLimit

Sherman — Tue, 23 Oct 2007 02:51:32 +0000

The PortalSiteMapProvider class is the base provider used by the four default “CMS” SiteMapProviders:

GlobalNavSiteMapProvider
CombinedNavSiteMapProvider
CurrentNavSiteMapProvider
CurrentNavSiteMapProviderNoEncode

That is, all of these SiteMapProviders use the same base code to generate a data source, but their “output” differs slightly due to the different attributes that are applied.

Recently, we wanted to filter out the pages from showing up in our left-navigation. You can do this at the rendering stage, but since the PortalSiteMapProvder gives us an IncludePages property, we can simply create a new entry in web.config for our “custom” provider, like this:

By default, there is also a 50 returned-items limit; we can set the DynamicChildLimit to “0″ to override this.

Of course, you can combine the different properties to come up with a combination you need. The next thing we would need to do is reference these new providers, and voila!

And if you haven’t read Chris Richard’s series of articles about MOSS Navigation and how to get better performance using the PortalSiteMapProvider, you really should…