1

Closed

Problem when using MFC objects within the Test DLL project

description

It seems to be an #include hell order, which does not allow to compile a test project that consumes MFC classes from another project, whether it is linked to MFC dynamically or statically. There is a problem with #include <windows.h>, it needs further research.
Closed Oct 19, 2009 at 4:31 AM by Jhualpa
This issue rises if you create your WinUnit project using an MFC empty DLL with precompiled headers. If WinUnit projects follow the project template described on the homepage the include hell problem goes away. So always create WinUnit projects starting from a C++ empty project.

comments

Jhualpa wrote Oct 19, 2009 at 4:30 AM

This issue rises if you create your WinUnit project using an MFC empty DLL with precompiled headers. If WinUnit projects follow the project template described on the homepage the include hell problem goes away. So always create WinUnit projects starting from a C++ empty project.

wrote Oct 19, 2009 at 4:31 AM

wrote Feb 14, 2013 at 6:21 PM

wrote May 16, 2013 at 8:27 AM