Merge pull request #4450 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch master)

Author: gewarren

.markdownlint.json

@@ -9,7 +9,6 @@
     "MD007": false,
     "MD009": false,
     "MD011": false,
-    "MD012": false,
     "MD013": false,
     "MD019": false,
     "MD020": false,

docs/azure/includes/storage-try-azure-tools.md

@@ -5,4 +5,3 @@
 > [Microsoft Azure Storage Explorer](/azure/vs-azure-tools-storage-manage-with-storage-explorer) is a free, standalone app from Microsoft. You can use it to work visually with Azure Storage data on Windows, macOS, and Linux.
 > 
 > 
-

docs/azure/vs-azure-tools-multiple-services-project-configurations.md

@@ -23,7 +23,6 @@ Configuration settings are managed and modified in Visual Studio using property
 
 For information about the underlying schemas for the service definition and service configuration files, see the [.csdef XML Schema](/azure/cloud-services/schema-csdef-file) and [.cscfg XML Schema](/azure/cloud-services/schema-cscfg-file) articles. For more information about service configuration, see [How to Configure Cloud Services](/azure/cloud-services/cloud-services-how-to-configure-portal).
 
-
 ## Configuration page
 
 ### Service Configuration

docs/azure/vs-azure-tools-publish-webapplicationwebsite-windows-powershell-script.md

@@ -22,7 +22,6 @@ Publishes a web project to an Azure website. The script creates the required res
     -SendHostMessagesToOutput
     -Verbose
 
-
 ## Configuration
 The path to the JSON configuration file that describes the details of the deployment.
 

docs/code-quality/C26401.md

@@ -16,5 +16,4 @@ ms.workload:
 # C26401 DONT_DELETE_NON_OWNER
 This check detects places where moving to `owner<T>` can be a good option for the first stage of refactoring. Like C26400 it enforces rules I.11 and R.3, but focuses on the "release" portion of the pointer lifetime. It warns on any call to operator `delete` if its target is neither an `owner<T>` nor an implicitly assumed owner. For more information, see [C26400](c26400.md) regarding the auto declarations. This does include expressions that refer to global variables, formals, and so on.
 
-
 Warnings C26400 and C26401 always occur with [C26409](c26409.md), but they are more appropriate for scenarios where immediate migration to smart pointers is not feasible. In such cases the `owner<T>` concept can be adopted first and C26409 may be temporarily suppressed.

docs/code-quality/C26402.md

@@ -16,5 +16,4 @@ ms.workload:
 # C26401 DONT_DELETE_NON_OWNER
 This check detects places where moving to `owner<T>` can be a good option for the first stage of refactoring. Like C26400 it enforces rules I.11 and R.3, but focuses on the "release" portion of the pointer lifetime. It warns on any call to operator `delete` if its target is neither an `owner<T>` nor an implicitly assumed owner. For more information, see [C26400](c26400.md) regarding the auto declarations. This does include expressions that refer to global variables, formals, and so on.
 
-
 Warnings C26400 and C26401 always occur with [C26409](c26409.md), but they are more appropriate for scenarios where immediate migration to smart pointers is not feasible. In such cases the `owner<T>` concept can be adopted first and C26409 may be temporarily suppressed.

docs/code-quality/annotating-locking-behavior.md

@@ -99,7 +99,6 @@ To avoid concurrency bugs in your multithreaded program, always follow an approp
 |`_Interlocked_operand_`|The annotated function parameter is the target operand of one of the various Interlocked functions.  Those operands must have specific additional properties.|
 |`_Write_guarded_by_(expr)`|Annotates a variable and indicates that whenever the variable is modified, the lock count of the lock object that's named by `expr` is at least one.|
 
-
 ## Smart Lock and RAII Annotations
  Smart locks typically wrap native locks and manage their lifetime. The following table lists annotations that can be used with smart locks and RAII coding patterns with support for `move` semantics.
 

docs/code-quality/c26446.md

@@ -22,7 +22,6 @@ The Bounds profile of the C++ Core Guidelines tries to eliminate unsafe manipula
 
 This rule helps to find places where potentially unchecked access is performed via calls to operator\[](). In most cases such calls can be easily replaced by `gsl::at()`.
 
-
 - Access to arrays with known size is flagged when non-constant index is used in a subscript operator. Constant indices are handled by [C26483 STATIC_INDEX_OUT_OF_RANGE](c26483.md).
 - The logic to warn on overloaded operator[] calls is more complex:
   - If index is non-integral, the call is ignored. This also handles indexing in standard maps since parameters in such operators are passed by reference.

docs/code-quality/ca2000-dispose-objects-before-losing-scope.md

@@ -142,7 +142,6 @@ Public Function OpenPort2(ByVal PortName As String) As SerialPort
          tempPort.Close()
       End If
 
-
    End Try
 
    Return port

docs/code-quality/code-analysis-for-cpp-corecheck.md

@@ -135,15 +135,12 @@ Function '%symbol%' should be marked with 'override'. See [C.128: Virtual functi
 [C26435 SINGLE_VIRTUAL_SPECIFICATION](c26435.md)
 Function '%symbol%' should specify exactly one of 'virtual', 'override', or 'final'. See [C.128: Virtual functions should specify exactly one of virtual, override, or final](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md).
 
-
 [C26436 NEED_VIRTUAL_DTOR](C26436.md)
   The type '%symbol%' with a virtual function needs either public virtual or protected nonvirtual destructor. See [C++ Core Guidelines C.35](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#c35-a-base-class-destructor-should-be-either-public-and-virtual-or-protected-and-nonvirtual).
 
-
 [C26443 NO_EXPLICIT_DTOR_OVERRIDE](c26443.md)
 Overriding destructor should not use explicit 'override' or 'virtual' specifiers. See [C.128: Virtual functions should specify exactly one of virtual, override, or final](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md).
 
-
 ## TYPE Group
 
 [C26437 DONT_SLICE](C26437.md)
@@ -271,7 +268,6 @@ Consider using `gsl::finally` if final action is intended. See [C++ Core Guideli
 `gsl::span` or `std::string_view` created from a temporary will be invalid when the temporary is invalidated. See
 [C++ Core Guidelines: GSL.view: Views](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#gslview-views).
 
-
 ## Deprecated Warnings
 
 The following warnings are present in an early experimental rule set of the core guidelines checker, but are now deprecated and can be safely ignored. The warnings are superceded by warnings from the list above.

docs/code-quality/cpp-core-guidelines-warnings.md

@@ -90,7 +90,6 @@ As new rules are added to the C++ Core Guidelines Checker, the number of warning
 
   - **Type Rules** enforce the [Type profile of the C++ Core Guidelines](http://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#prosafety-type-safety-profile).
 
-
 You can choose to limit warnings to just one or a few of the groups. The **Native Minimum** and **Native Recommended** rule sets include C++ Core Check rules in addition to other PREfast checks. To see the available rule sets, open the Project Properties dialog, select **Code Analysis\General**, open the dropdown in the **Rule Sets** combo-box, and pick **Choose multiple rule sets**. For more information about using Rule Sets in Visual Studio, see [Using Rule Sets to Group Code Analysis Rules](using-rule-sets-to-group-code-analysis-rules.md).
 
 ## Macros

docs/data-tools/working-with-a-conceptual-model-wcf-data-services.md

@@ -19,7 +19,6 @@ When you use a conceptual model to describe the data in a database, you can quer
 
  You can use conceptual models with WCF Data Services applications. The following topics show how to query data through a conceptual model.
 
-
 | Topic | Description |
 | - | - |
 | [How to: Execute Data Service queries](/dotnet/framework/data/wcf/how-to-execute-data-service-queries-wcf-data-services) | Shows how to query a data service from a [!INCLUDE[dnprdnshort](../code-quality/includes/dnprdnshort_md.md)] application. |

docs/debugger/c-cpp-assertions.md

@@ -100,7 +100,6 @@ VERIFY ( myFnctn(0)==1 ) // safe
 ## <a name="BKMK_CRT_assertions"></a> CRT assertions
 The CRTDBG.H header file defines the [_ASSERT and _ASSERTE macros](/cpp/c-runtime-library/reference/assert-asserte-assert-expr-macros) for assertion checking.
 
-
 | Macro | Result |
 |------------| - |
 | `_ASSERT` | If the specified expression evaluates to FALSE, the file name and line number of the `_ASSERT`. |

docs/debugger/create-custom-views-of-native-objects.md

@@ -148,7 +148,6 @@ You can define different Natvis views to display types in different ways. For ex
 </Type>
 ```
 
-
 In the **Watch** window, use the **,view** format specifier to specify an alternate view. The simple view appears as **vec,view(simple)**:
 
 ![Watch window with simple view](../debugger/media/watch-simpleview.png "Watch window with simple view")

docs/debugger/debugging-windows-store-and-windows-universal-apps.md

@@ -24,6 +24,5 @@ The Visual Studio debugger provides complete support for debugging UWP apps. See
 |Debug deployed apps, both local and remote.|[Debug an installed app package](../debugger/debug-installed-app-package.md)|
 |Analyze the effect of the ContentPrefetcher class on UWP apps.|[Prefetch content for UWP apps](../debugger/prefetch-content-for-windows-store-apps.md)|
 
-
 ## See Also
 - [Analyze code quality using static code analysis](/visualstudio/code-quality/code-analysis-for-managed-code-overview)

docs/debugger/diagnose-problems-after-deployment.md

@@ -40,7 +40,6 @@ Visual Studio 2017 and later versions do not include the *BuildInfo.config* file
 
 * If you need to use IntelliTrace, open the project in Visual Studio and load the symbol files from the matching build. You can load symbol files from the **Modules** window or by configuring symbols in **Tools** > **Options** > **Debugging** > **Symbols**.
 
-
 ####  <a name="TFS2013"></a> Team Foundation Server 2013
  Set up your build pipeline to add the locations of your source, build, and symbols to the build manifest (BuildInfo.config file). Team Foundation Build automatically creates this file and puts it in your project's output folder.
 

docs/debugger/graphics/graphics-event-list.md

@@ -101,7 +101,6 @@ Visual Studio 2017 and greater contain the **Resource History** window.  Selecti
 
 This window allows you to view the history of the selected item in the event list.  The dropdown at the top can be used to select other items to view the history of.  The top half of the window contains the **Frame Setup Events**.  These are the events which fall into the *Create* type category and are calls that typically initialize and create the resource.  The bottom half of the window contains the **Frame Events** section.  These are the normal read and write events that occur during the usage of the resource.
 
-
 | Column | Description |
 |-----------| - |
 | **Type** | Shows the type of the entry, typically *Create*, *Read* and *Write*. |

docs/debugger/graphics/graphics-frame-validation.md

@@ -19,7 +19,6 @@ Visual Studio 2017 and greater support the **Frame Validation** tool.  The Frame
 
 Click the **Run Validation** button at the top left corner to initiate the analysis.  It may take several minutes to complete depending on the complexity of the frame.  The data which appears here is a combination from two sources: the messages that D3D itself emits when [SDK Layers](/windows/desktop/direct3d11/overviews-direct3d-11-devices-layers) is enabled, and data that is collected from the tool's own internal state tracking. Once complete, you will see several columns of data:
 
-
 | **Column** | **Description** |
 |------------| - |
 | Event Id | ID which maps to an entry in the [Event List](graphics-event-list.md) window. |

docs/debugger/graphics/graphics-log-document.md

@@ -99,7 +99,6 @@ The Graphics Log document is the record of graphics events that occurred while y
  **VSG Log File**
  Lists information about the graphics log document.
 
-
 | Property | Description |
 |------------------------| - |
 | **Created by** | The name of the app that created the graphics log document. For example, if the capture session was initiated from [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] (manual capture) the value of this property is [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)]. |

docs/debugger/how-to-debug-on-a-high-performance-cluster.md

@@ -90,7 +90,6 @@ Debugging a multiprocessing program on a high-performance cluster is like debugg
 
 `(MachineName = marvin) & (ThreadName = fourier1)`
 
-
 ## See Also
 - [Debug Multithreaded Applications](../debugger/debug-multithreaded-applications-in-visual-studio.md)
 - [Remote Debugging](../debugger/remote-debugging.md)

docs/debugger/keyboard-shortcuts-html-and-javascript.md

@@ -23,7 +23,6 @@ ms.workload:
  Keyboard shortcuts in Visual Studio for debugging UWP apps using HTML and JavaScript.
 ::: moniker-end
 
-
 ## General shortcuts
 
  These shortcuts work across all tools for UWP apps using HTML and JavaScript.

docs/debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md

@@ -254,7 +254,6 @@ You can specify the locations the debugger searches for source files, and exclud
 
 1. Select **OK** or **Apply**.
 
-
 ## See also
 - [Understand symbol files and Visual Studio symbol settings](https://devblogs.microsoft.com/devops/understanding-symbol-files-and-visual-studios-symbol-settings/)
 

docs/debugger/start-a-debugging-session-for-a-store-app-in-visual-studio-vb-csharp-cpp-and-xaml.md

@@ -117,7 +117,6 @@ In C++ apps, Visual Studio debugs native code by default. You can choose to debu
 |**Native with Script**|Debug native C/C++ code and JavaScript code in your app. Managed code is ignored. Available in C++ projects or background tasks only.|
 |**GPU only (C++ AMP)**|Debug native C++ code that runs on a graphics processing unit (GPU). Available in C++ projects only.|
 
-
 ###  <a name="BKMK__Optional__Disable_network_loopbacks"></a> Disable network loopbacks (optional)
 
  For security, a UWP app that is installed in the standard manner can't make network calls to the device it's installed on. Visual Studio exempts deployed apps from this rule by default, so you can test communication procedures on a single machine. Before you release your app, you should test your app without the exemption.

docs/debugger/unable-to-connect-to-the-microsoft-visual-studio-remote-debugging-monitor.md

@@ -75,7 +75,6 @@ Visual Studio could not connect to the remote debugger. This message may occur f
 
 - The remote debugger version does not match Visual Studio. To get the correct version of the remote debugger, see [Remote Debugging](../debugger/remote-debugging.md)
 
-
 ## <a name="valid_name"></a> The requested name was valid, but no data of the requested type was found
 
 The remote computer exists, but Visual Studio could not connect to the remote debugger. This message may occur for several reasons:

docs/debugger/where-can-i-look-up-win32-error-codes-q.md

@@ -26,7 +26,6 @@ WINERROR.H in the INCLUDE directory of your default system installation contains
 
 `0x80000004,hr`
 
-
 ## See Also
 - [Debugging Native Code FAQs](../debugger/debugging-native-code-faqs.md)
 - [Debugging Native Code](../debugger/debugging-native-code.md)

docs/deployment/application-deployment-prerequisites.md

@@ -65,7 +65,6 @@ To have your application to install and run successfully, first install all comp
 
  If you change any bootstrapper options, you must change the unsigned bootstrapper and then later sign the bootstrapper file.
 
-
 | Command-line argument | Description |
 | - | - |
 | **-?, -h, -help** | Displays a Help dialog box. |

docs/deployment/clickonce-application-manifest.md

@@ -21,7 +21,6 @@ A [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application
 
 [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application manifests have the following elements and attributes.
 
-
 | Element | Description | Attributes |
 | - | - | - |
 | [\<assembly> Element](../deployment/assembly-element-clickonce-application.md) | Required. Top-level element. | `manifestVersion` |

docs/deployment/clickonce-deployment-manifest.md

@@ -21,7 +21,6 @@ A deployment manifest is an XML file that describes a [!INCLUDE[ndptecclick](../
 
  Deployment manifests have the following elements and attributes.
 
-
 | Element | Description | Attributes |
 | - | - | - |
 | [\<assembly> Element](../deployment/assembly-element-clickonce-deployment.md) | Required. Top-level element. | `manifestVersion` |

docs/deployment/dependency-element-clickonce-application.md

@@ -116,7 +116,6 @@ Identifies a platform or assembly dependency that is required for the applicatio
 
  `dependentAssembly` has the following attributes.
 
-
 | Attribute | Description |
 |-----------------------| - |
 | `dependencyType` | Required. Specifies the dependency type. Valid values are `preprequisite` and `install`. An `install` assembly is installed as part of the [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application. A `prerequisite` assembly must be present in the global assembly cache (GAC) before the [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application can install. |
@@ -147,15 +146,13 @@ Identifies a platform or assembly dependency that is required for the applicatio
 ### dsig:Transform
  The `dsig:Transform` element is a required child of the `dsig:Transforms` element. The `dsig:Transform` element has the following attributes.
 
-
 | Attribute | Description |
 |-------------| - |
 | `Algorithm` | The algorithm used to calculate the digest for this file. Currently the only value used by [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] is `urn:schemas-microsoft-com:HashTransforms.Identity`. |
 
 ### dsig:DigestMethod
  The `dsig:DigestMethod` element is a required child of the `hash` element. The `dsig:DigestMethod` element has the following attributes.
 
-
 | Attribute | Description |
 |-------------| - |
 | `Algorithm` | The algorithm used to calculate the digest for this file. Currently the only value used by [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] is `http://www.w3.org/2000/09/xmldsig#sha1`. |

docs/deployment/dependency-element-clickonce-deployment.md

@@ -72,7 +72,6 @@ Identifies the version of the application to install, and the location of the ap
 ## dependentAssembly
  Required. This element contains the `assemblyIdentity` element. The following table shows the attributes the `dependentAssembly` supports.
 
-
 | Attribute | Description |
 |------------------| - |
 | `preRequisite` | Optional. Specifies that this assembly should already exist in the GAC. Valid values are `true` and `false`. If `true`, and the specified assembly does not exist in the GAC, the application fails to run. |
@@ -104,15 +103,13 @@ Identifies the version of the application to install, and the location of the ap
 ## dsig:Transform
  The `dsig:Transform` element is a required child of the `dsig:Transforms` element. The following table shows the attributes of the `dsig:Transform` element.
 
-
 | Attribute | Description |
 |-------------| - |
 | `Algorithm` | The algorithm used to calculate the digest for this file. Currently the only value used by [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] is `urn:schemas-microsoft-com:HashTransforms.Identity`. |
 
 ## dsig:DigestMethod
  The `dsig:DigestMethod` element is a required child of the `hash` element. The following table shows the attributes of the `dsig:DigestMethod` element.
 
-
 | Attribute | Description |
 |-------------| - |
 | `Algorithm` | The algorithm used to calculate the digest for this file. Currently the only value used by [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] is `http://www.w3.org/2000/09/xmldsig#sha1`. |

docs/deployment/deploying-prerequisites-for-64-bit-applications.md

@@ -27,7 +27,6 @@ ClickOnce deployment supports the installation of applications on 64-bit platfor
 
  If you select a prerequisite that does not have 64-bit components, you may see a warning stating that the selected packages are not available for the 64-bit platform.
 
-
 | Redistributable | x64 support | IA64 support |
 | - |-------------|--------------|
 | [!INCLUDE[vsto_runtime](../deployment/includes/vsto_runtime_md.md)] | Yes | No |

docs/deployment/deployment-element-clickonce-deployment.md

@@ -54,7 +54,6 @@ Identifies the attributes used for the deployment of updates and exposure to the
 ## Elements and attributes
  The `deployment` element is required and is in the `urn:schemas-microsoft-com:asm.v1` namespace. The element has the following attributes.
 
-
 | Attribute | Description |
 |--------------------------| - |
 | `install` | Required. Specifies whether this application defines a presence on the Windows **Start** menu and in the Control Panel **Add or Remove Programs** application. Valid values are `true` and `false`. If `false`, [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] will always run the latest version of this application from the network, and will not recognize the `subscription` element. |
@@ -91,7 +90,6 @@ Identifies the attributes used for the deployment of updates and exposure to the
 
  This element is a child of the `deployment` element and has the following attribute.
 
-
 | Attribute | Description |
 |------------| - |
 | `codebase` | Required. Identifies the location, as a Uniform Resource Identifier (URI), of the deployment manifest that is used to update the [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application. This element also allows for forwarding update locations for CD-based installations. Must be a valid URI. |