By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,876 Members | 1,239 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,876 IT Pros & Developers. It's quick & easy.

Compile for x64 - Difference?

P: n/a
I ran an executable written in C# and compiled for 'any CPU' on Windows
XP x64 edition. It didn't run as a 32bit application. (You know, if it
did, there's a *32 suffix at the Task manager". The file also ran on
32bit Windows XP.

A few minuits ago, I compiled it for 'x64' and it didn't run on 32bit
Windows XP. If an excutable compiled for any CPU can run as a 64bit
applicaton, why should I compile it for 'x64'? Is there any difference?

Feb 24 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a

"Sin Jeong-hun" <ty*******@gmail.com> wrote in message
news:11**********************@p10g2000cwp.googlegr oups.com...
I ran an executable written in C# and compiled for 'any CPU' on Windows
XP x64 edition. It didn't run as a 32bit application. (You know, if it
did, there's a *32 suffix at the Task manager". The file also ran on
32bit Windows XP.

A few minuits ago, I compiled it for 'x64' and it didn't run on 32bit
Windows XP. If an excutable compiled for any CPU can run as a 64bit
applicaton, why should I compile it for 'x64'? Is there any difference?


AFIAK it has something todo when you are not using only managed code...
for example using native 64 bit DLL's etc.
normally you would use 'any CPU'

Best Regards,

Jeroen Vandezande

Feb 24 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.