iSharePoint

One of my collegues called me as she had a problem with a Sharepoint Designer Workflow. Three of the five workflows had a problem. When you logged in as a user and tried to edit the workflow task Sharepoint was throwing an access denied error.

I had a look and told here to restore rights inherintance. Unfortunately this did not solve the problem. So it was time to have another look. Nothing I could see was out of the usual in the workflows nor in the permission settings (task list, workflow history list etc). Even assigning full control to all users did not help. In this case: Google is your friend! Googled it and came up with this

Turns out that if you add a workflow with Sharepoint Designer, assign tasks to users in that workflow and add users afterwards, the rights are not properly set for those new users. Solution is to republish the workflow through Sharepoint Designer. Even if you publish to c: the workflow will run fine with proper rights afterwards. I am not sure if this is a bug or by design…

roelhans Geen rubriek Sharepoint Designer

I usually use Subversion plus CruiseControl.NET and WSP Builder for automatic builds of WSP files for the Sharepoint DEV and TEST environments. Recently I have started a project for a customer that uses Team Foundation Server (TFS). Of course I wondered how to set up the same. Lo and behold it got twitted. So here is the link: http://blog.brianfarnhill.com/2008/12/30/how-to-get-tfs-to-automate-your-wsp-builds-with-wspbuilder/. Thanks @waldekm for bringing it to attention!

The thing that really shines for me is in step six: referencing if you have no MOSS installed on the build server. I have always used the first approach; dump the referenced dll in the GAC. I did not know about the possibilty of adding an extra reference path in the build project for TFS. Much more elegant than dumping it on the GAC.

roelhans Build Automation sharepoint, TFS, WSPBuilder