afxComCtlWrapper undeclared identifier

[Ian Harding]

I am investigating the upgrade of a VC++ 6 project to build in VS 2005.

There is a compiler error in one of the MFC files - afxcomctl32.inl.
The message is: error C2065: 'afxComCtlWrapper' : undeclared identifier.

The odd thing is that if I hover over afxComCtlWrapper in the source
code, the intellisense shows that it is declared and right-click "Go to
Declaration" takes me to line 25 of afxwin.h which contains

#define afxComCtlWrapper
static_cast<CComCtlWrapper*>(AfxGetModuleState()->m_pDllIsolationWrappers[_AFX_COMCTL32_ISOLATION_WRAPPER_INDEX])

I'm confused. How can the IDE find the declaration but suffer amnesia
when it comes to build the project?

My best guess is that a project setting or something in one of our
header files somewhere is somehow undefining the symbol. Some of the
source was written over 10 years ago and uses a mixture of MFC, ATL, STL
contributed by a lot of different people so it wouldn't be the first
time we've found something strange which might have made sense at the
time but caused problems down the line.

I can't find anything useful on Google groups or web search, can anyone
offer any suggestions as to what to try next?

Thanks,
Ian

[Bruno van Dooren]

Is it possible for you to post a code snippet that reproduces this behaviour
so that we can see what happens exactly?

without that, my only guess is that VC_EXTRA_LEAN or WIN32_LEAN_AND_MEAN is
defined, which excluded some stuff from the header files.

kind regards,
Bruno.

"Ian Harding" wrote:

I am investigating the upgrade of a VC++ 6 project to build in VS 2005.

There is a compiler error in one of the MFC files - afxcomctl32.inl.
The message is: error C2065: 'afxComCtlWrapper' : undeclared identifier.

The odd thing is that if I hover over afxComCtlWrapper in the source
code, the intellisense shows that it is declared and right-click "Go to
Declaration" takes me to line 25 of afxwin.h which contains

#define afxComCtlWrapper
static_cast<CComCtlWrapper*>(AfxGetModuleState()->m_pDllIsolationWrappers[_AFX_COMCTL32_ISOLATION_WRAPPER_INDEX])

I'm confused. How can the IDE find the declaration but suffer amnesia
when it comes to build the project?

My best guess is that a project setting or something in one of our
header files somewhere is somehow undefining the symbol. Some of the
source was written over 10 years ago and uses a mixture of MFC, ATL, STL
contributed by a lot of different people so it wouldn't be the first
time we've found something strange which might have made sense at the
time but caused problems down the line.

I can't find anything useful on Google groups or web search, can anyone
offer any suggestions as to what to try next?

Thanks,
Ian

[Ian Harding]

Bruno van Dooren wrote:

Is it possible for you to post a code snippet that reproduces this behaviour
so that we can see what happens exactly?

without that, my only guess is that VC_EXTRA_LEAN or WIN32_LEAN_AND_MEAN is
defined, which excluded some stuff from the header files.

kind regards,
Bruno.

Got it! stdafx.h contained this:

#define _AFX_NO_DAO_SUPPORT
#define _AFX_NO_AFXCMN_SUPPORT

#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 OLE automation classes
#endif // _AFX_NO_OLE_SUPPORT

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

#ifndef _AFX_NO_DAO_SUPPORT
#include <afxdao.h> // MFC DAO database classes
#endif // _AFX_NO_DAO_SUPPORT

#ifndef _AFX_NO_AFXCMN_SUPPORT
#include <afxcmn.h> // MFC support for Windows 95 Common Controls
#endif // _AFX_NO_AFXCMN_SUPPORT

When I commented out #define _AFX_NO_AFXCMN_SUPPORT the errors disappeared.

Ian

[Ted]

I highly recommend you also get rid of _AFX_NO_DAO_SUPPORT as this will
cause serious crashes in your program (causing a structure member in
afxstat_.h to be left out, thereby causing the structure members after it to
be in the wrong position) More info here (on the last page of the thread)

http://forums.microsoft.com/MSDN/Sho...68836&SiteID=1

Ted.

"Ian Harding" <ih*********@hotmail.com> wrote in message
news:42*************@individual.net...

Bruno van Dooren wrote:

Is it possible for you to post a code snippet that reproduces this
behaviour so that we can see what happens exactly?

without that, my only guess is that VC_EXTRA_LEAN or WIN32_LEAN_AND_MEAN
is defined, which excluded some stuff from the header files.

kind regards,
Bruno.

Got it! stdafx.h contained this:

#define _AFX_NO_DAO_SUPPORT
#define _AFX_NO_AFXCMN_SUPPORT

#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 OLE automation classes
#endif // _AFX_NO_OLE_SUPPORT

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

#ifndef _AFX_NO_DAO_SUPPORT
#include <afxdao.h> // MFC DAO database classes
#endif // _AFX_NO_DAO_SUPPORT

#ifndef _AFX_NO_AFXCMN_SUPPORT
#include <afxcmn.h> // MFC support for Windows 95 Common Controls
#endif // _AFX_NO_AFXCMN_SUPPORT

When I commented out #define _AFX_NO_AFXCMN_SUPPORT the errors
disappeared.

Ian

[Ian Harding]

Thanks Ted, I'm going to check the other projects as well.

Ian

Ted wrote:

I highly recommend you also get rid of _AFX_NO_DAO_SUPPORT as this will
cause serious crashes in your program (causing a structure member in
afxstat_.h to be left out, thereby causing the structure members after it to
be in the wrong position) More info here (on the last page of the thread)

http://forums.microsoft.com/MSDN/Sho...68836&SiteID=1

Ted.