The MFC AppWizard (EXE version): Step-by-Step

  • Article

|  Overview |  How Do I |  Details | 

The MFC AppWizard series is a branching path of either 4 or 6 steps depending on the architecture you select for your program. You can move forward and backward through the steps and make changes to the options you have selected.

Help is available for every option in each step: right-click on the control for more information about each option.

To complete Step 1

  1. Choose one of three architectures for your program: Single Document (SDI), Multiple Document (MDI), or Dialog Based.

  2. Decide if you want your application to support MFC's document/view architecture. An application without document/view architecture would not have MFC support to open a document from a disk file and the window area is derived from CWnd. See Alternatives to the Document/View Architecture.

    If you choose not to use document/view architecture, other options in Steps 2-5 will not be available.

  3. Select a language for the resource text and then click Next.

  4. If you selected a dialog-based architecture, click here for Step 2.

To complete Step 2 for an SDI or MDI type program

  1. Choose one of four database support options for your program: None, Header file support, Database View (with file support) or Database View (without file support).

  2. If you selected database view support, click Data Source and choose either an external ODBC database, DAO database or OLE DB database and the appropriate data source and Database Table options.

    For more information, see Data Source (ODBC), DAO External: Working with External Data Sources,

  3. Click Next.

To complete Step 3 for an SDI or MDI type program

Choose the compound document support you would like to include in your program:

Container

An OLE 2.0-style document container.

Mini-server

An OLE server that cannot run as a standalone program.

Full-server

An OLE server that can also run as a standalone program.

Active Document Servers

Active Document Containers

Also, select options to enable the standard ActiveX resources and to add extra Automation commands to the application's menu bar.

To complete Step 4 for an SDI or MDI type program

  1. Choose which basic user-interface features you want your program to have and the type of toolbars to use: IE4.0 ReBars or MFC (command) toolbars. See Windows Sockets in MFC and MAPI Support in MFC for more information.

  2. If you want to modify the filenames and extensions that your program uses or want to adjust the user interface window frame styles for your program, click Advanced.

  3. Click Next.

To complete Step 5 for an SDI or MDI type program

  1. Choose the project style: Explorer, which gives you a tree view on the left and a list view on the right or MFC Standard, which gives you one area for a file view.

  2. Choose whether or not you would like AppWizard to generate comments in the source file that will guide you in writing your program.

  3. Choose whether you would like to use the MFC library as a shared or statically linked DLL.

Feature Only in Professional and Enterprise Editions   Static linking to MFC is supported only in Visual C++ Professional and Enterprise Editions. For more information, see .

To complete Step 6 for an SDI or MDI type program

  1. If you want to change the default class name, base class, header or implementation file names provided by AppWizard, enter the new names. To change the Base class, select your program's view class (see Derived View Classes).

  2. Click Finish and then click here to prepare your MFC program for use.

To complete Step 2 for a dialog-based program

  1. Choose which basic user-interface features you want your program to have and what WOSA support to include. See Windows Sockets in MFC for more information.

  2. Click Next.

To complete Step 3 for a dialog-based program

  1. Choose Yes, if you would like comments about where you need to add your own code into the source file.

  2. Choose whether you would like to use the MFC library as a shared or statically linked DLL.

Feature Only in Professional and Enterprise Editions   Static linking to MFC is supported only in Visual C++ Professional and Enterprise Editions. For more information, see .

To complete Step 4 for a dialog-based program

  1. If you want to change the default class name, header or implementation file names provided by AppWizard, enter the new names. To change the Header or Implementation file name, select your program's dialog class.

  2. Click Finish and then click here to prepare your MFC program for use.