================================================================================ MICROSOFT FOUNDATION CLASS LIBRARY : MFC Application Project Overview =============================================================================== The application wizard has created this MFC Application application for you. This application not only demonstrates the basics of using the Microsoft Foundation Classes but is also a starting point for writing your application. This file contains a summary of what you will find in each of the files that make up your MFC Application application. MFC Application.vcproj This is the main project file for VC++ projects generated using an application wizard. It contains information about the version of Visual C++ that generated the file, and information about the platforms, configurations, and project features selected with the application wizard. MFC Application.h This is the main header file for the application. It includes other project specific headers (including Resource.h) and declares the CMFCApplicationApp application class. MFC Application.cpp This is the main application source file that contains the application class CMFCApplicationApp. MFC Application.rc This is a listing of all of the Microsoft Windows resources that the program uses. It includes the icons, bitmaps, and cursors that are stored in the RES subdirectory. This file can be directly edited in Microsoft Visual C++. Your project resources are in 1033. res\MFCApplication.ico This is an icon file, which is used as the application's icon. This icon is included by the main resource file MFC Application.rc. res\MFCApplication.rc2 This file contains resources that are not edited by Microsoft Visual C++. You should place all resources not editable by the resource editor in this file. MFC Application.reg This is an example .reg file that shows you the kind of registration settings the framework will set for you. You can use this as a .reg file to go along with your application or just delete it and rely on the default RegisterShellFileTypes registration. ///////////////////////////////////////////////////////////////////////////// For the main frame window: The project includes a standard MFC interface. MainFrm.hpp, MainFrm.cpp These files contain the frame class CMainFrame, which is derived from CFrameWnd and controls all SDI frame features. res\Toolbar.bmp This bitmap file is used to create tiled images for the toolbar. The initial toolbar and status bar are constructed in the CMainFrame class. Edit this toolbar bitmap using the resource editor, and update the IDR_MAINFRAME TOOLBAR array in MFC Application.rc to add toolbar buttons. res\IToolbar.bmp This bitmap file is used to create tiled images for the toolbar when your server application is in-place activated inside another container. This toolbar is constructed in the CInPlaceFrame class. This bitmap is similar to the bitmap in res\Toolbar.bmp except that it has many nonserver commands removed. ///////////////////////////////////////////////////////////////////////////// The application wizard creates one document type and one view: MFC ApplicationDoc.hpp, MFC ApplicationDoc.cpp - the document These files contain your CMFCApplicationDoc class. Edit these files to add your special document data and to implement file saving and loading (via CMFCApplicationDoc::Serialize). The Document will have the following strings: File extension: testproject File type ID: MFCApplication.Document Main frame caption: MFC Application Doc type name: MFCApplication Filter name: MFC Application Files (*.testproject) File new short name: MFC Application File type long name: MFC Application.Document MFC ApplicationView.hpp, MFC ApplicationView.cpp - the view of the document These files contain your CMFCApplicationView class. CMFCApplicationView objects are used to view CMFCApplicationDoc objects. ///////////////////////////////////////////////////////////////////////////// The application wizard has also created classes specific to OLE CntrItem.hpp, CntrItem.cpp These files contain your CMFCApplicationCntrItem class. This class is used to manipulate OLE objects. OLE objects are usually displayed by your CMFCApplicationView class and serialized as part of your CMFCApplicationDoc class. SrvrItem.hpp, SrvrItem.cpp These files contain your CMFCApplicationSrvrItem. This class is used to connect your CMFCApplicationDoc class to the OLE system, and optionally provide links to your document. IpFrame.hpp, IpFrame.cpp These files contain your CInPlaceFrame. This class is derived from COleIPFrameWnd and controls all frame features during in-place activation. The project has support for Compound files. The Compound-file format stores a document that contains one or more Automation objects to one file and still allows access to the it for the individual objects. ///////////////////////////////////////////////////////////////////////////// Other Features: ActiveX Controls The application includes support to use ActiveX controls. Printing and Print Preview support The application wizard has generated code to handle the print, print setup, and print preview commands by calling member functions in the CView class from the MFC library. Database support The application wizard has added the basic level of database support for your program. Only the needed files have been included. ///////////////////////////////////////////////////////////////////////////// Other standard files: StdAfx.h, StdAfx.cpp These files are used to build a precompiled header (PCH) file named MFC Application.pch and a precompiled types file named StdAfx.obj. Resource.h This is the standard header file, which defines new resource IDs. Microsoft Visual C++ reads and updates this file. MFC Application.manifest Application manifest files are used by Windows XP to describe an applications dependency on specific versions of Side-by-Side assemblies. The loader uses this information to load the appropriate assembly from the assembly cache or private from the application. The Application manifest maybe included for redistribution as an external .manifest file that is installed in the same folder as the application executable or it may be included in the executable in the form of a resource. ///////////////////////////////////////////////////////////////////////////// Other notes: The application wizard uses "TODO:" to indicate parts of the source code you should add to or customize. If your application uses MFC in a shared DLL, and your application is in a language other than the operating system's current language, you will need to copy the corresponding localized resources MFC70XXX.DLL from the Microsoft Visual C++ CD-ROM under the Win\System directory to your computer's system or system32 directory, and rename it to be MFCLOC.DLL. ("XXX" stands for the language abbreviation. For example, MFC70DEU.DLL contains resources translated to German.) If you don't do this, some of the UI elements of your application will remain in the language of the operating system. /////////////////////////////////////////////////////////////////////////////