Can .NET/C# build 64-bit app?

[Polaris]

Hi:

On a 64-bit platform with Windows 2003, can .NET Visual C# build a 64-bit
application? Or is there a 64-bit version of Visual .NET available for this
purpose?

Thanks

 

[Pieter Philippaerts]

On a 64-bit platform with Windows 2003, can .NET Visual C# build a 64-bit
application? Or is there a 64-bit version of Visual .NET available for this
purpose?

If I'm not mistaken, the next version of the .NET framework will have 64-bit
support.
I don't think it's possible to build 64-bit .NET applications with the
current versions of the framework.

Regards,
Pieter Philippaerts
Managed SSL/TLS: http://www.mentalis.org/go.php?sl

 

[Jon Skeet [C# MVP]]

I don't think it's possible to build 64-bit .NET applications with the
current versions of the framework.

I think that depends on how you look at it - arguably we're *already*
building 64-bit .NET applications, they just don't have anywhere to run
yet

Assuming the 64-bit CLR is backwardly compatible, (nearly?) any
application we write now will run on the new CLR, and will be running
in 64-bit mode. Ah the joys of not having a virtual execution system...

 

[William Stacey]

Other then 64 bit memory addresses, what would be the benefit to c# programs
in general.

 

[Daniel O'Connell]

Other then 64 bit memory addresses, what would be the benefit to c# programs
in general.

That would depend on the processor you are running on, how good the JIT is
at optimizations, and what you are doing. You should be able to do basic
calculations on larger pieces of data at once in standard registers, etc.
On the Itanium for example, the JITer may be able to play with predication
and prediction in ways that produces significant performance increases(or it
may be hampered by it, I'm kind of curious on that myself), the JIT may be
in a better position at runtime to guess when data will be needed and be
able to generate prediction instructions for branches and speculative memory
loads. The JIT should also have access to more registers than on a standards
X86.
I don't know what kind of tricks may exist on the AA64.
In general however, considering that most things are abstracted away, it
should simply allow you to run larger programs and run on 64 bit cpus,
hopefully with close to the best performance possible for the given
processor.

 

[William Stacey]

Thanks Daniel. Unrelated, but this is strange. I see your reply to my
post, but do not see my post in this thread. I have noticed this a few
times on this ng. Anyone else seen this? Related to Swen?

--
William Stacey, DNS MVP

Other then 64 bit memory addresses, what would be the benefit to c# programs
in general.

That would depend on the processor you are running on, how good the JIT is
at optimizations, and what you are doing. You should be able to do basic
calculations on larger pieces of data at once in standard registers, etc.
On the Itanium for example, the JITer may be able to play with predication
and prediction in ways that produces significant performance increases(or it
may be hampered by it, I'm kind of curious on that myself), the JIT may be
in a better position at runtime to guess when data will be needed and be
able to generate prediction instructions for branches and speculative memory
loads. The JIT should also have access to more registers than on a standards
X86.
I don't know what kind of tricks may exist on the AA64.
In general however, considering that most things are abstracted away, it
should simply allow you to run larger programs and run on 64 bit cpus,
hopefully with close to the best performance possible for the given
processor.

 

[Daniel O'Connell]

Thanks Daniel. Unrelated, but this is strange. I see your reply to my
post, but do not see my post in this thread. I have noticed this a few
times on this ng. Anyone else seen this? Related to Swen?

Every now and then one of my posts won't show up, I never figured out why.
Its been happening for the last year...the posts seem to go through though.
I always chalked it up to a screwed up server at my ISP or OE problems.