Merge pull request #2309 from mikeblome/mb-1068

Updates across MFC for updated Class Wizard UI

Author: v-shils

.openpublishing.redirection.json

@@ -624,7 +624,7 @@
          "source_path": "docs/build/reference/input-and-output-manifest-tool.md",
          "redirect_url": "/cpp/build/reference/manifest-tool-property-pages",
          "redirect_document_id": false
-      },       
+      },
       {
          "source_path": "docs/build/reference/isolated-com-manifest-tool.md",
          "redirect_url": "/cpp/build/reference/manifest-tool-property-pages",
@@ -7320,6 +7320,11 @@
          "redirect_url": "/cpp/mfc/using-the-mfc-source-files",
          "redirect_document_id": false
       },
+      {
+         "source_path": "docs/mfc/document-template-strings-mfc-add-class-wizard.md",
+         "redirect_url": "/cpp/mfc/reference/mfc-add-class-wizard",
+         "redirect_document_id": false
+      },
       {
          "source_path": "docs/mfc/automatic-linking-of-mfc-library-version.md",
          "redirect_url": "/cpp/mfc/mfc-library-versions",

docs/ide/adding-functionality-with-code-wizards-cpp.md

@@ -22,13 +22,13 @@ Once you have created a project, you will want to change or add to that project'
 
 
 > [!NOTE]
->  You can now add message handlers and map messages to them and override MFC virtual functions using the [Properties window](/visualstudio/ide/reference/properties-window).
+>  You can add message handlers and map messages to them and override MFC virtual functions using the [MFC Class Wizard](../mfc/reference/mfc-class-wizard.md).
 
 ## Accessing C++ Code Wizards
 
 There are three locations where you can access C++ code wizards:
 
-- On the **Project** menu, the **Add New Item** command allows you to bring up the `Add New Item` dialog box, which helps you to add new files to your project. The **Add Class** command displays the [Add Class](../ide/add-class-dialog-box.md) dialog box, which in turn open wizards for each of the class types you can add to your project. The **Add Resource** command displays the [Add Resource](../windows/add-resource-dialog-box.md) dialog box, from which you can create or select a resource to add to your project.
+- On the **Project** menu, the **Add New Item** command allows you to bring up the `Add New Item` dialog box, which helps you to add new files to your project. The **Add Class** command displays the [Add Class](../ide/add-class-dialog-box.md) dialog box, which in turn open wizards for each of the class types you can add to your project. For MFC classes, use the [MFC Class Wizard](../mfc/reference/mfc-class-wizard.md). The **Add Resource** command displays the [Add Resource](../windows/add-resource-dialog-box.md) dialog box, from which you can create or select a resource to add to your project.
 
    If you highlight a class or an interface in your project in Class View, the **Project** menu also displays the following commands:
 

docs/mfc/activex-control-containers-handling-events-from-an-activex-control.md

@@ -6,26 +6,26 @@ ms.assetid: f9c106db-052f-4e32-82ad-750646aa760b
 ---
 # ActiveX Control Containers: Handling Events from an ActiveX Control
 
-This article discusses using the Properties window to install event handlers for ActiveX controls in an ActiveX control container. The event handlers are used to receive notifications (from the control) of certain events and perform some action in response. This notification is called "firing" the event.
+This article discusses using the **Properties** window (in **Class View**) to install event handlers for ActiveX controls in an ActiveX control container. The event handlers are used to receive notifications (from the control) of certain events and perform some action in response. This notification is called "firing" the event.
 
 >[!IMPORTANT]
 > ActiveX is a legacy technology that should not be used for new development. For more information about modern technologies that supersede ActiveX, see [ActiveX Controls](activex-controls.md).
 
 > [!NOTE]
 >  This article uses a dialog-based ActiveX control container project named Container and an embedded control named Circ as examples in the procedures and code.
 
-Using the Events button in the Properties window, you can create a map of events that can occur in your ActiveX control container application. This map, called an "event sink map,'' is created and maintained by Visual C++ when you add event handlers to the control container class. Each event handler, implemented with an event map entry, maps a specific event to a container event handler member function. This event handler function is called when the specified event is fired by the ActiveX control object.
+Using the Events button in the **Properties** window (in **Class View**), you can create a map of events that can occur in your ActiveX control container application. This map, called an "event sink map,'' is created and maintained by Visual C++ when you add event handlers to the control container class. Each event handler, implemented with an event map entry, maps a specific event to a container event handler member function. This event handler function is called when the specified event is fired by the ActiveX control object.
 
 For more information on event sink maps, see [Event Sink Maps](../mfc/reference/event-sink-maps.md) in the *Class Library Reference*.
 
 ##  <a name="_core_event_handler_modifications_to_the_project"></a> Event Handler Modifications to the Project
 
-When you use the Properties window to add event handlers, an event sink map is declared and defined in your project. The following statements are added to the control .CPP file the first time an event handler is added. This code declares an event sink map for the dialog box class (in this case, `CContainerDlg`):
+When you use the **Properties** window to add event handlers, an event sink map is declared and defined in your project. The following statements are added to the control .CPP file the first time an event handler is added. This code declares an event sink map for the dialog box class (in this case, `CContainerDlg`):
 
 [!code-cpp[NVC_MFC_AxCont#8](../mfc/codesnippet/cpp/activex-control-containers-handling-events-from-an-activex-control_1.cpp)]
 [!code-cpp[NVC_MFC_AxCont#9](../mfc/codesnippet/cpp/activex-control-containers-handling-events-from-an-activex-control_2.cpp)]
 
-As you use the Properties window to add events, an event map entry (`ON_EVENT`) is added to the event sink map and an event handler function is added to the container's implementation (.CPP) file.
+As you use the **Properties** window to add events, an event map entry (`ON_EVENT`) is added to the event sink map and an event handler function is added to the container's implementation (.CPP) file.
 
 The following example declares an event handler, called `OnClickInCircCtrl`, for the Circ control's `ClickIn` event:
 
@@ -41,11 +41,11 @@ For more information on event sink macros, see [Event Sink Maps](../mfc/referenc
 
 1. From Class View, select the dialog class that contains the ActiveX control. For this example, use `CContainerDlg`.
 
-1. In the Properties window, click the **Events** button.
+1. In the **Properties** window, click the **Events** button.
 
-1. In the Properties window, select the control ID of the embedded ActiveX control. For this example, use `IDC_CIRCCTRL1`.
+1. In the **Properties** window, select the control ID of the embedded ActiveX control. For this example, use `IDC_CIRCCTRL1`.
 
-   The Properties window displays a list of events that can be fired by the embedded ActiveX control. Any member function shown in bold already has handler functions assigned to it.
+   The **Properties** window displays a list of events that can be fired by the embedded ActiveX control. Any member function shown in bold already has handler functions assigned to it.
 
 1. Select the event you want the dialog class to handle. For this example, select **Click**.
 

docs/mfc/activex-control-containers-viewing-and-modifying-control-properties.md

@@ -24,7 +24,7 @@ The first step in viewing the control's properties is to add an instance of the
 
 1. Select the ActiveX control in the dialog box.
 
-1. From the Properties window, click the **Properties** button.
+1. From the **Properties** window, click the **Properties** button.
 
 Use the **Properties** dialog box to modify and test new properties immediately.
 

docs/mfc/automation-servers.md

@@ -25,7 +25,7 @@ The framework's principal mechanism for supporting Automation is the dispatch ma
 
 [!code-cpp[NVC_MFCAutomation#1](../mfc/codesnippet/cpp/automation-servers_1.cpp)]
 
-The Properties window and Class View assist in maintaining dispatch maps. When you add a new method or property to a class, Visual C++ adds a corresponding `DISP_FUNCTION` or `DISP_PROPERTY` macro with parameters indicating the class name, external and internal names of the method or property, and data types.
+The [Class Wizard](reference/mfc-class-wizard.md) and Class View assist in maintaining dispatch maps. When you add a new method or property to a class, Visual Studio adds a corresponding `DISP_FUNCTION` or `DISP_PROPERTY` macro with parameters indicating the class name, external and internal names of the method or property, and data types.
 
 The **Add Class** dialog box also simplifies the declaration of Automation classes and the management of their properties and operations. When you use the Add Class dialog box to add a class to your project, you specify its base class. If the base class allows Automation, the Add Class dialog box displays controls you use to specify whether the new class should support Automation, whether it is "OLE creatable" (that is, whether objects of the class can be created on a request from a COM client), and the external name for the COM client to use.
 

docs/mfc/command-routing.md

@@ -1,12 +1,12 @@
 ---
 title: "Command Routing"
-ms.date: "11/04/2016"
+ms.date: "09/06/2019"
 helpviewer_keywords: ["MFC, command routing", "command handling [MFC], routing commands", "handlers [MFC]", "handlers, command [MFC]", "command routing"]
 ms.assetid: 9393a956-bdd4-47c5-9013-dbd680433f93
 ---
 # Command Routing
 
-Your responsibility in working with commands is limited to making message-map connections between commands and their handler functions, a task for which you use the Properties window. You must also write most command handlers.
+Your responsibility in working with commands is limited to making message-map connections between commands and their handler functions, a task for which you use the [MFC Class Wizard](reference/mfc-class-wizard.md). You must also write the code for the command handlers.
 
 Windows messages are usually sent to the main frame window, but command messages are then routed to other objects. The framework routes commands through a standard sequence of command-target objects, one of which is expected to have a handler for the command. Each command-target object checks its message map to see if it can handle the incoming message.
 

docs/mfc/commonly-overridden-member-functions.md

@@ -1,6 +1,6 @@
 ---
 title: "Commonly Overridden Member Functions"
-ms.date: "11/04/2016"
+ms.date: "09/06/2019"
 helpviewer_keywords: ["CDialog class [MFC], members", "OnInitDialog function", "dialog classes [MFC], commonly overridden member functions", "OnCancel function", "overriding, dialog class members", "OnOK function", "MFC dialog boxes [MFC], overriding member functions"]
 ms.assetid: 78eb566c-e361-4c86-8db5-c7e2791b249a
 ---
@@ -16,7 +16,7 @@ The following table lists the most likely member functions to override in your `
 |`OnOK`|**BN_CLICKED** for button **IDOK**|Respond when the user clicks the OK button.|
 |`OnCancel`|**BN_CLICKED** for button **IDCANCEL**|Respond when the user clicks the Cancel button.|
 
-`OnInitDialog`, `OnOK`, and `OnCancel` are virtual functions. To override them, you declare an overriding function in your derived dialog class using the [Properties window](/visualstudio/ide/reference/properties-window).
+`OnInitDialog`, `OnOK`, and `OnCancel` are virtual functions. To override them, you declare an overriding function in your derived dialog class using the [MFC Class Wizard](reference/mfc-class-wizard.md).
 
 `OnInitDialog` is called just before the dialog box is displayed. You must call the default `OnInitDialog` handler from your override — usually as the first action in the handler. By default, `OnInitDialog` returns **TRUE** to indicate that the focus should be set to the first control in the dialog box.
 

docs/mfc/creating-an-extended-combo-box-control.md

@@ -16,7 +16,7 @@ How the extended combo box control is created depends on whether you are using t
 
 1. Use the [Add Member Variable Wizard](../ide/adding-a-member-variable-visual-cpp.md) to add a member variable of type [CComboBoxEx](../mfc/reference/ccomboboxex-class.md) with the Control property. You can use this member to call `CComboBoxEx` member functions.
 
-1. Use the Properties window to map handler functions in the dialog class for any extended combo box control notification messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
+1. Use the [Class Wizard](reference/mfc-class-wizard.md) to map handler functions in the dialog class for any extended combo box control notification messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
 
 1. In [OnInitDialog](../mfc/reference/cdialog-class.md#oninitdialog), set any additional styles for the `CComboBoxEx` object.
 

docs/mfc/creating-the-date-and-time-picker-control.md

@@ -16,7 +16,7 @@ How the date and time picker control is created depends on whether you are using
 
 1. Use the [Add Member Variable Wizard](../ide/adding-a-member-variable-visual-cpp.md) to add a member variable of type [CDateTimeCtrl](../mfc/reference/cdatetimectrl-class.md) with the Control property. You can use this member to call `CDateTimeCtrl` member functions.
 
-1. Use the Properties window to map handler functions in the dialog class for any date time picker control [notification](../mfc/processing-notification-messages-in-date-and-time-picker-controls.md) messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
+1. Use the [Class Wizard](reference/mfc-class-wizard.md) to map handler functions in the dialog class for any date time picker control [notification](../mfc/processing-notification-messages-in-date-and-time-picker-controls.md) messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
 
 1. In [OnInitDialog](../mfc/reference/cdialog-class.md#oninitdialog), set any additional styles for the `CDateTimeCtrl` object.
 

docs/mfc/creating-the-header-control.md

@@ -16,7 +16,7 @@ The header control is not directly available in the dialog editor (although you
 
 1. Add items to the header control.
 
-1. Use the Properties window to map handler functions in the dialog class for any header-control notification messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
+1. Use the [Class Wizard](reference/mfc-class-wizard.md) to map handler functions in the dialog class for any header-control notification messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
 
 ### To put a header control in a view (not a CListView)
 
@@ -26,7 +26,7 @@ The header control is not directly available in the dialog editor (although you
 
 1. Add items to the header control.
 
-1. Use the Properties window to map handler functions in the view class for any header-control notification messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
+1. Use the [Class Wizard](reference/mfc-class-wizard.md) to map handler functions in the view class for any header-control notification messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
 
 In either case, the embedded control object is created when the view or dialog object is created. Then you must call [CHeaderCtrl::Create](../mfc/reference/cheaderctrl-class.md#create) to create the control window. To position the control, call [CHeaderCtrl::Layout](../mfc/reference/cheaderctrl-class.md#layout) to determine the control's initial size and position and [SetWindowPos](../mfc/reference/cwnd-class.md#setwindowpos) to set the position you want. Then add items as described in [Adding Items to the Header Control](../mfc/adding-items-to-the-header-control.md).
 

docs/mfc/creating-the-list-control.md

@@ -14,7 +14,7 @@ How the list control ([CListCtrl](../mfc/reference/clistctrl-class.md)) is creat
 
 1. Use the [Add Member Variable Wizard](../ide/adding-a-member-variable-visual-cpp.md) to add a member variable of type `CListCtrl` with the Control property. You can use this member to call `CListCtrl` member functions.
 
-1. Use the Properties window to map handler functions in the dialog class for any list control notification messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
+1. Use the [Class Wizard](reference/mfc-class-wizard.md) to map handler functions in the dialog class for any list control notification messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
 
 1. In [OnInitDialog](../mfc/reference/cdialog-class.md#oninitdialog), set the styles for the `CListCtrl`. See [Changing List Control Styles](../mfc/changing-list-control-styles.md). This determines the kind of "view" you get in the control, although you can change the view later.
 

docs/mfc/creating-the-month-calendar-control.md

@@ -16,7 +16,7 @@ How the month calendar control is created depends on whether you are using the c
 
 1. Use the [Add Member Variable Wizard](../ide/adding-a-member-variable-visual-cpp.md) to add a member variable of type [CMonthCalCtrl](../mfc/reference/cmonthcalctrl-class.md) with the Control property. You can use this member to call `CMonthCalCtrl` member functions.
 
-1. Use the Properties window to map handler functions in the dialog class for any month calendar control notification messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
+1. Use the [Class Wizard](reference/mfc-class-wizard.md) to map handler functions in the dialog class for any month calendar control notification messages you need to handle (see [Mapping Messages to Functions](../mfc/reference/mapping-messages-to-functions.md)).
 
 1. In [OnInitDialog](../mfc/reference/cdialog-class.md#oninitdialog), set any additional styles for the `CMonthCalCtrl` object.
 

docs/mfc/creating-your-dialog-class.md

@@ -1,20 +1,20 @@
 ---
 title: "Creating Your Dialog Class"
-ms.date: "11/04/2016"
+ms.date: "09/06/2019"
 helpviewer_keywords: ["dialog boxes [MFC], creating", "MFC dialog boxes [MFC], creating", "files [MFC], creating", "dialog classes [MFC], Add Class Wizard", "dialog classes [MFC], creating"]
 ms.assetid: d5321741-da41-47a8-bb1c-6a0e8b28c4c1
 ---
 # Creating Your Dialog Class
 
 For each dialog box in your program, create a new dialog class to work with the dialog resource.
 
-[Adding a Class](../ide/adding-a-class-visual-cpp.md) explains how to create a new dialog class. When you create a dialog class with the Add Class Wizard, it writes the following items in the .H and .CPP files you specify:
+[Adding a Class](../ide/adding-a-class-visual-cpp.md) explains how to create a new dialog class. When you create a dialog class with the [Class Wizard](reference/mfc-class-wizard.md), it writes the following items in the .h and .cpp files you specify:
 
-In the .H file:
+In the .h file:
 
 - A class declaration for the dialog class. The class is derived from [CDialog](../mfc/reference/cdialog-class.md).
 
-In the .CPP file:
+In the .cpp file:
 
 - A message map for the class.