Ce6 There is no obvious component for MFC, m$ is ready to abandon MFC

If you want to use MFC, you need to manually add MFC to the system.
1: Locate the MFC DLL in the VS2005 directory. The directory on my computer is D:/program files/microsoft Visual Studio 8/vc/ce/dll/x86.
Because the platform I use is based on CEPC, select the x86 directory.
2: Copy the MFC DLL to the%WINCE_ROOT%/OSDESIGNS/MFC directory.
Copy all DLL files under x86 to the MFC directory, which is the directory you create yourself, or it can be a different name. Not all DLL files will be used, just for the sake of convenience.
3: Set Custom Build Actions. Open the platform's property Pages, and in the tab page of the custom build pages of Configration properties, select Pre-make Image in the Build step drop-down box.
Click on the new ... button to enter the copy%_winceroot%/osdesigns/mfc/%_flatreleasedir%/in the popup dialog box.
The DOS command is entered here, and the environment variables set in Windows CE can be used in the command. The above command is to copy the DLL files in the MFC directory into the%_flatreleasedir% directory, as well, not all DLL files will be used.
4: Modify the configuration file. Add the following sentences to the Project.bib file
mfc80u. DLL $ (_flatreleasedir)/mfc80u. DLL NK SH
Mfc80ud. DLL $ (_flatreleasedir)/mfc80ud. DLL NK SH
Mfc80enu. DLL $ (_flatreleasedir)/mfc80enu. DLL NK SH
Atl80.dll $ (_flatreleasedir)/atl80.dll NK SH
Msvcr80.dll $ (_flatreleasedir)/msvcr80.dll NK SH
Msvcr80D.dll $ (_flatreleasedir)/msvcr80d.dll NK SH
If you want to use this configuration in your future operating system design, you can add it to the Platform.bib file.
Mfc80enu. DLL is an English resource file that selects different resource DLL files according to the language you are using.
The debug version of the DLL may not have to be added to the operating system image, as needed to make specific changes.
5: Build. Get support for MFC's Windows Embedded CE6.0 platform, you can see several DLL files in MFC after running in the/windows directory.
If you have created a Nk.bin file and don't want to spend another half hour creating it from scratch, you can copy the MFC DLL files you use directly to%_flatreleasedir%/.
Then modify the Project.bib file, locate the Project.bib, and copy it to%_flatreleasedir%/.
In the Build menu of VS2005, click Open Release Directory in Build window, the Command Line window opens, enter the Makeimg command, and create the Nk.bin.
This process takes only two or three minutes.

Ce6 There is no obvious component for MFC, m$ is ready to abandon MFC