Merge pull request #12856 from MicrosoftDocs/repo_sync_working_branch

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

Author: Albertyang0

docs/data-tools/query-datasets.md

@@ -87,7 +87,7 @@ The following code examples demonstrate how to navigate up and down relationship
 
 - An `Orders` table.
 
-- A relationship named `FK_Orders_Customers`relating the two tables.
+- A relationship named `FK_Orders_Customers` relating the two tables.
 
 Additionally, both tables need to be filled with data for any records to be returned.
 

docs/data-tools/update-data-by-using-a-tableadapter.md

@@ -42,7 +42,7 @@ Call the `Update` method of a TableAdapter. Pass the name of the data table that
 
 ### To update a database by using a TableAdapter
 
-- Enclose the TableAdapter's`Update` method in a `try`/`catch` block. The following example shows how to update the contents of the `Customers` table in `NorthwindDataSet` from within a `try`/`catch` block .
+- Enclose the TableAdapter's `Update` method in a `try`/`catch` block. The following example shows how to update the contents of the `Customers` table in `NorthwindDataSet` from within a `try`/`catch` block.
 
      ### [C#](#tab/csharp)
      :::code language="csharp" source="../snippets/csharp/VS_Snippets_VBCSharp/VbRaddataSaving/CS/Form3.cs" id="Snippet9":::

docs/debugger/debug-interface-access/lexical-hierarchy-of-symbol-types.md

@@ -1,6 +1,6 @@
 ---
-description: "The following table shows the symbol types in the lexical hierarchy."
 title: "Lexical Hierarchy of Symbol Types"
+description: "The following table shows the symbol types in the lexical hierarchy."
 ms.date: "11/04/2016"
 ms.topic: "reference"
 dev_langs:
@@ -34,7 +34,7 @@ The following table shows the symbol types in the lexical hierarchy.
 |[Label (Debug Interface Access SDK)](../../debugger/debug-interface-access/label-debug-interface-access-sdk.md)|Specifies a location in program code.|
 |[PublicSymbol](../../debugger/debug-interface-access/publicsymbol.md)|Specifies an external symbol that appears when building the executable program.|
 |[Thunk](../../debugger/debug-interface-access/thunk.md)|Specifies a `thunk`.|
-|[UsingNameSpace](../../debugger/debug-interface-access/usingnamespace.md)|Specifies a `namespace`identifier.|
+|[UsingNameSpace](../../debugger/debug-interface-access/usingnamespace.md)|Specifies a `namespace` identifier.|
 
 > [!NOTE]
 > Additional symbol properties may be available depending on the symbol type. These properties are listed in the individual symbol topics.

docs/deployment/localizing-clickonce-applications.md

@@ -56,7 +56,7 @@ Localization is the process of making your application appropriate for a specifi
 
  You can accomplish the same thing by using the *MageUI.exe* tool in the Microsoft Windows Software Development Kit (SDK). Use the **Populate** button on the **Files** tab of your application manifest to exclude all other satellite assemblies from the application directory, and then set the **Culture** field on the **Name** tab for your deployment manifest in *MageUI.exe*. These steps not only include the correct satellite assembly, but they also set the `language` attribute on the `assemblyIdentity` element in your deployment manifest to the corresponding culture.
 
- After publishing the application, you must repeat this step for each additional culture your application supports. You must make sure that you publish to a different Web server directory or file share directory every time, because each application manifest will reference a different satellite assembly, and each deployment manifest will have a different value for the `language`attribute.
+ After publishing the application, you must repeat this step for each additional culture your application supports. You must make sure that you publish to a different Web server directory or file share directory every time, because each application manifest will reference a different satellite assembly, and each deployment manifest will have a different value for the `language` attribute.
 
 ## Download satellite assemblies on demand
  If you decide to include all satellite assemblies in a single deployment, you can improve performance by using on-demand downloading, which enables you to mark assemblies as optional. The marked assemblies will not be downloaded when the application is installed or updated. You can install the assemblies when you need them by calling the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> method on the <xref:System.Deployment.Application.ApplicationDeployment> class.

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

@@ -67,7 +67,7 @@ Describes the minimum security permissions required for the application to run o
  Required. This element is a child of the `trustInfo` element. It contains the `applicationRequestMinimum` element and has no attributes.
 
 ## applicationRequestMinimum
- Required. This element is a child of the `security` element and contains the `PermissionSet`, `assemblyRequest`, and `defaultAssemblyRequest`elements. This element has no attributes.
+ Required. This element is a child of the `security` element and contains the `PermissionSet`, `assemblyRequest`, and `defaultAssemblyRequest` elements. This element has no attributes.
 
 ## PermissionSet
  Required. This element is a child of the `applicationRequestMinimum` element and contains the `IPermission` element. This element has the following attributes.

docs/deployment/walkthrough-downloading-assemblies-on-demand-with-the-clickonce-deployment-api.md

@@ -89,7 +89,7 @@ By default, all of the assemblies included in a ClickOnce application are downlo
 
 10. In the code, locate the call to <xref:System.Reflection.Assembly.LoadFile%2A>.
 
-11. Set`PublicKeyToken` to the value that you retrieved earlier.
+11. Set `PublicKeyToken` to the value that you retrieved earlier.
 
 12. Save the file as either *Form1.cs* or *Form1.vb*.
 

docs/extensibility/debugger/evaluating-a-watch-window-expression.md

@@ -27,7 +27,7 @@ ms.subservice: debug-diagnostics
 
 3. `IDebugExpressionContext2::ParseText` calls [Parse](../../extensibility/debugger/reference/idebugexpressionevaluator-parse.md) to do the actual work of parsing the text and produce an [IDebugParsedExpression](../../extensibility/debugger/reference/idebugparsedexpression.md) object.
 
-4. `IDebugExpressionContext2::ParseText` creates an [IDebugExpression2](../../extensibility/debugger/reference/idebugexpression2.md) object and puts the `IDebugParsedExpression` object into it. This I`DebugExpression2` object is then returned to Visual Studio.
+4. `IDebugExpressionContext2::ParseText` creates an [IDebugExpression2](../../extensibility/debugger/reference/idebugexpression2.md) object and puts the `IDebugParsedExpression` object into it. This `IDebugExpression2` object is then returned to Visual Studio.
 
 5. Visual Studio calls [EvaluateSync](../../extensibility/debugger/reference/idebugexpression2-evaluatesync.md) to evaluate the parsed expression.
 

docs/extensibility/debugger/reference/const-guid-array.md

@@ -1,6 +1,6 @@
 ---
-description: "A structure that holds a list of GUID`s."
 title: CONST_GUID_ARRAY
+description: "A structure that holds a list of `GUID`s."
 ms.date: 11/04/2016
 ms.topic: reference
 f1_keywords:

docs/extensibility/debugger/reference/field-kind.md

@@ -1,6 +1,6 @@
 ---
-description: "Specifies the kind of field contained in an IDebugField object."
 title: FIELD_KIND
+description: "Specifies the kind of field contained in an IDebugField object."
 ms.date: 11/04/2016
 ms.topic: reference
 f1_keywords:
@@ -223,7 +223,7 @@ Indicates a mask for symbol information.
 ## Remarks
 Returned from a call to the [GetKind](../../../extensibility/debugger/reference/idebugfield-getkind.md) method.
 
-Depending on the kind of field, [QueryInterface](/cpp/atl/queryinterface) can be called on the [IDebugField](../../../extensibility/debugger/reference/idebugfield.md) interface for a more specific form of interface. For example, if [GetKind](../../../extensibility/debugger/reference/idebugfield-getkind.md) returns `FIELD_TYPE_METHOD`, you can then call `QueryInterface` on I`DebugField` to obtain the [IDebugMethodField](../../../extensibility/debugger/reference/idebugmethodfield.md) interface.
+Depending on the kind of field, [QueryInterface](/cpp/atl/queryinterface) can be called on the [IDebugField](../../../extensibility/debugger/reference/idebugfield.md) interface for a more specific form of interface. For example, if [GetKind](../../../extensibility/debugger/reference/idebugfield-getkind.md) returns `FIELD_TYPE_METHOD`, you can then call `QueryInterface` on `IDebugField` to obtain the [IDebugMethodField](../../../extensibility/debugger/reference/idebugmethodfield.md) interface.
 
 ## Requirements
 Header: sh.h

docs/extensibility/error-handling-and-return-values.md

@@ -43,7 +43,7 @@ VSPackages and COM use the same architecture for errors. The `SetErrorInfo` and
 
 - Any party that explicitly ignores an error `HRESULT` must call the <xref:Microsoft.VisualStudio.Shell.Interop.IVsUIShell.SetErrorInfo%2A> method with <xref:Microsoft.VisualStudio.VSConstants.S_OK>. Otherwise, the `ErrorInfo` object might be accidentally used when another party generates an error without providing their own `ErrorInfo`.
 
-- All methods that originate an error `HRESULT` are encouraged to call the <xref:Microsoft.VisualStudio.Shell.Interop.IVsUIShell.SetErrorInfo%2A> method to provide rich error information. If the returned `HRESULT` is a special `FACILITY_ITF` error, then the method is required to provide a proper `ErrorInfo`object. If the returned error is a standard system error (for example, <xref:Microsoft.VisualStudio.VSConstants.E_OUTOFMEMORY>, <xref:Microsoft.VisualStudio.VSConstants.E_ABORT>, <xref:Microsoft.VisualStudio.VSConstants.E_INVALIDARG>, <xref:Microsoft.VisualStudio.VSConstants.E_UNEXPECTED>, and so on.) it is acceptable to return the error code without explicitly calling the <xref:Microsoft.VisualStudio.Shell.Interop.IVsUIShell.SetErrorInfo%2A> method. As a defensive coding strategy, when originating an error `HRESULT` (including system errors), always call the <xref:Microsoft.VisualStudio.Shell.Interop.IVsUIShell.SetErrorInfo%2A> method, either with `ErrorInfo` describing the failure in greater detail, or `null`.
+- All methods that originate an error `HRESULT` are encouraged to call the <xref:Microsoft.VisualStudio.Shell.Interop.IVsUIShell.SetErrorInfo%2A> method to provide rich error information. If the returned `HRESULT` is a special `FACILITY_ITF` error, then the method is required to provide a proper `ErrorInfo` object. If the returned error is a standard system error (for example, <xref:Microsoft.VisualStudio.VSConstants.E_OUTOFMEMORY>, <xref:Microsoft.VisualStudio.VSConstants.E_ABORT>, <xref:Microsoft.VisualStudio.VSConstants.E_INVALIDARG>, <xref:Microsoft.VisualStudio.VSConstants.E_UNEXPECTED>, and so on.) it is acceptable to return the error code without explicitly calling the <xref:Microsoft.VisualStudio.Shell.Interop.IVsUIShell.SetErrorInfo%2A> method. As a defensive coding strategy, when originating an error `HRESULT` (including system errors), always call the <xref:Microsoft.VisualStudio.Shell.Interop.IVsUIShell.SetErrorInfo%2A> method, either with `ErrorInfo` describing the failure in greater detail, or `null`.
 
 - All functions that return an error originated by another call must pass on the information that was received from the failing call in the `HRESULT` without modifying the `ErrorInfo` object.
 

docs/extensibility/internals/project-configuration-object.md

@@ -33,7 +33,7 @@ The Project Configuration Provider manages the project configurations. The envir
 > [!NOTE]
 > Since Visual Studio is no longer limited to two configuration types, code that processes configurations should not be written with assumptions about the number of configurations, nor should it be written with the assumption that a project that has only one configuration is necessarily either Debug or Retail. This makes the use of <xref:Microsoft.VisualStudio.Shell.Interop.IVsCfg.get_IsReleaseOnly%2A> and <xref:Microsoft.VisualStudio.Shell.Interop.IVsCfg.get_IsDebugOnly%2A> obsolete.
 
- Calling `QueryInterface` on the object returned from`IVsGetCfgProvider::GetCfgProvider` retrieves `IVsCfgProvider2`. If `IVsGetCfgProvider` is not found by calling `QueryInterface` on the `IVsProject3` project object, you can access the configuration provider object by calling `QueryInterface` on the hierarchy root browser object for the object returned for `IVsHierarchy::GetProperty(VSITEM_ROOT, VSHPROPID_BrowseObject)`, or through a pointer to the configuration provider returned for `IVsHierarchy::GetProperty(VSITEM_ROOT, VSHPROPID_ConfigurationProvider)`.
+ Calling `QueryInterface` on the object returned from `IVsGetCfgProvider::GetCfgProvider` retrieves `IVsCfgProvider2`. If `IVsGetCfgProvider` is not found by calling `QueryInterface` on the `IVsProject3` project object, you can access the configuration provider object by calling `QueryInterface` on the hierarchy root browser object for the object returned for `IVsHierarchy::GetProperty(VSITEM_ROOT, VSHPROPID_BrowseObject)`, or through a pointer to the configuration provider returned for `IVsHierarchy::GetProperty(VSITEM_ROOT, VSHPROPID_ConfigurationProvider)`.
 
  `IVsProjectCfg2` primarily provides access to build, debug and deployment management objects and allows projects the freedom to group outputs. The methods of `IVsProjectCfg` and `IVsProjectCfg2` can be used to implement <xref:Microsoft.VisualStudio.Shell.Interop.IVsBuildableProjectCfg> to manage the build process, and <xref:Microsoft.VisualStudio.Shell.Interop.IVsOutputGroup> pointers for the output groups of a configuration.
 

docs/extensibility/internals/property-pages.md

@@ -47,7 +47,7 @@ Users can view and change project configuration-dependent and -independent prope
 
   Implementing `Help::DisplayTopicFromF1Keyword` in your VSPackage provides the functionality for the Help button.
 
-  For further information, see `IDispatch` and `ISpecifyPropertyPages`in the MSDN library.
+  For further information, see `IDispatch` and `ISpecifyPropertyPages` in the MSDN library.
 
   The second type of property pages displayed in the samples hosts a form of the properties grid, as shown in the following screenshot.
 

docs/extensibility/sccaddfromscc-function.md

@@ -1,6 +1,6 @@
 ---
-description: "This function allows the user to browse for files that are already in the source control system and subsequently make those files part of the current project."
 title: SccAddFromScc Function
+description: "This function allows the user to browse for files that are already in the source control system and subsequently make those files part of the current project."
 ms.date: 11/04/2016
 ms.topic: reference
 f1_keywords:
@@ -63,7 +63,7 @@ SCCRTN SccAddFromScc (
  `lplpFileNames` is a `char ***` pointer. The source control plug-in places a pointer to an array of pointers to file names, thus passing the list in the standard way for this API.
 
 > [!NOTE]
-> Initial versions of the VSSCI API did not provide a way to indicate the target project for the added files. To accommodate this, the semantics of the `lplpFIleNames` parameter have been enhanced to make it an in/out parameter rather than an output parameter. If only a single file is specified, that is, the value pointed to by `lpnFiles` = 1, then the first element of `lplpFileNames` contains the target folder. To use these new semantics, the IDE calls the `SccSetOption` function with the `nOption`parameter set to `SCC_OPT_SHARESUBPROJ`. If a source control plug-in does not support the semantics, it returns `SCC_E_OPTNOTSUPPORTED`. Doing so disables the use of the **Add from Source Control** feature. If a plug-in supports the **Add from Source Control** feature (`SCC_CAP_ADDFROMSCC`), then it must support the new semantics and return `SCC_I_SHARESUBPROJOK`.
+> Initial versions of the VSSCI API did not provide a way to indicate the target project for the added files. To accommodate this, the semantics of the `lplpFIleNames` parameter have been enhanced to make it an in/out parameter rather than an output parameter. If only a single file is specified, that is, the value pointed to by `lpnFiles` = 1, then the first element of `lplpFileNames` contains the target folder. To use these new semantics, the IDE calls the `SccSetOption` function with the `nOption` parameter set to `SCC_OPT_SHARESUBPROJ`. If a source control plug-in does not support the semantics, it returns `SCC_E_OPTNOTSUPPORTED`. Doing so disables the use of the **Add from Source Control** feature. If a plug-in supports the **Add from Source Control** feature (`SCC_CAP_ADDFROMSCC`), then it must support the new semantics and return `SCC_I_SHARESUBPROJOK`.
 
 ## See also
 - [Source control plug-in API functions](../extensibility/source-control-plug-in-api-functions.md)

docs/extensibility/scccreatesubproject-function.md

@@ -1,6 +1,6 @@
 ---
-description: "This function creates a subproject with the given name under an existing parent project specified by the lpParentProjPath argument."
 title: SccCreateSubProject Function
+description: "This function creates a subproject with the given name under an existing parent project specified by the lpParentProjPath argument."
 ms.date: 11/04/2016
 ms.topic: reference
 f1_keywords:
@@ -77,7 +77,7 @@ SCCRTN SccCreateSubProject(
 |SCC_E_NONSPECIFICERROR<br /><br /> SCC_E_UNKNOWNERROR|Nonspecific failure.|
 
 ## Remarks
- If a subproject with the name already exists, the function can change the default name to create a unique one, for example by adding "_\<number>" to it. The caller must be prepared to accept changes to `lpUser`, `lpSubProjPath`, and `lpAuxProjPath`. The `lpSubProjPath` and`lpAuxProjPath` arguments are then used in a call to the [SccOpenProject](../extensibility/sccopenproject-function.md). They should not be modified by the caller upon return. These strings provide a way for the source control plug-in to track information that it needs to associate with a project. The caller IDE will not display these two parameters upon return, because the plug-in can use a formatted string that might not be suitable for viewing. The function returns a success or failure code and, if successful, fills the variable `lpSubProjPath` with the full project path to the new project.
+ If a subproject with the name already exists, the function can change the default name to create a unique one, for example by adding "_\<number>" to it. The caller must be prepared to accept changes to `lpUser`, `lpSubProjPath`, and `lpAuxProjPath`. The `lpSubProjPath` and `lpAuxProjPath` arguments are then used in a call to the [SccOpenProject](../extensibility/sccopenproject-function.md). They should not be modified by the caller upon return. These strings provide a way for the source control plug-in to track information that it needs to associate with a project. The caller IDE will not display these two parameters upon return, because the plug-in can use a formatted string that might not be suitable for viewing. The function returns a success or failure code and, if successful, fills the variable `lpSubProjPath` with the full project path to the new project.
 
  This function is similar to the [SccGetProjPath](../extensibility/sccgetprojpath-function.md), except that it silently creates a project rather than prompting the user to select one. When the `SccCreateSubProject` function is called, `lpParentProjName` and `lpAuxProjPath` will not be empty and will correspond to a valid project. These strings are usually received by the IDE from a previous call to the `SccGetProjPath` function or the [SccGetParentProjectPath](../extensibility/sccgetparentprojectpath-function.md).
 

docs/extensibility/sccgetparentprojectpath-function.md

@@ -1,6 +1,6 @@
 ---
-description: "This function determines the parent project path of a specified project."
 title: SccGetParentProjectPath Function
+description: "This function determines the parent project path of a specified project."
 ms.date: 11/04/2016
 ms.topic: reference
 f1_keywords:
@@ -88,7 +88,7 @@ SCCRTN SccGetParentProjectPath(
 
  **[HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\SourceControl] "DoNotCreateSolutionRootFolderInSourceControl"=dword:00000001**
 
- If this registry entry does not exist or is set to dword:00000000, Visual Studio attempts to use the new functions, `SccCreateSubProject`and`SccGetParentProjectPath`.
+ If this registry entry does not exist or is set to dword:00000000, Visual Studio attempts to use the new functions, `SccCreateSubProject` and `SccGetParentProjectPath`.
 
  If the registry entry is set to dword:00000001, Visual Studio does not attempt to use these new functions, and the operations of adding to source control work as they did in prior versions of Visual Studio.