Added missing MFC ref topics (MicrosoftDocs#232)

* temp commit for new mfc macros functions

* added remaining macros and globals

* fixed broken links from previous commit

Author: mikeblome

docs/mfc/reference/TOC.md

@@ -465,6 +465,7 @@
 ## [Type Casting of MFC Class Objects](type-casting-of-mfc-class-objects.md)
 ## [Run-Time Object Model Services](run-time-object-model-services.md)
 ## [Diagnostic Services](diagnostic-services.md)
+## [Modules and DLLs](extension-dll-macros.md)
 ## [Exception Processing](exception-processing.md)
 ## [CString Formatting and Message-Box Display](cstring-formatting-and-message-box-display.md)
 ## [Application Information and Management](application-information-and-management.md)
@@ -496,6 +497,7 @@
 ## [AFX Messages](afx-messages.md)
 ## [ToolBar Control Styles](toolbar-control-styles.md)
 ## [CMFCImagePaintArea::IMAGE_EDIT_MODE Enumeration](cmfcimagepaintarea-image-edit-mode-enumeration.md)
+## [UICheckState Enumeration](uicheckstate-enumeration.md)
 # [Structures, Styles, Callbacks, and Message Maps](structures-styles-callbacks-and-message-maps.md)
 ## [Structures Used by MFC](structures-used-by-mfc.md)
 ### [ABC Structure](abc-structure.md)
@@ -560,6 +562,7 @@
 ### [Callback Function for CDC::SetAbortProc](callback-function-for-cdc-setabortproc.md)
 ## [Message Maps (MFC)](message-maps-mfc.md)
 ### [Message Map Macros (MFC)](message-map-macros-mfc.md)
+### [Delegate and Interface Map Macros](delegate-and-interface-maps.md)
 ### [How to: Use the Message-Map Cross-Reference](how-to-use-the-message-map-cross-reference.md)
 ### [WM_COMMAND Message Handler](wm-command-message-handler.md)
 ### [Child Window Notification Message Handlers](child-window-notification-message-handlers.md)

docs/mfc/reference/application-control.md

@@ -35,7 +35,7 @@ translation.priority.ht:
   - "zh-tw"
 ---
 # Application Control
-OLE requires substantial control over applications and their objects. The OLE system DLLs must be able to launch and release applications automatically, coordinate their production and modification of objects, and so on. The functions in this topic meet those requirements. In addition to being called by the OLE system DLLs, these functions must sometimes be called by applications as well.  
+OLE requires substantial control over applications and their objects. The OLE system DLLs must be able to launch and release applications automatically, coordinate their production and modification of objects, and so on. The functions in this topic meet those requirements. In addition to being called by the OLE system DLLs, these functions must sometimes be called by applications as well. 
 
 ### Application Control  
 
@@ -46,9 +46,12 @@ OLE requires substantial control over applications and their objects. The OLE sy
 |[AfxOleGetUserCtrl](#afxolegetuserctrl)|Retrieves the current user-control flag.|  
 |[AfxOleSetUserCtrl](#afxolesetuserctrl)|Sets or clears the user-control flag.|  
 |[AfxOleLockApp](#afxolelockapp)|Increments the framework's global count of the number of active objects in an application.|  
-|[AfxOleUnlockApp](#afxoleunlockapp)|Decrements the framework's count of the number of active objects in an application.|  
+|[AfxOleLockControl](#afxolelockcontrol)| Locks the class factory of the specified control. |
+|[AfxOleUnlockApp](#afxoleunlockapp)|Decrements the framework's count of the number of active objects in an application.| 
+|[AfxOleUnlockControl](#afxoleunlockcontrol)| Unlocks the class factory of the specified control. |
 |[AfxOleRegisterServerClass](#afxoleregisterserverclass)|Registers a server in the OLE system registry.|  
 |[AfxOleSetEditMenu](#afxoleseteditmenu)|Implements the user interface for the *typename* Object command.|  
+
 
 ##  <a name="afxolecanexitapp"></a>  AfxOleCanExitApp  
  Indicates whether the application can terminate.  
@@ -73,7 +76,7 @@ BOOL AFXAPI AfxOleCanExitApp();
  Retrieves the application's current message filter.  
 
 ```   
-COleMessageFilter* AFXAPI  AfxOleGetMessageFilter(); 
+COleMessageFilter* AFXAPI AfxOleGetMessageFilter(); 
 ```  
 
 ### Return Value  
@@ -94,7 +97,7 @@ COleMessageFilter* AFXAPI  AfxOleGetMessageFilter();
  Retrieves the current user-control flag.  
 
 ```   
-BOOL  AFXAPI AfxOleGetUserCtrl(); 
+BOOL AFXAPI AfxOleGetUserCtrl(); 
 ```  
 
 ### Return Value  
@@ -110,7 +113,7 @@ BOOL  AFXAPI AfxOleGetUserCtrl();
  Sets or clears the user-control flag, which is explained in the reference for `AfxOleGetUserCtrl`.  
 
 ```  
-void  AFXAPI AfxOleSetUserCtrl(BOOL bUserCtrl); 
+void AFXAPI AfxOleSetUserCtrl(BOOL bUserCtrl); 
 ```  
 
 ### Parameters  
@@ -129,7 +132,7 @@ void  AFXAPI AfxOleSetUserCtrl(BOOL bUserCtrl);
  Increments the framework's global count of the number of active objects in the application.  
 
 ```   
-void  AFXAPI  AfxOleLockApp(); 
+void AFXAPI AfxOleLockApp(); 
 ```  
 
 ### Remarks  
@@ -163,6 +166,43 @@ void AFXAPI AfxOleUnlockApp();
 ### Requirements  
  **Header**: afxdisp.h  
 
+ ## AfxOleLockControl
+Locks the class factory of the specified control so that dynamically created data associated with the control remains in memory.  
+   
+### Syntax    
+```
+BOOL AFXAPI AfxOleLockControl(  REFCLSID clsid  );  
+BOOL AFXAPI AfxOleLockControl( LPCTSTR lpszProgID );  
+```
+### Parameters  
+ `clsid`  
+ The unique class ID of the control.  
+  
+ `lpszProgID`  
+ The unique program ID of the control.  
+   
+### Return Value  
+ Nonzero if the class factory of the control was successfully locked; otherwise 0.  
+   
+### Remarks  
+ This can significantly speed up display of the controls. For example, once you create a control in a dialog box and lock the control with `AfxOleLockControl`, you do not need to create and kill it again every time the dialog is shown or destroyed. If the user opens and closes a dialog box repeatedly, locking your controls can significantly enhance performance. When you are ready to destroy the control, call `AfxOleUnlockControl`.  
+   
+### Example  
+```cpp
+// Starts and locks control's (Microsoft Calendar) class factory. 
+// Control will remain in memory for lifetime of
+// application or until AfxOleUnlockControl() is called.
+
+AfxOleLockControl(_T("MSCAL.Calendar"));
+```
+   
+### Requirements  
+ **Header:** <afxwin.h>  
+   
+### See Also  
+ [Macros and Globals](mfc-macros-and-globals.md)   
+ [AfxOleUnlockControl](#afxoleunlockcontrol)
+ 
 ##  <a name="afxoleregisterserverclass"></a>  AfxOleRegisterServerClass  
  This function allows you to register your server in the OLE system registry.  
   
@@ -232,7 +272,7 @@ BOOL AFXAPI AfxOleRegisterServerClass(
  Implements the user interface for the *typename* Object command.  
   
 ```   
-void  AFXAPI  AfxOleSetEditMenu(
+void AFXAPI AfxOleSetEditMenu(
     COleClientItem* pClient,  
     CMenu* pMenu,  
     UINT iMenuItem,  
@@ -272,3 +312,40 @@ void  AFXAPI  AfxOleSetEditMenu(
 
 ## See Also  
  [Macros and Globals](../../mfc/reference/mfc-macros-and-globals.md)
+
+## <a name="afxoleunlockcontrol"></a> AfxOleUnlockControl
+Unlocks the class factory of the specified control.  
+   
+### Syntax  
+  ```
+BOOL AFXAPI AfxOleUnlockControl( REFCLSID clsid );  
+BOOL AFXAPI AfxOleUnlockControl( LPCTSTR lpszProgID );  
+```
+### Parameters  
+ `clsid`  
+ The unique class ID of the control.  
+  
+ `lpszProgID`  
+ The unique program ID of the control.  
+   
+### Return Value  
+ Nonzero if the class factory of the control was successfully unlocked; otherwise 0.  
+   
+### Remarks  
+ A control is locked with `AfxOleLockControl`, so that dynamically created data associated with the control remains in memory. This can significantly speed up display of the control because the control need not be created and destroyed every time it is displayed. When you are ready to destroy the control, call `AfxOleUnlockControl`.  
+   
+### Example  
+ ```cpp
+// Unlock control's (Microsoft Calendar Control) class factory.
+
+AfxOleUnlockControl(_T("MSCAL.Calendar"));
+
+```
+   
+### Requirements  
+ **Header:** <afxwin.h>  
+   
+### See Also  
+ [Macros and Globals](mfc-macros-and-globals.md)  
+ [AfxOleLockControl](#afxolelockcontrol)
+