Compiling WF assemblies with /platform:x64

[PReichert]

Hello,

I have a service application that uses Windows Workflow Foundation as part
of its processes. One of the class libraries in this application is a
collection of custom WF activities that I have written to represent the bits
of business process.

The solution compiles fine when compiling with the /platform:anycpu flag and
all is good, but when I try to compile the same solution with the
/platform:x64 the class library with the WF activities fail with a "error
348: Compilation failed." It goes on to say "Unable to load one or more of
the requested types." but that's all the help I get.

I'm trying to build the application in a 32 bits machine running Windows XP
SP2, but I will run it in a Windows Server 2003 64 bits.

On the destination machine I have installed the 64 bit version of the
Framework 3.5 and when looking in "C:\WINDOWS\Microsoft.NET\Framework64\v3.0"
I can see only two sub-folders: "Windows Communication Foundation" and "WPF",
whereas in the 32 bit version of the Framework 3.0 I can see a third folder
called "Windows Workflow Foundation". Does it have any relevance?

Any help is appreciated.

 

[Steven Cheng]

Hi preichert,

As for the WWF involved project, are you developing it through VS 2008 or
VS 20005 extension? Based on my local environment, if you have VS 2008
installed, the necessary component to build .NET 3.0 projects for X64
platform should be available. For target deployment machine, you can
manually install .NET 3.0 X64 redist package if you're not sure whether it
has been installed:

#.NET 3 X64 Redist Package
http://www.microsoft.com/downloads/details.aspx?familyid=10cc340b-f857-4a14-
83f5-25634c3bf043&displaylang=en

Also , for the WWF activity project, will it report the same error if you
try build a simple solution which just contains a WWF project(and set
platform to X64)?

BTW, generally, for .NET application, start from 2.0, you can build them as
"Any CPU" so that it will automatically fit the target OS (on X64 box, it
will run onto .NET framework x64).

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we

can improve the support we provide to you. Please feel free to let my
manager know what you think of

the level of service provided. You can send feedback directly to my manager
at: (e-mail address removed).

==================================================
Get notification to my posts through email? Please refer to

http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response

from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take

approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution.

The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump

analysis issues. Issues of this nature are best handled working with a
dedicated Microsoft Support

Engineer by contacting Microsoft Customer Support Services (CSS) at

http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[PReichert]

Hello Steven,

Thanks for the reply. Sorry I didn't make it clear, but I'm using Visual
Studio 2008. As for the target deployment machine, as I have mentioned I have
installed the Framework 3.5 64 bits and I have all that deployed, but what I
was pointing out is that while the 32 bits Framework 3.0 folders have a
folder called "Workflow Foundation", the 64 bit version doesn't have the same
folder.

I tried to build a simple sequential workflow console app in x64 and it
builds fine, so I will investigate more.

As for building in Any CPU, the project will be actually built like that,
but because my system is built up of several solutions (each one for a
different application) and I have one application in the system that will
have to be built in 32 bit exclusive (to run on WOW64) because of 32 bits
dependencies, another one will be built in 64 bits exclusive because of 64
bits dependencies and the rest can be built for any CPU, then I was testing
the various configurations in all solutions.

Regards,
Paulo

 

[Steven Cheng]

Thanks for your Paulo,

So your target system have all the things installed, I've checked a local
win2k3 x64 box, there does exists difference between the 32 bit and x64's
net framework 3.0 folder. For the compile error, I think there might be
something else that cause it. You can even try create a new solution with
new project and move your original solution and project items into the new
one to see whether the problem is due to some configuration settings of
project file get corrupted.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
(e-mail address removed).
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------