List of eVC Classes Not Supported from MFC 3.0 to 9.0

• CDaoFieldExchange Class

• CDBVariant Class

• CFieldExchange Class

• CFontDialog Class

• CLongBinary Class

• COleCmdUI Class

• COleCurrency Class

• COleDataObject Class

• COlePropertyPage Class

• CPrintDialog Class

• CPrintInfo Members

• CSocketFile Class

• CBitmap Class

• CDialogBar Class

• CEditView Class

• CFindReplaceDialog Class

• CHttpConnection Class

• CHttpFile Class

• CInternetConnection Class

• CInternetException Class

• CInternetFile Class

• CInternetSession Class

• COleSafeArray Class

• CReBar Class

• CReBarCtrl Class

• CRecentFileList Class

• CSplitterWnd Class

The following classes are typedef that use template classes to provide equivalent functionality:

• CByteArray Class

• CDWordArray Class

• CMapPtrToPtr Class

• CMapPtrToWord Class

• CMapStringToOb Class

• CMapStringToPtr Class

• CMapStringToString Class

• CMapWordToOb Class

• CMapWordToPtr Class

• CObArray Class

• CObList Class

• COleSafeArray Class

• CPtrArray Class

• CPtrList Class

• CStringArray Class

• CStringList Class

• CUIntArray Class

• CWordArray Class

Behavioral Differences of APIs from MFC 3.0 to MFC 9.0

• The CDocument::SaveModified dialog class and associated resources have been dropped from MFC 9.0 for all platforms. Therefore, on Pocket PC 2003 and Smartphone 2003 platforms DoSave and SaveModified methods have no default file name when they are used, nor do they have a default prompt for the file name such as an auto-generated file name. However, an option is provided to override this behavior and prompt for file name on the Pocket PC 2003 platform. On the Smartphone platform, you can call CDocManager::DoPromptFileName, if you want to prompt for file name. DoSave and SaveModified methods' default-file name behavior is supported on Windows CE platform and the functionality is the same as that on the desktop.

• MFC 9.0 for devices has no docking support. For example CCommandBar::m_pDockBar and CCommandBar::m_pDockContext members are not supported. For more information, see CCommandBar Class. For more information about docking support, see Docking and Floating Toolbars.

• In MFC 9.0 for devices, CDC::FrameRect is no longer a member of CDC Class.

• In MFC 9.0 for devices, CCeDocList is renamed to CDocList Class.

• In MFC 9.0 for devices, CCeSocket functionality is encapsulated in CAsyncSocket Class.

• In MFC 9.0 for devices, CFont::CreateFont is not supported, you can use CFont::CreatePointFont instead.

• In MFC 9.0 for devices, CCommandBar::m_pDockBar and CCommandBar::m_pDockContext members are no longer supported.

• In MFC 9.0 for devices, LPINLINEIMAGEINFO structure is replaced with INLINEIMAGEINFO.

• The Visual Studio wizard-generated resources follow the Windows Mobile 5.0 User Interface (UI) guidelines. This means all applications' MenuBar classes will always have the New button on the left side and a Menu on the right side. Therefore, MFC 9.0 for devices does not support the m_bShowSharedNewButton variable. For example, if your application code is using wndCommandBar.m_bShowSharedNewButton = TRUE;, you can comment the code line out and get your application to port to MFC 9.0 for devices.

• If your application code is using ON_NOTIFY(DLN_CE_CREATE, AFXCE_ID_DOCLIST, or OnCreateDocList,you will get the following compile errors:

• MainFrm.cpp(42) : error C2065: 'DLN_CE_CREATE' : undeclared identifier

• MainFrm.cpp(42) : error C2065: 'AFXCE_ID_DOCLIST' : undeclared identifier

• In MFC 9.0, you can safely use DLN_DOCLIST_CREATE, DLN_DOCLIST_DESTROY, and AFX_ID_DOCLIST.

• When using MFC 9.0, you cannot link to the standard CRT libraries.

• When porting to MFC 9.0, include # define _WIN32_WCE_PSPC. By default, this flag is not defined in MFC 9.0.

• For more information, see List of Unsupported Desktop MFC Classes for Devices.

See Also

Concepts

Differences Between MFC C++ for Devices and Standard MFC

Other Resources

Unique MFC for Devices Classes