Developing Workflows Not Possible on 64-Bit SharePoint
As most companies are moving to the 64-bit platform of Windows Server and MOSS, more SharePoint developers are adopting this as their main dev environment.
However, if you plan to develop SharePoint workflows in Visual Studio 2008 on your new 64-bit box, you’re going to be disappointed.
Upon creating a new workflow in VS, an “Object reference not set to an instance of an object”-error pops up:
You can still get to the next step in the process where you have to chose the site which will be used to debug the workflow. Here too, you will be faced with an error:
The solution
Well, there isn’t any. Not right now anyway.
The only thing you can do is to continue developing in your old 32-bit environment and then move your WSP to the 64-bit box for installation.
All this is not a bug per se, rather, it’s down to Microsoft’s lack of resources in their dev team:
(source)
Hmm…
There’s definitely a way around the 64bit issue, because I’ve built MANY workflows on my windows 2008, 64bit box. Maybe it’s a 2k3 thing. All I know is if you don’t use the SharePoint extensions and you create a generic .NET workflow, create your own feature/wsp to deploy it, you can build/deploy/unit test on a 64bit box just fine. Have you tried not using the sharepoint extensions and/or win2k8?
Phil
Phil Wicklund
January 23, 2009 at 3:28 am
Phil, you’re right – it’s the SharePoint extensions that are causing the problems.
Since most developers rely on the convenience of the extensions, I assume that the 64-bit problem is a widespread one.
We really shouldn’t have to resort to these workarounds to develop in a 64-bit environment, I’m sure you agree
thomassondergaard
January 24, 2009 at 1:28 pm
You know what I want to know? Why VSeWSS works perfectly to deploy other solutions like webparts but not workflows….Anyone?
Brady Huskey
June 8, 2009 at 2:30 pm
Microsoft didn’t develop 64bit supported workflow extensions for VS. Plain and simple.
They sold everyone on 64 bit servers, and sold them on SharePoint, and didn’t make the two compatible.
Think of it as someone selling you a microwave and set of metal bowls for it. All you get is a bunch of pissed off consumers.
TheGuy
September 4, 2009 at 4:43 pm
does anybody know how is possible to move my WSP to the 64-bit box for installation
I implement my workflow in 32 bit and made wsp file but when I add the solution in 64 bit I can not see the workflow for specific list?
Laleh
December 18, 2009 at 4:27 pm
My only remaining problem was getting debugging working in x64. I resolved it here, http://wynv.blogspot.com/2010/02/debugging-wss-3sharepoint-2007.html
Wyn V
February 17, 2010 at 3:52 pm
[...] Developing workflows on server looks like they crash: http://sharepointsharpener.wordpress.com/2009/01/12/developing-workflows-not-possible-on-64-bit-shar… [...]
MOSS 2007 Migrating to MS Server 2008 64-bit Drija
November 17, 2010 at 6:17 am