Choosing vsto2007 SharePoint 2007 workflow project on Windows2003/64 running SharePoint 2007 64 bit edition locally causes a "Object reference not set to an instance of an object" dialog to pop up. Additionally, attempts to continue the wizard fail due to it being unable to detect the local instance of SharePont/64.
I have marked this a blocking issue even though it is possible to work around it manually. However, when one commits to a timeline based on promised functionality and it fails to deliver leaving you with egg on your face in front of a client, this to me is a blocking issue.
It seems crazy that Microsoft fails to support a product (MOSS 2007) that begs to be installed on a 64bit platform due to its immense complexity and size. People are being coaxed into moving to 64 bit platforms yet when they do, they get smacked down, hard.
* Visual Studio 2005 extensions for SharePoint - Not supported on 64bit.
* Visual Studio 2008 vsto extensions for SharePoint - Not supported on 64bit.
MOSS is your FLAGSHIP PRODUCT. Visual Studio is your FLAGSHIP DEVELOPMENT ENVIRONMENT. Win64 is the FUTURE. The least you can do is have them all work together. We really don't care if your WORDs became DWORDs, or if IntPtrs cease to point to where they should. This is supposed to MANAGED code.