SharePoint 2010

Recently I started to look into some more detail at PowerShell and the SharePoint 2010 Snap-in. As a small exercise I wanted to create something (somewhat) usefull.

I came up with a small site structure install script for SP2010.

Read more: http://stefvanhooijdonk.com/2010/03/02/power-of-powershell-and-the-sharepoint-snap-in/

Did you know the SPDisposeCheck tool?

Well on the product blog is a great post on Disposing and SP2010. named “SharePoint 2007/2010 ‘Do Not Dispose Guidance’“

And even more usefull: SPDisposeCheck using Static Analysis in TFS ( 2010 )

You can download SPDisposeCheck as FxCop Ruleset here.

Cross post of: http://stefvanhooijdonk.com/2010/02/24/spdisposecheck-and-sharepoint-2010/

When you create a project in Visual Studio 2010 on one of the SharePoint project templates it will take care of all the packaging for you.

But when I was working on a project with custom workflow actions, the SafeControl entry that is needed for making it work was not added to the generated manifest.xml file.

Fortunately the package designer allows you to modify the template file it uses for generating this file. So open up the package designer, switch to the “Manifest” tab and add the assembly reference in the template yourself, but this time, include the SafeControl entry:

You can safely use the SharePoint project tokens in there as well, but only for the SafeControl entry. When you put it into the Assembly entry, the package generator won’t understand it and will add another assembly reference for the project output: