Merge pull request MicrosoftDocs#2364 from MicrosoftDocs/master637329378499860270

Colin Robertson · web-flow · commit 3c59449bf800 · 2020-08-13T11:05:29.000-07:00
Repo sync for protected CLA branch
diff --git a/docs/atl/reference/aggregation-and-class-factory-macros.md b/docs/atl/reference/aggregation-and-class-factory-macros.md
@@ -1,28 +1,28 @@
 ---
 title: "Aggregation and Class Factory Macros"
-ms.date: "11/04/2016"
-f1_keywords: ["atlcom/ATL::DECLARE_AGGREGATABLE", "atlcom/ATL::DECLARE_CLASSFACTORY", "atlcom/ATL::DECLARE_CLASSFACTORY_EX", "atlcom/ATL::DECLARE_CLASSFACTORY_AUTO_THREAD", "atlcom/ATL::DECLARE_CLASSFACTORY_SINGLETON", "atlcom/ATL::DECLARE_GET_CONTROLLING_UNKNOWN", "atlcom/ATL::DECLARE_NOT_AGGREGATABLE", "atlcom/ATL::DECLARE_ONLY_AGGREGATABLE", "atlcom/ATL::DECLARE_POLY_AGGREGATABLE", "atlcom/ATL::DECLARE_PROTECT_FINAL_CONSTRUCT", "atlcom/ATL::DECLARE_VIEW_STATUS"]
-helpviewer_keywords: ["class factories, ATL macros", "aggregation [C++], ATL macros"]
+ms.date: 08/12/2020
+f1_keywords: ["ATLCOM/ATL::DECLARE_AGGREGATABLE", "ATLCOM/ATL::DECLARE_CLASSFACTORY", "ATLCOM/ATL::DECLARE_CLASSFACTORY_EX", "ATLCOM/ATL::DECLARE_CLASSFACTORY_AUTO_THREAD", "ATLCOM/ATL::DECLARE_CLASSFACTORY_SINGLETON", "ATLCOM/ATL::DECLARE_GET_CONTROLLING_UNKNOWN", "ATLCOM/ATL::DECLARE_NOT_AGGREGATABLE", "ATLCOM/ATL::DECLARE_ONLY_AGGREGATABLE", "ATLCOM/ATL::DECLARE_POLY_AGGREGATABLE", "ATLCOM/ATL::DECLARE_PROTECT_FINAL_CONSTRUCT", "ATLCOM/ATL::DECLARE_VIEW_STATUS", "ATLDEF/ATL::DECLARE_AGGREGATABLE", "ATLDEF/ATL::DECLARE_CLASSFACTORY", "ATLDEF/ATL::DECLARE_CLASSFACTORY_EX", "ATLDEF/ATL::DECLARE_CLASSFACTORY_AUTO_THREAD", "ATLDEF/ATL::DECLARE_CLASSFACTORY_SINGLETON", "ATLDEF/ATL::DECLARE_GET_CONTROLLING_UNKNOWN", "ATLDEF/ATL::DECLARE_NOT_AGGREGATABLE", "ATLDEF/ATL::DECLARE_ONLY_AGGREGATABLE", "ATLDEF/ATL::DECLARE_POLY_AGGREGATABLE", "ATLDEF/ATL::DECLARE_PROTECT_FINAL_CONSTRUCT", "ATLDEF/ATL::DECLARE_VIEW_STATUS", "ATLCOM/DECLARE_AGGREGATABLE", "ATLCOM/DECLARE_CLASSFACTORY", "ATLCOM/DECLARE_CLASSFACTORY_EX", "ATLCOM/DECLARE_CLASSFACTORY_AUTO_THREAD", "ATLCOM/DECLARE_CLASSFACTORY_SINGLETON", "ATLCOM/DECLARE_GET_CONTROLLING_UNKNOWN", "ATLCOM/DECLARE_NOT_AGGREGATABLE", "ATLCOM/DECLARE_ONLY_AGGREGATABLE", "ATLCOM/DECLARE_POLY_AGGREGATABLE", "ATLCOM/DECLARE_PROTECT_FINAL_CONSTRUCT", "ATLCOM/DECLARE_VIEW_STATUS", "ATL::DECLARE_AGGREGATABLE", "ATL::DECLARE_CLASSFACTORY", "ATL::DECLARE_CLASSFACTORY_EX", "ATL::DECLARE_CLASSFACTORY_AUTO_THREAD", "ATL::DECLARE_CLASSFACTORY_SINGLETON", "ATL::DECLARE_GET_CONTROLLING_UNKNOWN", "ATL::DECLARE_NOT_AGGREGATABLE", "ATL::DECLARE_ONLY_AGGREGATABLE", "ATL::DECLARE_POLY_AGGREGATABLE", "ATL::DECLARE_PROTECT_FINAL_CONSTRUCT", "ATL::DECLARE_VIEW_STATUS", "DECLARE_AGGREGATABLE", "DECLARE_CLASSFACTORY", "DECLARE_CLASSFACTORY_EX", "DECLARE_CLASSFACTORY_AUTO_THREAD", "DECLARE_CLASSFACTORY_SINGLETON", "DECLARE_GET_CONTROLLING_UNKNOWN", "DECLARE_NOT_AGGREGATABLE", "DECLARE_ONLY_AGGREGATABLE", "DECLARE_POLY_AGGREGATABLE", "DECLARE_PROTECT_FINAL_CONSTRUCT", "DECLARE_VIEW_STATUS"]
+helpviewer_keywords: ["class factories, ATL macros", "aggregation [C++], ATL macros", "ATL::DECLARE_AGGREGATABLE", "ATL::DECLARE_CLASSFACTORY", "ATL::DECLARE_CLASSFACTORY_EX", "ATL::DECLARE_CLASSFACTORY_AUTO_THREAD", "ATL::DECLARE_CLASSFACTORY_SINGLETON", "ATL::DECLARE_GET_CONTROLLING_UNKNOWN", "ATL::DECLARE_NOT_AGGREGATABLE", "ATL::DECLARE_ONLY_AGGREGATABLE", "ATL::DECLARE_POLY_AGGREGATABLE", "ATL::DECLARE_PROTECT_FINAL_CONSTRUCT", "ATL::DECLARE_VIEW_STATUS"]
 ms.assetid: d99d379a-0eec-481f-8daa-252dac18f163
 ---
 # Aggregation and Class Factory Macros
 
 These macros provide ways of controlling aggregation and of declaring class factories.
 
-|||
-|-|-|
-|[DECLARE_AGGREGATABLE](#declare_aggregatable)|Declares that your object can be aggregated (the default).|
-|[DECLARE_CLASSFACTORY](#declare_classfactory)|Declares the class factory to be [CComClassFactory](../../atl/reference/ccomclassfactory-class.md), the ATL default class factory.|
-|[DECLARE_CLASSFACTORY_EX](#declare_classfactory_ex)|Declares your class factory object to be the class factory.|
-|[DECLARE_CLASSFACTORY2](#declare_classfactory2)|Declares [CComClassFactory2](../../atl/reference/ccomclassfactory2-class.md) to be the class factory.|
-|[DECLARE_CLASSFACTORY_AUTO_THREAD](#declare_classfactory_auto_thread)|Declares [CComClassFactoryAutoThread](../../atl/reference/ccomclassfactoryautothread-class.md) to be the class factory.|
-|[DECLARE_CLASSFACTORY_SINGLETON](#declare_classfactory_singleton)|Declares [CComClassFactorySingleton](../../atl/reference/ccomclassfactorysingleton-class.md) to be the class factory.|
-|[DECLARE_GET_CONTROLLING_UNKNOWN](#declare_get_controlling_unknown)|Declares a virtual `GetControllingUnknown` function.|
-|[DECLARE_NOT_AGGREGATABLE](#declare_not_aggregatable)|Declares that your object cannot be aggregated.|
-|[DECLARE_ONLY_AGGREGATABLE](#declare_only_aggregatable)|Declares that your object must be aggregated.|
-|[DECLARE_POLY_AGGREGATABLE](#declare_poly_aggregatable)|Checks the value of the outer unknown and declares your object aggregatable or not aggregatable, as appropriate.|
-|[DECLARE_PROTECT_FINAL_CONSTRUCT](#declare_protect_final_construct)|Protects the outer object from deletion during construction of an inner object.|
-|[DECLARE_VIEW_STATUS](#declare_view_status)|Specifies the VIEWSTATUS flags to the container.|
+| Macro | Description |
+|--|--|
+| [DECLARE_AGGREGATABLE](#declare_aggregatable) | Declares that your object can be aggregated (the default). |
+| [DECLARE_CLASSFACTORY](#declare_classfactory) | Declares the class factory to be [CComClassFactory](../../atl/reference/ccomclassfactory-class.md), the ATL default class factory. |
+| [DECLARE_CLASSFACTORY_EX](#declare_classfactory_ex) | Declares your class factory object to be the class factory. |
+| [DECLARE_CLASSFACTORY2](#declare_classfactory2) | Declares [CComClassFactory2](../../atl/reference/ccomclassfactory2-class.md) to be the class factory. |
+| [DECLARE_CLASSFACTORY_AUTO_THREAD](#declare_classfactory_auto_thread) | Declares [CComClassFactoryAutoThread](../../atl/reference/ccomclassfactoryautothread-class.md) to be the class factory. |
+| [DECLARE_CLASSFACTORY_SINGLETON](#declare_classfactory_singleton) | Declares [CComClassFactorySingleton](../../atl/reference/ccomclassfactorysingleton-class.md) to be the class factory. |
+| [DECLARE_GET_CONTROLLING_UNKNOWN](#declare_get_controlling_unknown) | Declares a virtual `GetControllingUnknown` function. |
+| [DECLARE_NOT_AGGREGATABLE](#declare_not_aggregatable) | Declares that your object cannot be aggregated. |
+| [DECLARE_ONLY_AGGREGATABLE](#declare_only_aggregatable) | Declares that your object must be aggregated. |
+| [DECLARE_POLY_AGGREGATABLE](#declare_poly_aggregatable) | Checks the value of the outer unknown and declares your object aggregatable or not aggregatable, as appropriate. |
+| [DECLARE_PROTECT_FINAL_CONSTRUCT](#declare_protect_final_construct) | Protects the outer object from deletion during construction of an inner object. |
+| [DECLARE_VIEW_STATUS](#declare_view_status) | Specifies the VIEWSTATUS flags to the container. |
 
 ## Requirements
 
diff --git a/docs/build/reference/advanced-property-page.md b/docs/build/reference/advanced-property-page.md
@@ -1,30 +1,36 @@
 ---
 title: "Advanced Property Page (Project)"
-ms.date: "07/19/2019"
+ms.date: 08/10/2020
 f1_keywords: ["VC.Project.VCConfiguration.VCToolsVersion"]
 ms.description: "Use the Advanced property page in Visual Studio 2019 to set various properties for C++ projects."
 ---
 # Advanced Property Page
 
-The Advanced property page is available in Visual Studio 2019 and later.
+::: moniker range="<=vs-2017"
+
+The Advanced property page is available in Visual Studio 2019 and later. To see the documentation for that version, set the Visual Studio **Version** selector control for this article to Visual Studio 2019. It's found at the top of the table of contents on this page.
+
+::: moniker-end
 
 ::: moniker range="vs-2019"
 
+The Advanced property page is available in Visual Studio 2019 and later.
+
 ## Advanced Properties
 
 - **Target File Extension**
 
-   Specifies the file extension to use for the build output. Defaults to **.exe** for applications, **.lib** for static libraries and **.dll** for DLLs.
+   Specifies the file extension to use for the build output. Defaults to *`.exe`* for applications, *`.lib`* for static libraries and *`.dll`* for DLLs.
 
 - **Extensions to Delete on Clean**
 
-   The **Clean** option (**Build** menu) deletes files from the intermediate directory where a project's configuration is built. Files with extensions specified with this property will be deleted when **Clean** is run or when you perform a rebuild. In addition to files of these extensions in the intermediate directory, the build system will also delete any known output of the build regardless of where it is located (including intermediate outputs such as .obj files). Note that you can specify wildcard characters.
+   The **Clean** option (**Build** menu) deletes files from the intermediate directory where a project's configuration is built. Files with extensions specified in this property get deleted when **Clean** is run or when you rebuild. The build system deletes any files that have these extensions in the intermediate directory. It also deletes any known output of the build, no matter where it's located. (That includes the intermediate outputs such as *`.obj`* files.) You can specify wildcard characters in this property.
 
    To programmatically access this property, see <xref:Microsoft.VisualStudio.VCProjectEngine.VCConfiguration.DeleteExtensionsOnClean%2A>.
 
 - **Build Log File**
 
-   Allows you to specify a non-default location for the log file that is created whenever you build a project. The default location is specified by the macros $(IntDir)$(MSBuildProjectName).log.
+   Allows you to specify a non-default location for the log file that's created whenever you build a project. The default location is specified by the macros `$(IntDir)$(MSBuildProjectName).log`.
 
    You can use project macros to change the directory location. See [Common macros for build commands and properties](common-macros-for-build-commands-and-properties.md).
 
@@ -34,37 +40,53 @@ The Advanced property page is available in Visual Studio 2019 and later.
 
 - **Use Debug Libraries**
 
-   Specifies whether to create a DEBUG or RELEASE build.
+   Specifies whether to create a Debug or Release build.
 
 - **Enable Unity (JUMBO) build**
 
-   Enables a build process where many C++ source files are combined into one or more "unity" files before compilation to improve build performance. Unrelated to the Unity game engine.
+   Enables a faster build process that combines many C++ source files into one or more files before compilation. These combined files are known as *unity* files. They're unrelated to the Unity game engine.
+
+- **Copy Content to OutDir**
+
+   Copy the items marked as *content* in the project to the project's output directory (`$(OutDir)`). This setting can simplify deployment. This property is available starting in Visual Studio 2019 version 16.7.
+
+- **Copy Project References to OutDir**
+
+   Copy the executable (DLL and EXE file) project reference items to the project's output directory (`$(OutDir)`). In C++/CLI ([`/clr`](clr-common-language-runtime-compilation.md)) projects, this property is ignored. Instead, the **Copy Local** property on each project reference controls whether it's copied to the output directory. This setting can simplify local deployment. It's available starting in Visual Studio 2019 version 16.7.
+
+- **Copy Project References' Symbols to OutDir**
+
+   Copy the PDB files for project reference items along with the project reference executable items to the project's output directory (`$(OutDir)`). This property is always enabled for C++/CLI projects. This setting can simplify debug deployment. It's available starting in Visual Studio 2019 version 16.7.
+
+- **Copy C++ Runtime to OutDir**
+
+   Copy the runtime DLLs to the project's output directory (`$(OutDir)`). This setting can simplify local deployment. It's available starting in Visual Studio 2019 version 16.7.
 
 - **Use of MFC**
 
-   Specifies whether the MFC project will statically or dynamically link to the MFC DLL. Non-MFC projects can select **Use Standard Windows Libraries** to link to various Win32 libraries that are included when you use MFC.
+   Specifies whether the MFC project statically or dynamically links to the MFC DLL. In non-MFC projects, select **Use Standard Windows Libraries** to link the Win32 libraries included by MFC.
 
    To programmatically access this property, see <xref:Microsoft.VisualStudio.VCProject.VCProjectConfigurationProperties.useOfMfc%2A>.
 
 - **Character Set**
 
-   Defines whether _UNICODE or _MBCS should be set. Also affects the linker entry point where appropriate.
+   Defines whether `_UNICODE` or `_MBCS` should be set. Also affects the linker entry point where appropriate.
 
    To programmatically access this property, see <xref:Microsoft.VisualStudio.VCProject.VCProjectConfigurationProperties.CharacterSet%2A>.
 
 - **Whole Program Optimization**
 
-   Specifies the [/GL](gl-whole-program-optimization.md) compiler option and [/LTCG](ltcg-link-time-code-generation.md) linker option. By default, this is disabled for Debug configurations, and enabled for Retail configurations.
+   Specifies the [`/GL`](gl-whole-program-optimization.md) compiler option and [`/LTCG`](ltcg-link-time-code-generation.md) linker option. By default, whole program optimization is disabled for Debug configurations, and enabled for Release configurations.
 
 - **MSVC Toolset Version**
 
-   Specifies the full version of the MSVC toolset that will be used to build the project. If you have various update and preview versions of a toolset installed, you can specify which one to use here.
+   Specifies the full version of the MSVC toolset that's used to build the project. You may have various update and preview versions of a toolset installed. You can specify which one to use here.
 
 ## C++/CLI Properties
 
 - **Common Language Runtime support**
 
-   Causes the [/clr](clr-common-language-runtime-compilation.md) compiler option to be used.
+   Causes the [`/clr`](clr-common-language-runtime-compilation.md) compiler option to be used.
 
    To programmatically access this property, see <xref:Microsoft.VisualStudio.VCProject.VCProjectConfigurationProperties.ManagedExtensions%2A>.
 
@@ -74,6 +96,6 @@ The Advanced property page is available in Visual Studio 2019 and later.
 
 - **Enable Managed Incremental Build**
 
-   For managed projects, this enables detection of external visibility when you generate assemblies. If a change to a managed project is not visible to other projects, then dependent projects are not rebuilt. This can dramatically improve build times in solutions that include managed projects.
+   For managed projects, this option enables detection of external visibility when you generate assemblies. If a change to a managed project isn't visible to other projects, dependent projects aren't rebuilt. Managed incremental builds can dramatically improve build times in solutions that include managed projects.
 
 ::: moniker-end
diff --git a/docs/code-quality/c26474.md b/docs/code-quality/c26474.md
@@ -1,38 +1,41 @@
 ---
 title: C26474
-ms.date: 11/15/2017
+ms.date: 08/11/2020
 ms.topic: "conceptual"
 f1_keywords: ["C26474"]
 helpviewer_keywords: ["C26474"]
 ms.assetid: 1e23a8e6-97fa-47f5-a279-b52aa2efafa4
-
 ---
 # C26474 NO_IMPLICIT_CAST
 
 "Don't cast between pointer types when the conversion could be implicit."
 
-**C++ Core Guidelines**:
+**C++ Core Guidelines**:\
 Type.1: Avoid casts
 
-In some cases, implicit casts between pointer types can safely be done and don’t require user to write specific cast expression. This rule finds instances of such unnecessary casting which can be removed.
+In some cases, implicit casts between pointer types are safe and don't require you to write a specific cast expression. This rule finds instances of unnecessary casts you can safely remove.
 
 ## Remarks
 
-- The rule ID is a bit misleading: it should be interpreted as "implicit cast is not used where it is acceptable".
-  - The rule is applicable to pointers only and checks static casts and reinterpret casts.
-  - The following cases are acceptable pointer conversions that should not use explicit cast expressions:
-    - conversion to nullptr_t;
-    - conversion to void*;
-    - conversion from a derived type to its base when invoking a base member function that is not hidden by the derived type. 
+The rule ID should be interpreted as "An implicit cast isn't used where it's acceptable."
+
+This rule is only applicable to pointers. It checks static casts and reinterpret casts.
+
+These cases are acceptable pointer conversions that shouldn't use explicit cast expressions:
+- conversion to `nullptr_t`;
+- conversion to `void*`;
+- conversion from a derived type to its base when invoking a base member function that's not hidden by the derived type. 
 
 ## Example 1
 
-unnecessary conversion hides logic error
+An unnecessary conversion hides a logic error in this example:
 
 ```cpp
 template<class T>
 bool register_buffer(T buffer) {
     auto p = reinterpret_cast<void*>(buffer); // C26474, also 26490 NO_REINTERPRET_CAST
+    // To fix, declare buffer as T*, and use this to define p:
+    // auto p = buffer;
     return buffers_.insert(p).second;
 }
 
@@ -47,35 +50,26 @@ void merge_bytes(std::uint8_t *left, std::uint8_t *right)
 }
 ```
 
-unnecessary conversion hides logic error - reworked
+## Example 2
 
-```cpp
-// ...
-template<class T>
-bool register_buffer(T *buffer) {
-    auto p = buffer;
-    return buffers_.insert(p).second;
-}
-// ...
-```
+This example demonstrates using casts to access base-class member functions:
 
-## Example 2
-Using casts to access base-class member functions
 ```cpp
 struct struct_1
 {
-  void foo();
-  void bar();
+    void foo();
+    void bar();
 };
+
 struct struct_2 : struct_1
 {
-  void foo(); // this definition hides struct_1::foo
+    void foo(); // this definition hides struct_1::foo
 };
 
 void fn(struct_2* ps2)
 {
-  static_cast<struct_1*>(ps2)->foo(); // this cast is necessary to access `struct_1::foo`
-                                      // alternatively ps2->struct_1::foo();
-  static_cast<struct_1*>(ps2)->bar(); // this cast is unnecessary and can be done implicitly
+    static_cast<struct_1*>(ps2)->foo(); // This cast is necessary to access struct_1::foo
+                                        // Alternatively, use ps2->struct_1::foo();
+    static_cast<struct_1*>(ps2)->bar(); // This cast is unnecessary and can be done implicitly
 }
 ```
diff --git a/docs/overview/what-s-new-for-visual-cpp-in-visual-studio.md b/docs/overview/what-s-new-for-visual-cpp-in-visual-studio.md
@@ -631,7 +631,7 @@ The Desktop Bridge infrastructure lets you package your existing desktop applica
 
 A **Windows Application Packaging Project** project template is added, which greatly simplifies packaging of desktop applications with Desktop Bridge. It's available under **File | New | Project | Installed | Visual C++ | Universal Windows Platform**. For more information, see [Package an app by using Visual Studio (Desktop Bridge)](/windows/uwp/porting/desktop-to-uwp-packaging-dot-net).
 
-When writing new code, you can now use C++/WinRT, a standard C++ language projection for the Windows Runtime implemented solely in header files. It allows you to consume and author Windows Runtime APIs using any standards-compliant C++ compiler. C++/WinRT is designed to provide C++ developers with first-class access to the modern Windows API. For more information, see [C++/WinRT: Modern C++ for the Windows Runtime](https://moderncpp.com/).
+When writing new code, you can now use C++/WinRT, a standard C++ language projection for the Windows Runtime implemented solely in header files. It allows you to consume and author Windows Runtime APIs using any standards-compliant C++ compiler. C++/WinRT is designed to provide C++ developers with first-class access to the modern Windows API. For more information, see [C++/WinRT](/windows/uwp/cpp-and-winrt-apis/).
 
 Starting in build 17025 of the Windows SDK Insider Preview, C++/WinRT is included in the Windows SDK. For more information, see [C++/WinRT is now included the Windows SDK](https://devblogs.microsoft.com/cppblog/cppwinrt-is-now-included-the-windows-sdk/).
 
