1 | ================================================================================
|
---|
2 | MICROSOFT FOUNDATION CLASS LIBRARY : TestProg Project Overview
|
---|
3 | ===============================================================================
|
---|
4 |
|
---|
5 | The application wizard has created this TestProg application for
|
---|
6 | you. This application not only demonstrates the basics of using the Microsoft
|
---|
7 | Foundation Classes but is also a starting point for writing your application.
|
---|
8 |
|
---|
9 | This file contains a summary of what you will find in each of the files that
|
---|
10 | make up your TestProg application.
|
---|
11 |
|
---|
12 | TestProg.vcproj
|
---|
13 | This is the main project file for VC++ projects generated using an application wizard.
|
---|
14 | It contains information about the version of Visual C++ that generated the file, and
|
---|
15 | information about the platforms, configurations, and project features selected with the
|
---|
16 | application wizard.
|
---|
17 |
|
---|
18 | TestProg.h
|
---|
19 | This is the main header file for the application. It includes other
|
---|
20 | project specific headers (including Resource.h) and declares the
|
---|
21 | CTestProgApp application class.
|
---|
22 |
|
---|
23 | TestProg.cpp
|
---|
24 | This is the main application source file that contains the application
|
---|
25 | class CTestProgApp.
|
---|
26 |
|
---|
27 | TestProg.rc
|
---|
28 | This is a listing of all of the Microsoft Windows resources that the
|
---|
29 | program uses. It includes the icons, bitmaps, and cursors that are stored
|
---|
30 | in the RES subdirectory. This file can be directly edited in Microsoft
|
---|
31 | Visual C++. Your project resources are in 1033.
|
---|
32 |
|
---|
33 | res\TestProg.ico
|
---|
34 | This is an icon file, which is used as the application's icon. This
|
---|
35 | icon is included by the main resource file TestProg.rc.
|
---|
36 |
|
---|
37 | res\TestProg.rc2
|
---|
38 | This file contains resources that are not edited by Microsoft
|
---|
39 | Visual C++. You should place all resources not editable by
|
---|
40 | the resource editor in this file.
|
---|
41 |
|
---|
42 | TestProg.reg
|
---|
43 | This is an example .reg file that shows you the kind of registration
|
---|
44 | settings the framework will set for you. You can use this as a .reg
|
---|
45 | file to go along with your application or just delete it and rely
|
---|
46 | on the default RegisterShellFileTypes registration.
|
---|
47 |
|
---|
48 |
|
---|
49 | /////////////////////////////////////////////////////////////////////////////
|
---|
50 |
|
---|
51 | For the main frame window:
|
---|
52 | The project includes a standard MFC interface.
|
---|
53 |
|
---|
54 | MainFrm.h, MainFrm.cpp
|
---|
55 | These files contain the frame class CMainFrame, which is derived from
|
---|
56 | CMDIFrameWnd and controls all MDI frame features.
|
---|
57 |
|
---|
58 | res\Toolbar.bmp
|
---|
59 | This bitmap file is used to create tiled images for the toolbar.
|
---|
60 | The initial toolbar and status bar are constructed in the CMainFrame
|
---|
61 | class. Edit this toolbar bitmap using the resource editor, and
|
---|
62 | update the IDR_MAINFRAME TOOLBAR array in TestProg.rc to add
|
---|
63 | toolbar buttons.
|
---|
64 |
|
---|
65 | res\IToolbar.bmp
|
---|
66 | This bitmap file is used to create tiled images for the toolbar
|
---|
67 | when your server application is in-place activated inside another
|
---|
68 | container. This toolbar is constructed in the CInPlaceFrame
|
---|
69 | class. This bitmap is similar to the bitmap in res\Toolbar.bmp
|
---|
70 | except that it has many nonserver commands removed.
|
---|
71 |
|
---|
72 | /////////////////////////////////////////////////////////////////////////////
|
---|
73 |
|
---|
74 | For the child frame window:
|
---|
75 |
|
---|
76 | ChildFrm.h, ChildFrm.cpp
|
---|
77 | These files define and implement the CChildFrame class, which
|
---|
78 | supports the child windows in an MDI application.
|
---|
79 |
|
---|
80 | /////////////////////////////////////////////////////////////////////////////
|
---|
81 |
|
---|
82 | The application wizard creates one document type and one view:
|
---|
83 |
|
---|
84 | TestProgDoc.h, TestProgDoc.cpp - the document
|
---|
85 | These files contain your CTestProgDoc class. Edit these files to
|
---|
86 | add your special document data and to implement file saving and loading
|
---|
87 | (via CTestProgDoc::Serialize).
|
---|
88 |
|
---|
89 | TestProgView.h, TestProgView.cpp - the view of the document
|
---|
90 | These files contain your CTestProgView class.
|
---|
91 | CTestProgView objects are used to view CTestProgDoc objects.
|
---|
92 |
|
---|
93 | res\TestProgDoc.ico
|
---|
94 | This is an icon file, which is used as the icon for MDI child windows
|
---|
95 | for the CTestProgDoc class. This icon is included by the main
|
---|
96 | resource file TestProg.rc.
|
---|
97 |
|
---|
98 |
|
---|
99 | /////////////////////////////////////////////////////////////////////////////
|
---|
100 |
|
---|
101 | The application wizard has also created classes specific to OLE
|
---|
102 |
|
---|
103 | CntrItem.h, CntrItem.cpp
|
---|
104 | These files contain your CTestProgCntrItem class. This class is used to
|
---|
105 | manipulate OLE objects. OLE objects are usually displayed by your
|
---|
106 | CTestProgView class and serialized as part of your CTestProgDoc class.
|
---|
107 |
|
---|
108 | SrvrItem.h, SrvrItem.cpp
|
---|
109 | These files contain your CTestProgSrvrItem. This class is used to
|
---|
110 | connect your CTestProgDoc class to the OLE system, and optionally
|
---|
111 | provide links to your document.
|
---|
112 |
|
---|
113 | IpFrame.h, IpFrame.cpp
|
---|
114 | These files contain your CInPlaceFrame. This class is derived
|
---|
115 | from COleIPFrameWnd and controls all frame features during in-place activation.
|
---|
116 |
|
---|
117 | The project has support for Compound files. The Compound-file format stores a document
|
---|
118 | that contains one or more Automation objects to one file and still allows access to
|
---|
119 | the it for the individual objects.
|
---|
120 |
|
---|
121 |
|
---|
122 | /////////////////////////////////////////////////////////////////////////////
|
---|
123 |
|
---|
124 | Other Features:
|
---|
125 |
|
---|
126 | ActiveX Controls
|
---|
127 | The application includes support to use ActiveX controls.
|
---|
128 |
|
---|
129 | Printing and Print Preview support
|
---|
130 | The application wizard has generated code to handle the print, print setup, and print preview
|
---|
131 | commands by calling member functions in the CView class from the MFC library.
|
---|
132 |
|
---|
133 | /////////////////////////////////////////////////////////////////////////////
|
---|
134 |
|
---|
135 | Other standard files:
|
---|
136 |
|
---|
137 | StdAfx.h, StdAfx.cpp
|
---|
138 | These files are used to build a precompiled header (PCH) file
|
---|
139 | named TestProg.pch and a precompiled types file named StdAfx.obj.
|
---|
140 |
|
---|
141 | Resource.h
|
---|
142 | This is the standard header file, which defines new resource IDs.
|
---|
143 | Microsoft Visual C++ reads and updates this file.
|
---|
144 |
|
---|
145 | TestProg.manifest
|
---|
146 | Application manifest files are used by Windows XP to describe an applications
|
---|
147 | dependency on specific versions of Side-by-Side assemblies. The loader uses this
|
---|
148 | information to load the appropriate assembly from the assembly cache or private
|
---|
149 | from the application. The Application manifest maybe included for redistribution
|
---|
150 | as an external .manifest file that is installed in the same folder as the application
|
---|
151 | executable or it may be included in the executable in the form of a resource.
|
---|
152 | /////////////////////////////////////////////////////////////////////////////
|
---|
153 |
|
---|
154 | Other notes:
|
---|
155 |
|
---|
156 | The application wizard uses "TODO:" to indicate parts of the source code you
|
---|
157 | should add to or customize.
|
---|
158 |
|
---|
159 | If your application uses MFC in a shared DLL, you will need
|
---|
160 | to redistribute the MFC DLLs. If your application is in a language
|
---|
161 | other than the operating system's locale, you will also have to
|
---|
162 | redistribute the corresponding localized resources MFC90XXX.DLL.
|
---|
163 | For more information on both of these topics, please see the section on
|
---|
164 | redistributing Visual C++ applications in MSDN documentation.
|
---|
165 |
|
---|
166 | /////////////////////////////////////////////////////////////////////////////
|
---|