Download AppWizard project source code: Http://www.vckbase.com/vckbase/vckbase11/src/VckbaseWiz.zip
Download the project source code created with custom AppWizard: Http://www.vckbase.com/vckbase/vckbase11/src/vckproj.zip
Part III customization of a high-level AppWizard
Download AppWizard Project source code
Download the project source code created with custom AppWizard
Add a custom dialog box
To create your own template file
modifying Newproj.inf files
Modify the AppWizard template
Modify a template resource definition file
modifying template resource Files
Modify a document/view source file Template and dialog box template file
modifying Confirm.inf files
Store macros in the registry
Introducing registry operations in CCustomAppWiz derived classes
The AppWizard example we demonstrated in part two is very simple and does not have any practicality. In this section we will discuss a few high-level topics on the production of AppWizard. Then use the custom AppWizard provided by VC to create a very practical AppWizard in programming. The applications created with this custom AppWizard have two customization features compared to the regular applications generated by the MFC AppWizard (EXE):
One is that all programs will have a custom "about" dialog box that displays information about yourself or the company in this dialog box, and a static text control or image (icon and BMP) that directs users to a Web site.
The second is that every source code file (*.h and *.cpp) in the project has the first name and program creation date, as well as a simple program description and comment.
The main techniques to be introduced in this section include:
1, how to define and add AppWizard to use the Stepping dialog box.
2. How to add a private macro for custom AppWizard to the dictionary.
3, how to modify the custom AppWizard to use the template files, including INF files, resource template files and so on.
4, the input information stored in the registry, so that the public information for each project does not have to repeat the input.
Here we go: Enter the Visual C + + development environment, as shown in Figure one:
Figure I