Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

64 bit FARM and Workflow

  Asked By: Sonya    Date: Sep 09    Category: Sharepoint    Views: 10479

we have a 64 bit farm. We built it that way per recommendations from
MS. Now we want to do some workflow via Visual Studio 2008. The out of the box
work flows are limited. Designer is nice, but the loosely coupled pieces of a
complex workflow are difficult to troubleshoot and maintain in my opinion. Not
to mention that it is difficult to re-use code from SPD. So, again on a
recommendation from MS we looked into using VS2008.

That's all great until we discovered that the workflow projects are 32 bit only
-
connect.microsoft.com/.../ViewFeedback.aspx\
407711

So is anyone doing any complex work flow in a 64bit environment? If so, how are
you getting around the 32 bit limitations?

Share: 

 

6 Answers Found

 
Answer #1    Answered By: Rosanna Parrish     Answered On: Sep 09

Workflows work just fine in x64. It's the project wizard for Visual Studio 2008
that is broken. My current workaround is to create the workflow  project in a
copy of Visual Studio 2005 and then upgrade the project to VS 2008. Once
upgraded the workflow will work just fine in VS 2008 x64. I've complained that
this is a bug, but MS seems to have no intention to fix it. So you will need to
workaround it by either developing in a 32 bit  copy of VS 2008 or starting your
project elsewhere and upgrading it.

 
Answer #2    Answered By: Kalash Karmakar     Answered On: Sep 09

Can you expand a bit  on creating the project in VS2005? Just the
simple, new project, then upgrade? Have you run into any limitations this way?

That almost seems too simple of a work around

The other option - developing in 32 bit - have you run into any issues deploying
those packages to a 64 bit farm?

I would definitely agree it is a bug. MS is pushing the 64 bit
(understandably). They are also pushing WSS/MOSS as their new development
platform with VS. But with pieces being mutually exclusive ...

 
Answer #3    Answered By: Mauricio Tanner     Answered On: Sep 09

The problem isn't in the workflow  itself in VS 2008. It's in the automation
that they have built  into the Project wizard. So if you build a SharePoint
workflow in a copy of VS 2005 and then upgrade it by opening it in VS 2008 the
project will work fine. You won't have the F5 capability and automatic WSP
creation that they've added to VS 2008, but the workflow will work fine and you
can still use the batch file system created by VS 2005 to do your testing
deployment. I've done this several times and the only limitations are the
automatic deployment ones I mentioned above. The resulting workflows work
normally.

 
Answer #4    Answered By: Gina Freeman     Answered On: Sep 09

Has anyone tried creating the project in 32-bit VS2008 and then opening it
in 64-bit VS2008?

 
Answer #5    Answered By: Tyrell Nash     Answered On: Sep 09

MSDN Article:
msdn.microsoft.com/en-us/library/cd7a85k9.aspx

Intel Article:
software.intel.com/.../generating-64-bit-binary-executables-us\
ing-microsoft-visual-studio-net/

There is a blog about known issue about x64 workflows:
http://pointstoshare.spaces.live.com/blog/cns!AEC42F315B4528B0!3018.entry

 
Answer #6    Answered By: Silvia Wilkinson     Answered On: Sep 09

The last blog is excellent and I hadn't stumbled across it in my
google/bing searches.

 
Didn't find what you were looking for? Find more on 64 bit FARM and Workflow Or get search suggestion and latest updates.




Tagged: