MFC Dropped Classes
Hello,
I am trying to compile my MFC application (created in eVC3) with Visual Studio 2005 (Beta 2) for Pocket PC 2003. But in MFC 8.0 some classes I have used are dropped (like CCeDBDatabase or CRecentFileList) and some classes have different methods available for the Pocket PC development.
How I am supposed to replace methods like CWinApp::LoadStdProfileSettings or CWinApp::WriteProfileString? How should I handle context sensitive help? Up to now I used ON_WM_HELPINFO but now all methods regarding the help system are removed.
What should I do?
Regards, Jutta
[579 byte] By [
jmk] at [2008-1-25]
MFC for Windows CE 2.11 devices with 8-16 mb of memory and no flash cards supported those classes easily.
You should not call your new MFC - "MFC", rename it then do M-Degraded-FC or M-NON-PORTABLE-FC :)
Believe it or not, we have 40 MB of C++ code which compiles in VC 7.1 and 8.0 with only several conditional defines.
It's funny, but I even was arguing yesterday with people in forums saying that MFC is legacy and should not be used in development. I was saying that MFC is very portable (meaning that I can use it for both Windows CE and Desktop without any modifications).
But today I downloaded your EVC Upgare Wizard and was terrified by the amount of compilation errors.
This is nonsense. MFC is working code. Having a vast body of working code is what lets you complete projects on time and under budget. Going to the trouble of carefully conditionally compiling out useful functionality is the height of stupidity.
If "size and schedule" explains MFC changes, why are there significant changes to the debug version of the MFC dll? what "size" does that affect? the amount of space used on the DVD? Are you kidding me?
Face it: Windows Mobile 5 and Visual Studio 2005 is a disaster of Palm OS proportions. Rumors of MS losing all its talent are being proven true with every error message being generated by my existing Pocket PC apps, which compile flawlessly under eVC3 and eVC4 (and Visual Studio before that).
Craig
I agree entirely, I won’t mind so much if this was the last time. But I have my suspicions Microsoft will be modifying the entire code base again, causing more annoying migration issues. I wish they would just come up with a standard and only upgrade on it i.e. make it backwards compatible, like win32.
