Linked by Thom Holwerda on Thu 14th Dec 2006 17:58 UTC
Thread beginning with comment 192297
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
All the 64-bit apps ARE being developed on a 64-bit machine running Win64. But even debugging locally, Visual Studio actually uses the remote debugger connected to localhost when debugging 64-bit code. This came to me straight from the mouth of Microsoft, not from a description on their web site. And it's for this reason that neither the profiler, unit test framework, nor edit-and-continue work on 64-bit apps running on a 64-bit machine being debugged "locally".




Member since:
2006-06-01
Yes there are 64 bit compilers with it but because the IDE is 32 bit, then the remote debugger must be used. Even though the debugger is 64 bit, it's the use of the remote debugger locally which prevents all the fancy whiz-bang features from being used.
I'm not sure why you would be developing x64 apps on an x86 PC.
http://msdn2.microsoft.com/en-us/library/ms184681(VS.80).aspx
"With Visual Studio 2005, you can debug a 64-bit application running on the local machine or on a remote machine.
If you are debugging locally, Visual Studio 2005 runs under WOW64, the 32-bit x86 emulator that allows 32-bit Windows applications to run on 64-bit Windows. Local debugging under WOW64 is supported on x64 only.
If you are debugging remotely, Visual Studio 2005 can run under WOW64 or on a 32-bit machine. You can debug both IA64 and x64 applications, as well as 32-bit applications running under or x64 WOW mode or on 32-bit platforms.
To debug a 64-bit application running on a remote computer, you need to install the 64-bit remote debugger on the remote computer. The 64-bit remote debugger is available on the last disc of your Visual Studio 2005 installation set."