Hi,
I've just discovered this weird bug in VS2005:
when compiling and linking my application with the x64 platform target on a computer running Windows 2000, the executable can't be run on a Win64 computer. I've spent a lot of time trying to solve this pronlem, and I found the following:
- by using Depends, I found that it's the "exported symbols" table that's invalid in these files,
- it seems to be related to the Embed manifest option, because disabling it will generate valid executables and dlls,
- the problem doesn't happen if I link the file on a Win 64 computer.
So it seems that the Embedding process is not correctly done for 64 bit executables on 32 bit computers.
By searching for this problem on the internet, I found that
- some users mentionned the dirty workaround of 'simply disableing embed manifest option'
- others didn't have a reply to their problem (especially here on the MS forums).
So, now, what can I do I want to distribute my application, I've also developped my custom installer which supports the new side-by-side applications, etc. so i don't want to change everything because of this problem...
Does this problem have a known fix/patch/worakound (better than disabling the embed manifest option) Do I need to move all my autocompilation system to a Win64 computer
Thanks for your help!
Benoit
Edit: I forgot to mention the following:
- I'm using unmanaged C++ only, just regular C++.
- I'm using Visual Studio 2005 Professional on Windows 2000 Professional.
- Static linking of the CRT and MFC dlls is not a solution as I really want to use a shared linking.

64b development: Huge problem with VS2005 on a 32b OS
shailu155
Thank you very much for the prompt reply. I've just reported the bug using the address you provided. Here is the report ID: 155343
I can send you some files if you need further information like executable files, etc.
Best regards,
Big--Ben
dandrievsky
Could you please log a bug at http://connect.microsoft.com/Main/content/content.aspx ContentID=2220 Please reply back to this thread with a link to you bug. I will make sure someone look at it straight ahead.
Thanks in advance for reporting the issue!
Thanks, Ayman Shoukry VC++ Team