Steven,
..NET 2.0 (VS.NET 2005, aka Whidbey due out later in 2005) supports both a
32-bit runtime & a 64-bit runtime. NOTE: VS.NET itself remains 32-bit,
however the assemblies created can be 32-bit or 64-bit...
For details see:
http://lab.msdn.microsoft.com/vs2005/
As Cor suggests the Integer stays 32-bit which IMHO will ensure your code
runs the same, unmodified, on both the 32-bit framework & 64-bit framework,
as any attempt to change the size of Integer will cause more problems then
it will solve. In other words you can compile your program once & it will
run identically on both the 32-bit & 64-bit framework. The 64-bit framework
will simply give you access to significantly more memory. The "tricky" parts
are going to be how much P/Invoke (Declare statements) you used, as they are
platform specific... My understanding is you can take 32-bit assemblies &
run time "as is" on the 64-bit framework if you did not use any P/Invoke
statements...
In addition to the above link, the follow links lead to 64-bit specific
information.
http://communities.microsoft.com/new...y&slcid=us http://blogs.msdn.com/joshwil/ http://msdn.microsoft.com/msdntv/epi...B/manifest.xml
Plus there have been a couple of threads in this newsgroup discussing it,
the thread titled "Integer Do's And Don'ts" from October 15-18 2004 seems to
be the longest & discusses the size of Integer the greatest...
Hope this helps
Jay
"yxq" <ga***@163.net> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
| Hello,
| Which VB version can make 64-bits programs?
|
| Thank you
| Steven
|
|