windows-xp/Source/XPSP1/NT/shell/tools/extwiz/readme.txt

========================================================================
                    CUSTOM APPWIZARD: Extensions
========================================================================


AppWizard has created a Extensions DLL for you.  This DLL is the starting point
for writing your custom AppWizard.  It demonstrates the basics of creating a
custom AppWizard.

Although your custom AppWizard is a DLL, it has the special suffix AWX.  When
you build Extensions.awx, it will automatically be copied to your Template
directory.  Your custom AppWizard will then appear as choice in the Project
Type drop-list in the New Workspace and Insert Project dialogs.  To run your
custom AppWizard, simply create a new workspace (or insert a project into the
current workspace), and select your custom AppWizard from the Project Type
drop-list.

This file contains a summary of what you will find in each of the files that
make up your Extensions DLL.


Extensions.mak
    This project file is compatible with the Visual C++ development
    environment.  It is also compatible with the NMAKE program provided with
    Visual C++.

    To build a debug version of the program from the MS-DOS prompt, type
    nmake /f Extensions.mak CFG="Win32 Debug".

    To build a release version of the program, type
    nmake /f Extensions.mak CFG="Win32 Release".

Extensions.cpp
    This file is the main DLL source file that contains the definition of
    DllMain().  It also exports the function GetCustomAppWizClass(), which
    returns a pointer to the one instance of this custom AppWizard's
    CCustomAppWiz-derived class.

Extensions.h
    This file is the main header file for the DLL.  It includes your 
    RESOURCE.H file.

Extensions.rc
    This file is a listing of all of the Microsoft Windows resources that the
    program uses.  It includes all of your custom AppWizard's templates as
    custom resources of type "TEMPLATE".  These resources are pointers to the
    files in your project's TEMPLATE directory.  This file can be directly
    edited in the Visual C++ development environment.  However, you will
    probably want to edit your templates by opening the template files directly
    in the source editor rather than by editing the "TEMPLATE" resources from
    the Visual C++ resource editor.

Extensions.clw
    This file contains information used by ClassWizard to edit existing
    classes or add new classes.  ClassWizard also uses this file to store
    information needed to create and edit message maps and dialog data
    maps and to create prototype member functions.

/////////////////////////////////////////////////////////////////////////////
Custom AppWizard Interface:

ExtensionsAw.h, ExtensionsAw.cpp - the CCustomAppWiz class
    These files contain your CCustomAppWiz-derived class,
    CExtensionsAppWiz.  This class contains virtual member functions which
    MFCAPWZ.DLL calls to initialize your custom AppWizard and to query which
    step to pop up at a given time.  This class also contains m_Dictionary,
    a CMapStringToString member variable, which maps template macro names
    to their values.

/////////////////////////////////////////////////////////////////////////////
Template Files:

Template\
    Put your template files in this directory.  Template files are stored
    in your custom AppWizard as custom resources of type "TEMPLATE", and are
    used by your custom AppWizard to determine the contents of the files it
    generates. When you add a new template file to this directory, you must
    import that file as a "TEMPLATE" custom resource into Extensions.rc.  Be
    sure to select the "External File" checkbox on the custom resource's
    property page.

Template\Confirm.inf
    In this template you should put a description of the project your
    custom AppWizard generates.  The file uses template macros to customize the
    text to reflect which options were selected by the custom AppWizard user.
    When the custom AppWizard user clicks the "Finish" button, MFCAPWZ.DLL
    parses this template and sends the output to the New Project Information
    dialog.

Template\NewProj.inf
    This template lists all of the templates other than Confirm.inf and
    NewProj.inf which your custom AppWizard will use to generate a project.
    After MFCAPWZ.DLL parses this template, the output lists the other
    templates to be parsed and what the output files should be called.
        Initially, this file contains the names of the templates that were
    generated from the project "E:\Workspaces\ShellExtensions\ShellExtensions.dsp".  You will not need to edit
    this template unless you add functionality to the project generated by
    your custom AppWizard.
        See the documentation on custom AppWizards for a more complete
    description of this template and the project generation process in general.

You have also been provided with template files in this directory based
off of the project "E:\Workspaces\ShellExtensions\ShellExtensions.dsp".

/////////////////////////////////////////////////////////////////////////////
Other Standard Files:

StdAfx.h, StdAfx.cpp
    These files are used to build a precompiled header (PCH) file
    named Extensions.pch and a precompiled types file named StdAfx.obj.

Rresource.h
    This is the standard header file, which defines new resource IDs.
    Visual C++ reads and updates this file.

/////////////////////////////////////////////////////////////////////////////
Other Notes:

AppWizard uses "TODO:" to indicate parts of the source code you
should add to or customize.