Application Type, MFC Application Wizard
Use this page of the MFC Application Wizard to design and add basic features to a new MFC project.
- Application type
Indicate the type of document support you want to create in your application. The type of application you select determines the user interface options available for your application. See User Interface Features, MFC Application Wizard for more information.
For more information about the types of documents, see:
Creates a single document interface (SDI) architecture for your application, with a view class based on CView. You can change the base class for the view in the Generated Classes page of the wizard. To create a form-based application, for example, you could use CFormView for the view class.
In this type of application, the document's frame window can hold only one document in the frame.
Creates a multiple document interface (MDI) architecture for your application, with a view class based on CView. You can change the base class for the view in the Generated Classes page of the wizard. To create a form-based application, for example, you could use CFormView for the view class.
In this type of application, the document's frame window can hold multiple child windows in the frame.
Creates a dialog-based architecture for your application, with a dialog class based on CDialog. (To create an HTML dialog, select the box Use HTML dialog.)
Multiple top-level documents
Creates a multiple top-level architecture for your application, with a view class based on CView.
In this type of application, when a user clicks New (or New Frame) on the File menu, the application creates a window whose parent is implicitly the desktop. The new document frame appears in the taskbar and is not restricted to the application window's client area.
- Project style
Indicates whether your application has a Windows Explorer architecture and display or a standard MFC architecture and display. See Creating a Windows Explorer-Style MFC Application for more information.
- Use of MFC
Indicates how to link to the MFC library. By default, MFC is linked as a shared DLL.
Use MFC in a shared DLL
Links the MFC library to your application as a shared DLL. Your application makes calls to the MFC library at run time. This option reduces the disk and memory requirements of your application if it is composed of multiple executable files that use the MFC library. Both Win32 and MFC applications can call functions in your DLL.
Use MFC in a static library
Links your application to the static MFC library at build time.
- Document/view architecture support
Includes document/view architecture in your application using the CDocument and CView base classes (default). Clear this check box if you are porting a non-MFC application, for example, or if you want reduce the size of your compiled executable. An application without document/view architecture is derived from CWinApp by default, and it does not include MFC support for opening a document from a disk file.
- Use HTML dialog
For dialog box applications only. Derives the dialog class from CDHtmlDialog instead of CDialog. If you check this box, CDHtmlDialog is listed in the Base class box in the Generated Classes page of the wizard.
A CDHtmlDialog-derived dialog box displays HTML-based dialog boxes and does data exchange with HTML controls and handles HTML events.
- Resource language
Sets the language to use for your resources. The list displays the languages available on your system, as installed by Visual Studio. If you want to select a language other than your system language, then the appropriate template folder for that language must already be installed. For more information on installing language resources different from the defaults available in the Resource language list, see Wizard Support for Other Languages.
The language you select is reflected in the Localized strings option of the Document Template Strings page of the wizard.