Quote Originally Posted by Marc G View Post
Maybe you have build a 64 bit version of your application and Windows 2000 cannot run 64 bit executables. Build it as 32 bit and try again.
No, it's not. Besides double-checking in the project properties I also ran the code on a 32-bit Windows XP platform and it ran just fine.

Quote Originally Posted by S_M_A View Post
Could this be related (4. Target Name)? http://qualapps.blogspot.com/2009/10...as-with-c.html
I especially like this part:
VS2010 introduces a new "Target Name" property in the General page of Configuration Properties. I still haven't figured out the rationale...
I haven't either.... It took me about 3 hours to make one of my previous projects compile on VS 2010.

OK, so I made an experiment. I compiled a simple Hello World console application using MS VS 2010.

1. First, without MFC or ATL. Just the following line:
Code:
_tprintf(_T("Hello world!\n"));
The size of the Release Unicode x86 build was around 6K. OK. I can live with that. But, if I run that code on Windows 2000 it simply shows the error "<Executable file path> is not a valid win32 application."

2. Then if I do pretty much the same, Win32 console app with MFC and use the following lines:
Code:
CString s;
s.Format(_T("Hello world!\n"));
_tprintf(s);
The size of the Release Unicode x86 build (with statically linked MFC libraries) mushrooms to, get ready for this, 1.54MB!!! Just for those 3 lines of code and a sh*t ton of MFC stuff that will never be used in this project. And obviously it doesn't run on Win2K either.


All that is BAD!