The following posting is courtesy of Simon Massey.
> Subject: RE: Building ACE+TAO x.6.4 with MFC using VS 9.0
> Date: Thu, 15 May 2008 04:09:01 -0400
> From: "Simon Massey" <Simon.Massey@prismtech.com>
> To: "Johnny.Willemsen" <email@example.com>,
> Cc: <firstname.lastname@example.org>
> As far as I know, if you define an microsoft MFC project, i.e. an application that IS an MFC application, that MWC/MPC project should include ace_mfc as a base project, either directly or by adding -base ace_mfc to the MWC/MPC command. This tells MWC/MPC to force ACE_HAS_MFC as a define onto the compiler line, thus all source has this macro defined correctly and a microsoft MFC application results.
> If you are not using MWC/MPC to generate your project files (for example creating a new MFC project), I believe this is also how microsoft do it, adding the _AFX define (or whatever it is) to the compiler lines; therefore to include ace MFC style libraries you would also need to add ACE_HAS_MFC as well.
> Isn't this the same "configurational" problem that you were talking about yesterday?
> I'll have a quick look at the missing CACE_Init_TestDlg class, as soon as I can, but as far as I was concerned I wasn't trying to get all of the tests to be MFC applications with my mods, just building MFC compatiable libraries.