SharePoint 2007 x64 workflow with Visual Studio 2008?

Question

I have a development environment with 64-bit SharePoint 2007. I tried to create a SharePoint workflow with Visual Studio 2008 and received the error message "The 32-bit version of SharePoint Server is not installed. Install the 32-bit version of SharePoint Server." Is there any way to solve this problem?

Answer 1

Soon I will be in a similar scenario and studied this issue in advance, since I heard about this issue on blogs. Apparently, you can still develop up to 32 bits and then move it to a 64-bit server.

It seems that the problem is really in the Sharepoint extensions ... so if you don't use them (like SharePoint 2007 Sequential Workflow or SharePoint 2007 State Machine Workflow) and just create a workflow project, it seems to be the best success for some . (look in the comments to the publication)

Here's a bug tracked in Microsoft Connect , some members of the VS team provided a “job,” which I basically mentioned for the first time.

The bottom line is Microsoft’s tiny processing, given that it’s their “Showpiece” and they are pushing people towards a 64-bit platform. In two weeks I should feel it, if I come up with something else, I will send it back. Good luck

Answer 2

Yes, go with curtisk. Today I developed a common Windows workflow for SharePoint because I could not use extensions. You lose a little in ease of deployment, but there are many resources on which you can do this manually. This worked for me (at least part of its deployment anyway): -

http://blah.winsmarts.com/2008-7-Authoring_SharePoint_2007_Workflows_using_VS2008.aspx

Please note that in my case, I was working on a 32-bit Windows 2003 virtual machine, but was hosted on a 64-bit virtual server.

Answer 3

I had the same problem just now. I found that STSDEV has the exact project type as an option.

Therefore, use STSDEV to create such a project. Since it crashed into 64-bit Win2k3 with VseWSS 2008, it is better to use STSDEV instead.

Answer 4

We worked on this by creating workflows in the SharePoint designer and then simply merging and then incorporating them into WSP when deploying through Visual Studio using VseWSS.

PS: SharePoint Designer is now a free product.