Using MSTest with MFC

Question

Is there anybody using MSTest to test MFC code?

I created a managed C++ Test project and and can write unit tests within it but once I #include <afxwin.h> then I have problems. The code will compile and when it gets to running the tests, the UI hangs and none of the symbols will load. You cannot debug the tests either. If I remove the #include, then the tests will run successfully. Any ideas?

It is compiling with /clr with multithreaded debug (/mtd) and using MFC through a shared dll. If I choose to statically link to MFC, then the compiler (VSVC9.0) will tell me that /clr and /mtd are not compatible.

Also, do you think adding DependencyInput's to the tests will fix this? I've tried adding some MFC dlls as dependency inputs but it hasn't helped. I could be doing it wrong though.

Thanks.

Jean-François Côté · Accepted Answer · 2011-10-17 13:48:43Z

At work, using visual studio 2010, we successfully created a managed c++ test project to test mfc code.

We began creating a c++ test project using the wizard. Then, in the configuration properties of the unit test project, change the following :

General->Use of MFC = changed to "Use MFC in a shared DLL"
General->Common language runtime support = changed to "Common language support (/clr)
(In debug config only) Linker->Output->Ignore Specific Default Libraries = add MSVCRT

In the stdafx.h : I have the following

// Modify the following defines if you have to target a platform prior to the ones specified below.
// Refer to MSDN for the latest info on corresponding values for different platforms.
#ifndef WINVER              // Allow use of features specific to Windows XP or later.
#define WINVER 0x0501       // Change this to the appropriate value to target other versions of Windows.
#endif

#ifndef _WIN32_WINNT        // Allow use of features specific to Windows XP or later.                   
#define _WIN32_WINNT 0x0501 // Change this to the appropriate value to target other versions of Windows.
#endif                      

#ifndef _WIN32_IE           // Allow use of features specific to IE 6.0 or later.
#define _WIN32_IE 0x0600    // Change this to the appropriate value to target other versions of IE.
#endif

#include <afxwin.h>         // MFC core and standard components
#include <afxext.h>         // MFC extensions

#ifndef _AFX_NO_OLE_SUPPORT
#include <afxole.h>         // MFC OLE classes
#include <afxodlgs.h>       // MFC OLE dialog classes
#include <afxdisp.h>        // MFC Automation classes
#endif // _AFX_NO_OLE_SUPPORT

#ifndef _AFX_NO_DB_SUPPORT
#include <afxdb.h>          // MFC ODBC database classes
#endif // _AFX_NO_DB_SUPPORT

#include <afxdtctl.h>       // MFC support for Internet Explorer 4 Common Controls
#ifndef _AFX_NO_AFXCMN_SUPPORT
#include <afxcmn.h>         // MFC support for Windows Common Controls
#endif // _AFX_NO_AFXCMN_SUPPORT

And everything works like a charm! Let me know if it works for you

Preet Sangha · Accepted Answer · 2009-05-01 23:25:36Z

0

Is it the same from the command line?

Not done this. But could a static window be being created? check the msest proces with process explorer.

answered May 1, 2009 at 23:25

Preet Sangha

65.7k20 gold badges152 silver badges227 bronze badges

Collectives™ on Stack Overflow

Using MSTest with MFC

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related