Jul 08 2008
I’ve only recently been working SharePoint and I’m still trying to get my head around the line that separates Windows SharePoint Services (WSS) from Microsoft Office SharePoint Services (MOSS). Yesterday I was able to clarify a bit more of my uncertainty.
I have been trying to create a Workflow solution for a client but I just couldn’t get it to work on my machine – Windows 2008 Server, WSS 3, VS2008 with extensions for SharePoint v1.2 and WPSBuilder addin. The problem was being caused by the SharePoint Sequential Workflow having a reference to Microsoft.Office.Workflow.Tasks. Removing the reference fixed the compilation errors, however the workflow still didn’t want to play ball with WSS. The workflow would install and I could associate it with a document library however, whenever I started the workflow I would get a failed on startup message.
The only thing I have been able to do to get the VS2008 SharePoint extensions workflow project to compile and run on my machine – given my time constraints – is to install MOSS on my development machine – which is what the client is running anyway.
Workflow is built into WSS, however, it doesn’t seem to be readily supported with a project type in VS2008. My advice for those that don’t have the resources to upgrade to MOSS is to not bother with the SharePoint extensions for VS but to take a look at Andrew Connell’s SharePoint Project Utility Tool.