09-16-2006 05:24 PM
09-18-2006 03:26 PM
09-18-2006 10:54 PM
09-19-2006 08:33 AM
09-19-2006 08:49 AM
Did you do the following, as suggested in the topic that Sam referenced?
To work around this issue call C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ldr64.exe setwow in the prebuild step of your Visual Studio 2005 project, and call C:\WINDOWS\Microsoft.NET\Framework64\v2.0.50727\ldr64.exe set64 in the postbuild step of your project.
09-19-2006 09:23 AM
09-19-2006 10:55 AM
I tried this on my 32-bit OS and was able to build without error.
01-04-2007 01:23 PM
01-05-2007 08:59 AM
We have plans to provide 64-bit support. However, we have not seen a great deal of demand for it to date. Additionally, we plan to support 64-bit Vista and not 64-bit XP. This is mainly due to the differences in driver requirements and also due to the fact that we have not seen adoption of XP x64 by many of our customers. We believe we will see greater adoption of 64-bit OSs in the future (when XP will not be readily available for new systems). Hence the decision to move forward with Vista x64.
It would be useful for us if you could provide some information about your needs.
Do you see yourself moving to Vista x64 in the future?
Which components/class libraries/drivers in particular, do you want 64-bit versions of?
Why do you want to write 64-bit applications? Does your application demand the additional memory space? If so, can you briefly describe your application?
I think I mentioned this in another thread, but we don't consider all of our unmanaged code to be legacy. There are good reasons to have some unmanaged code. The best example is the analysis library. We get huge performance improvements by relying on the Intel Math Kernel Libraries, which are by nature unmanaged.
04-22-2008 02:02 AM
Hi,
I met the same problem. Actually, I added the prebuild and post build command. But it produced an error as I ran the commands. It returned an exited code -1.
Then, I used a DOS prompt in Vista x64 and went into the folder to run the 'ldr64 setwow' directly. It is also failed.
My system is running Vista x64, Visual Studio 2005 , updated to SP1 and also installed the VS2005 upgrade for Vista. I'm running Measurement Studio 8.1.1.
Any idea on what happened?
Michael