Is .NET 2.0 Framework going to take advantage of 64-bit computing?

  • Thread starter Thread starter int
  • Start date Start date
I

int

Is .NET 2.0 Framework going to take advantage of 64-bit computing?

Intel and especially AMD's Opteron are 64-bit and they are really
inexpensive.

Look at the prices here...
http://www.anandtech.com/guides/priceguide.html

By the time .NET 2.0 comes out, maybe middle to late 2005 at the earliest,
64-bit computing will be mainstream and will be bulk of all processors
shipping.

And what about SQL Server 64-bit? and how will MySql 64-bit affect this
entire landscape?
 
yes .net 2.0 will have x64, and IA64 support covering both intel and AMD
with both extended 64 and native 64 (AMD of which does not make a native
64bit chip, just an extended one, where as the itanium of course is a fully
64bit chip)
 
SQL Server 64-bit is already out for the Intel processors. I'm not sure if
it will ever be available in SQL 2000 for the Opteron processor; however,
Yukon will definitely support the Opteron processor, eventually. Windows
server 2003 will offer support for the Opteron with the release of service
pack 1 (2nd half of this year.) You can download a public beta from
Microsoft. I'm not sure about the framework. You can get more information
here:

http://www.microsoft.com/windowsserver2003/64bit/default.mspx

John Oakes
 
Yes, even your .NET code should be able to support 64 bit platforms without
you even needing to recompile your code.
 
anyone have an ideas on the percentage (% )performance increase for .NET
apps,
like how many more ASP.NET pages can be served?
 
Nope. Too early to tell as the code isn't even stable yet.
But anyone who has run tests isn't allowed to post statistics due to the NDA
(non-disclosure agreement).
Just sit tight and wait for MS to publish something official :-)

-Rob Teixeira [MVP]
 
Hi Steve,
Yes, even your .NET code should be able to support 64 bit platforms without
you even needing to recompile your code.

Even when there are API's in it?

Cor
 
Yes. The Framework install of the CLR will be the telling point. You will
not have to alter any code to take advantage. At least that is the "rumor"
running around. Of course, anything can change between now and then.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************
 
Hi Herfried,

I wrote this to show that it is better to use as less API's as needed.

Cor
 
* "Cor Ligthert said:
I wrote this to show that it is better to use as less API's as needed.

If possible, I avoud to use p/invoke, but I do not want to reduce user
experience, so sometimes p/invoke is necessary. As far as I see .NET
2.0 makes a lot of p/invoke samples "obsolete".
 
Back
Top