Force Visual Studio 2010 to add a SafeControl Entry

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:

Bookmark to:

Related posts:

1. Getting Custom Workflow Activities into SharePoint Designer 2010
2. Tam Tam Lauches Soccerino – World Cup 2010 Pool for SharePoint AND Facebook
3. SharePoint Server 2010 User Profile System
4. Issues deploying FAST Search Server 2010 Beta
5. SharePoint 2010 Search: Property Restriction in Keyword Queries