s afxcmn.h installed ANYWHERE in the install tree for VS? Note that the target
directories are quite different in .NET, so if your project had hardwired searches to the
VS6 directory paths, they will no longer work, and you need to make sure you have the
appropriate search paths for VS.NET 2005 set up.
MFC is still supported; I never know why these questions keep coming up.
Actually 0x0500 is more useful than 0x400. This describes the platform, and it means that
you will have Win2K APIs available to you, should you need them. It is unrelated to your
include failure, however.
You cannot use any of the VS6 libraries or source code; the new wizards make assumptions
about what MFC does and does not support.
Actually, the world would be vastly improved if we could use the new MFC with the old VS6
IDE, which was a usable IDE.
If you can't find afxcmn.h anywhere, try a reinstall and make sure you have selected all
the correct install options.
A search starting at the root of the VS.NET 2005 directory for afxcmn.h should be done.
Don't assume it is in the same place it was in the VS6 install tree.
On Wed, 16 Mar 2005 04:59:16 -0800, "Gerd.Keller" < XXXX@XXXXX.COM > wrote:
Joseph M. Newcomer [MVP]
MVP Tips: http://www.flounder.com/mvp_tips.htm