Merge pull request #10246 from MicrosoftDocs/main638518432299972280sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/azure/azure-sql-database-add-connected-service.md

@@ -10,9 +10,9 @@ ms.author: ghogen
 monikerRange: ">= vs-2019"
 ---
 
-# Add a connection to an Azure SQL database
+# Add a connection to an Azure SQL Database
 
-With Visual Studio Connected Services, you can connect to Azure SQL Database, a local emulator (for example, during development), or an on-premises SQL Server database. For on-premise SQL Server, see [Connect to a database](../data-tools/add-new-connections.md).
+With Visual Studio Connected Services, you can connect to Azure SQL Database, a local emulator (for example, during development), or an on-premises SQL Server database. For on-premises SQL Server, see [Connect to a database](../data-tools/add-new-connections.md).
 
 With Visual Studio, you can connect from any of the following project types by using the **Connected Services** feature:
 

docs/azure/how-to-get-publish-profile-from-azure-app-service.md

@@ -5,7 +5,7 @@ author: ghogen
 manager: mijacobs
 ms.subservice: azure-development
 ms.topic: how-to
-ms.date: 10/19/2021
+ms.date: 05/16/2024
 ms.author: ghogen
 monikerRange: ">=vs-2019"
 ---
@@ -19,7 +19,7 @@ A publish profile is a file that contains information and settings that Visual S
 
    :::image type="content" source="./media/app-service-get-publish-profile.png" alt-text="Screenshot showing how to get the publish profile from Azure App Service." lightbox="./media/app-service-get-publish-profile.png":::
 
-A file with a .publishsettings file extension has been generated in the location where you saved it.
+A file with a `.publishsettings` extension is generated in the location you specified.
 
 See also [Azure App Service](/azure/app-service).
 

docs/containers/container-tools-react.md

@@ -60,7 +60,7 @@ Follow these steps if you're using Visual Studio 2022 version 17.8 or later:
 
 1. Create a new project using the **React and ASP.NET Core** template.
 
-   [ ![Screenshot of creating a new React and ASP.NET Core project.](media/container-tools-react/vs-2022/react-and-asp-net-core.png).](media/container-tools-react/vs-2022/react-and-asp-net-core.png#lightbox)
+   :::image type="content" alt-text="Screenshot of creating a new React and ASP.NET Core project." source="media/container-tools-react/vs-2022/react-and-asp-net-core.png" lightbox="media/container-tools-react/vs-2022/react-and-asp-net-core.png" :::
 
 1. On the **Additional information** screen, you can't select **Enable Docker Support**, but don't worry, you can add that support later.
 
@@ -70,7 +70,7 @@ Follow these steps if you're using Visual Studio 2022 version 17.8 or later:
 
 1. Right-click on the server project node, and choose **Add** > **Docker Support** to add a Dockerfile to your project.
 
-   [ ![Screenshot of Add Docker support menu item.](media/container-tools-react/vs-2022/add-docker-support.png)](media/container-tools-react/vs-2022/add-docker-support.png#lightbox)
+   :::image alt-text="Screenshot of Add Docker support menu item" type="content" source="media/container-tools-react/vs-2022/add-docker-support.png" lightbox="media/container-tools-react/vs-2022/add-docker-support.png" :::
 
 1. Select the container type.
 

docs/data-tools/walkthrough-creating-a-simple-wcf-service-in-windows-forms.md

@@ -133,7 +133,7 @@ The WCF tools are not installed with the .NET workload; use the Visual Studio In
 
 1. From the **Toolbox**, drag a `TextBox` control, a `Label` control, and a `Button` control onto the form.
 
-     [ ![Screenshot showing adding controls to the form.](../data-tools/media/vs-2022/windows-communication-foundation-client-app.png).](../data-tools/media/vs-2022/windows-communication-foundation-client-app.png#lightbox)
+     :::image type="content" alt-text="Screenshot showing adding controls to the form." source="../data-tools/media/vs-2022/windows-communication-foundation-client-app.png" lightbox="../data-tools/media/vs-2022/windows-communication-foundation-client-app.png":::
 
 1. Double-click the `Button`, and add the following code in the `Click` event handler:
 

docs/data-tools/windows-communication-foundation-services-and-wcf-data-services-in-visual-studio.md

@@ -42,7 +42,7 @@ Visual Studio provides tools for working with Windows Communication Foundation (
 
 ## What Is WCF?
 
-Windows Communication Foundation (WCF) is a unified framework for creating secure, reliable, transacted, and interoperable distributed applications. It replaces older interprocess communication technologies such as ASMX web services, .NET Remoting, Enterprise Services (Distributed Component Object Model (DCOM)), and Microsoft Message Queuing (MSMQ). WCF brings together the functionality of all those technologies under a unified programming model. This simplifies the experience of developing distributed applications.
+Windows Communication Foundation (WCF) is a unified framework for creating secure, reliable, transacted, and interoperable distributed applications. It replaces older interprocess communication technologies such as ASMX web services, .NET Remoting, Enterprise Services (Distributed Component Object Model (DCOM)), and Microsoft Message Queue (MSMQ). WCF brings together the functionality of all those technologies under a unified programming model. This simplifies the experience of developing distributed applications.
 
 ### What are WCF Data Services
 

docs/debugger/attach-to-process-running-in-docker-container.md

@@ -86,10 +86,12 @@ To attach to a running process in a Linux Docker container:
 
 4. Choose the corresponding container process from the list of **Available processes** and select **Attach** to start debugging your C# container process in Visual Studio!
 
-   ::: moniker range=">= vs-2022"   
+   ::: moniker range=">= vs-2022"
+
    ![Screenshot of the Attach to Process dialog in Visual Studio. Connection type is set to Docker (Linux Container) and the dotnet process is selected.](../debugger/media/vs-2022/docker-attach-complete.png "Completed Linux Docker Attach Menu")
    ::: moniker-end
-   ::: moniker range="vs-2019"   
+   ::: moniker range="vs-2019"
+
    ![Screenshot of the Attach to Process dialog in Visual Studio. Connection type is set to Docker (Linux Container) and the dotnet process is selected.](../debugger/media/docker-attach-complete.png "Completed Linux Docker Attach Menu")
    ::: moniker-end
 
@@ -106,10 +108,12 @@ To attach to a running process in a Windows Docker container:
 
 2. Set the **Connection type** to **Docker (Windows Container)**.
 
-   ::: moniker range=">= vs-2022"  
+   ::: moniker range=">= vs-2022"
+
    ![Screenshot of the Attach to Process dialog in Visual Studio showing a Connection type of Docker (Windows Container).](../debugger/media/vs-2022/attach-process-menu-docker-windows.png "Attach_To_Process_Menu")
    ::: moniker-end
-   ::: moniker range="vs-2019"  
+   ::: moniker range="vs-2019"
+
    ![Screenshot of the Attach to Process dialog in Visual Studio showing a Connection type of Docker (Windows Container).](../debugger/media/attach-process-menu-docker-windows.png "Attach_To_Process_Menu")
    ::: moniker-end
 
@@ -128,9 +132,11 @@ To attach to a running process in a Windows Docker container:
 
 4. Choose the corresponding container process from the list of **Available processes** and select **Attach** to start debugging your C# container process.
 
-   ::: moniker range=">= vs-2022"  
+   ::: moniker range=">= vs-2022"
+
    ![Screenshot of the Attach to Process dialog in Visual Studio. Connection type is set to Docker (Windows Container) and the dotnet.exe process is selected.](../debugger/media/vs-2022/docker-attach-complete-windows.png "Completed Windows Docker Attach Menu")
    ::: moniker-end
-   ::: moniker range="vs-2019"  
+   ::: moniker range="vs-2019"
+
    ![Screenshot of the Attach to Process dialog in Visual Studio. Connection type is set to Docker (Windows Container) and the dotnet.exe process is selected.](../debugger/media/docker-attach-complete-windows.png "Completed Windows Docker Attach Menu")
    ::: moniker-end

docs/debugger/attach-to-running-processes-with-the-visual-studio-debugger.md

@@ -283,8 +283,8 @@ For client-side script debugging, script debugging must be enabled in the browse
 |Containerized app - Debug|Use **Attach to Process**|*dotnet.exe* or a unique process name|See [Attach to a process running in a Docker container](../debugger/attach-to-process-running-in-docker-container.md)|
 |Python on Linux - Remote debug|Use **Attach to Process**|*debugpy*|See [Attach remotely from Python Tools](../python/debugging-python-code-on-remote-linux-machines.md#attach-remotely-from-python-tools)|
 |Other supported app types - Debug on a server process|If server is remote, use remote tools, and **Attach to Process**|*chrome.exe*, *msedge.exe*, or other processes|If necessary, use Resource Monitor to help identify the process. See [Remote debugging](../debugger/remote-debugging.md).|
-|Universal Windows App (UWP), OneCore, HoloLens, or IoT app - Remote debug|Debug installed app package|N/A|See [Debug an installed app package](debug-installed-app-package.md) instead of using **Attach to Process**|
-|Universal Windows App (UWP), OneCore, HoloLens, or IoT - Debug an app that you didn't start from Visual Studio|Debug installed app package|N/A|See [Debug an installed app package](debug-installed-app-package.md) instead of using **Attach to Process**|
+|Universal Windows Platform (UWP) App, OneCore, HoloLens, or IoT app - Remote debug|Debug installed app package|N/A|See [Debug an installed app package](debug-installed-app-package.md) instead of using **Attach to Process**|
+|UWP App, OneCore, HoloLens, or IoT - Debug an app that you didn't start from Visual Studio|Debug installed app package|N/A|See [Debug an installed app package](debug-installed-app-package.md) instead of using **Attach to Process**|
 
 ## Use debugger features
 

docs/debugger/debug-interface-access/baseclass.md

@@ -1,5 +1,5 @@
 ---
-title: "BaseClass"
+title: BaseClass
 description: Find reference information about the BaseClass symbol type. A base class for user-defined type (UDT) symbols is identified by a child with a SymTagBaseClass tag.
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -14,12 +14,14 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # BaseClass
 
 Each base class for a user-defined type (UDT) symbol is identified by a child with a `SymTagBaseClass` tag. The [IDiaSymbol::get_type](../../debugger/debug-interface-access/idiasymbol-get-type.md) property contains the symbol for the underlying UDT, and all properties of the underlying UDT are available as part of this BaseClass symbol.
 
 ## Properties
- The following table shows additional valid properties for this symbol type.
+
+The following table shows additional valid properties for this symbol type.
 
 |Property|Data type|Description|
 |--------------|---------------|-----------------|
@@ -56,5 +58,6 @@ Each base class for a user-defined type (UDT) symbol is identified by a child wi
 |[IDiaSymbol::get_volatileType](../../debugger/debug-interface-access/idiasymbol-get-volatiletype.md)|`BOOL`|`TRUE` if the base class is marked as volatile.|
 
 ## See also
+
 - [Class Hierarchy of Symbol Types](../../debugger/debug-interface-access/class-hierarchy-of-symbol-types.md)
-- [UDT](../../debugger/debug-interface-access/udt.md)
+- [UDT](../../debugger/debug-interface-access/udt.md)

docs/debugger/debug-interface-access/data-debug-interface-access-sdk.md

@@ -1,6 +1,6 @@
 ---
-description: "All variables, such as parameters, local variables, global variables, and class members, are identified by SymTagData symbols."
-title: "Data (Debug Interface Access SDK)"
+description: All variables, such as parameters, local variables, global variables, and class members, are identified by SymTagData symbols.
+title: Data (Debug Interface Access SDK)
 ms.date: "11/04/2016"
 ms.topic: "reference"
 dev_langs:
@@ -15,12 +15,14 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # Data (Debug Interface Access SDK)
 
 All variables, such as parameters, local variables, global variables, and class members, are identified by `SymTagData` symbols. Constant values (`LocIsConstant`) are also identified with this type.
 
 ## Properties
- The following table shows the properties that are valid for this symbol type.
+
+The following table shows the properties that are valid for this symbol type.
 
 |Property|Data type|Description|
 |--------------|---------------|-----------------|
@@ -56,6 +58,7 @@ All variables, such as parameters, local variables, global variables, and class
 |[IDiaSymbol::get_volatileType](../../debugger/debug-interface-access/idiasymbol-get-volatiletype.md)|`BOOL`|`TRUE` if the data is marked as volatile.|
 
 ## See also
+
 - [CV_access_e Enumeration](../../debugger/debug-interface-access/cv-access-e.md)
 - [DataKind Enumeration](../../debugger/debug-interface-access/datakind.md)
 - [Lexical Hierarchy of Symbol Types](../../debugger/debug-interface-access/lexical-hierarchy-of-symbol-types.md)

docs/debugger/debug-interface-access/datakind.md

@@ -1,6 +1,6 @@
 ---
-description: "Indicates the particular scope of a data value."
-title: "DataKind"
+description: Indicates the particular scope of a data value.
+title: DataKind
 ms.date: "11/04/2016"
 ms.topic: "reference"
 dev_langs:
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # DataKind
 
 Indicates the particular scope of a data value.
 
 ## Syntax
 
-```C++
-enum DataKind {
+```c++
+enum DataKind {
     DataIsUnknown,
     DataIsLocal,
     DataIsStaticLocal,
@@ -49,11 +50,14 @@ enum DataKind {
 | DataIsConstant     | Data item is a constant value.           |
 
 ## Remarks
+
 The values in this enumeration are returned by the [IDiaSymbol::get_dataKind](../../debugger/debug-interface-access/idiasymbol-get-datakind.md) method.
 
 ## Requirements
+
 Header: cvconst.h
 
 ## See also
+
 - [Enumerations and Structures](../../debugger/debug-interface-access/enumerations-and-structures.md)
 - [IDiaSymbol::get_dataKind](../../debugger/debug-interface-access/idiasymbol-get-datakind.md)

docs/debugger/debug-interface-access/enum-debug-interface-access-sdk.md

@@ -1,6 +1,6 @@
 ---
-description: "Enumerations are identified by SymTagEnum symbols."
-title: "Enum (Debug Interface Access SDK)"
+description: Enumerations are identified by SymTagEnum symbols.
+title: Enum (Debug Interface Access SDK)
 ms.date: "11/04/2016"
 ms.topic: "reference"
 dev_langs:
@@ -13,12 +13,14 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # Enum (Debug Interface Access SDK)
 
 Enumerations are identified by `SymTagEnum` symbols. Each enumeration value appears as a class child with a `SymTagConstant` tag.
 
 ## Properties
- The following table shows additional valid properties for this symbol type.
+
+The following table shows additional valid properties for this symbol type.
 
 |Property|Data type|Description|
 |--------------|---------------|-----------------|
@@ -46,4 +48,5 @@ Enumerations are identified by `SymTagEnum` symbols. Each enumeration value appe
 |[IDiaSymbol::get_volatileType](../../debugger/debug-interface-access/idiasymbol-get-volatiletype.md)|`BOOL`|`TRUE` if the enumeration is marked as volatile.|
 
 ## See also
+
 - [Class Hierarchy of Symbol Types](../../debugger/debug-interface-access/class-hierarchy-of-symbol-types.md)

docs/debugger/debug-interface-access/idiadatasource-loaddatafrompdb.md

@@ -1,5 +1,5 @@
 ---
-description: "Opens and prepares a program database (.pdb) file as a debug data source."
+description: Opens and prepares a program database (.pdb) file as a debug data source.
 title: "IDiaDataSource::loadDataFromPdb"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,24 +12,27 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaDataSource::loadDataFromPdb
 
 Opens and prepares a program database (.pdb) file as a debug data source.
 
 ## Syntax
 
-```C++
+```c++
 HRESULT loadDataFromPdb (
    LPCOLESTR pdbPath
 );
 ```
 
 #### Parameters
+
 pdbPath
 
 [in] The path to the .pdb file.
 
 ## Return Value
+
 If successful, returns `S_OK`; otherwise, returns an error code. The following table shows the possible return values for this method.
 
 |Value|Description|
@@ -40,6 +43,7 @@ If successful, returns `S_OK`; otherwise, returns an error code. The following t
 |E_UNEXPECTED|Data source has already been prepared.|
 
 ## Remarks
+
 This method loads the debug data directly from a .pdb file.
 
 To validate the .pdb file against specific criteria, use the [IDiaDataSource::loadAndValidateDataFromPdb](../../debugger/debug-interface-access/idiadatasource-loadandvalidatedatafrompdb.md) method.
@@ -50,7 +54,7 @@ To load a .pdb file directly from memory, use the [IDiaDataSource::loadDataFromI
 
 ## Example
 
-```C++
+```c++
 HRESULT hr = pSource->loadDataFromPdb( L"myprog.pdb" );
 if (FAILED(hr))
 {
@@ -59,6 +63,7 @@ if (FAILED(hr))
 ```
 
 ## See also
+
 - [IDiaDataSource](../../debugger/debug-interface-access/idiadatasource.md)
 - [IDiaDataSource::loadDataForExe](../../debugger/debug-interface-access/idiadatasource-loaddataforexe.md)
 - [IDiaDataSource::loadAndValidateDataFromPdb](../../debugger/debug-interface-access/idiadatasource-loadandvalidatedatafrompdb.md)

docs/debugger/debug-interface-access/idiadatasource-opensession.md

@@ -1,5 +1,5 @@
 ---
-description: "Opens a session for querying symbols."
+description: Opens a session for querying symbols.
 title: "IDiaDataSource::openSession"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,24 +12,27 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaDataSource::openSession
 
 Opens a session for querying symbols.
 
 ## Syntax
 
-```C++
-HRESULT openSession ( 
+```c++
+HRESULT openSession ( 
    IDiaSession** ppSession
 );
 ```
 
 #### Parameters
+
 ppSession
 
 [out] Returns an [IDiaSession](../../debugger/debug-interface-access/idiasession.md) object representing the open session.
 
 ## Return Value
+
 If successful, returns `S_OK`; otherwise, returns an error code. The following table shows the possible return values for this method.
 
 |Value|Description|
@@ -39,13 +42,14 @@ If successful, returns `S_OK`; otherwise, returns an error code. The following t
 |E_OUTOFMEMORY|Insufficient memory to open the session.|
 
 ## Remarks
+
 This method opens an [IDiaSession](../../debugger/debug-interface-access/idiasession.md) object for a data source.
 
 `IDiaSession` objects implement queries into the data source. A session manages one address space for each set of debug symbols. If the .exe or .dll file described by the data source symbols is active in multiple address ranges (for example, because multiple processes have it loaded), then one session for each address range should be used.
 
 ## Example
 
-```C++
+```c++
 IDiaSession* pSession;
 HRESULT hr = pSource->openSession( &pSession );
 if (FAILED(hr))
@@ -55,6 +59,7 @@ if (FAILED(hr))
 ```
 
 ## See also
+
 - [IDiaDataSource](../../debugger/debug-interface-access/idiadatasource.md)
 - [Overview](../../debugger/debug-interface-access/overview-debug-interface-access-sdk.md)
 - [IDiaSession](../../debugger/debug-interface-access/idiasession.md)