Merging changes synced from https://github.com/MicrosoftDocs/visualstudio-docs-pr (branch live)

Author: Learn Build Service GitHub App

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

@@ -1,5 +1,5 @@
 ---
-title: "CustomType"
+title: CustomType
 description: Find reference information about the CustomType symbol type (SymTagCustomType) in the Visual Studio debug interface access SDK.
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,12 +12,14 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # CustomType
 
 Vendor-defined types (compiler-specific types) are identified by a `SymTagCustomType` 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|
 |--------------|---------------|-----------------|
@@ -30,4 +32,5 @@ Vendor-defined types (compiler-specific types) are identified by a `SymTagCustom
 |[IDiaSymbol::get_types](../../debugger/debug-interface-access/idiasymbol-get-types.md)|`IDiaSymbol**`|Array of all types referenced by the custom type symbol.|
 
 ## See also
-- [Class Hierarchy of Symbol Types](../../debugger/debug-interface-access/class-hierarchy-of-symbol-types.md)
+
+- [Class Hierarchy of Symbol Types](../../debugger/debug-interface-access/class-hierarchy-of-symbol-types.md)

docs/debugger/debug-interface-access/cv-access-e.md

@@ -1,5 +1,5 @@
 ---
-title: "CV_access_e"
+title: CV_access_e
 description: Get information about the CV_access_e enumeration type, which specifies the scope of visibility (access level) of members in the debug interface access SDK.
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,13 +12,14 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # CV_access_e
 
 Specifies the scope of visibility (access level) of member functions and variables.
 
 ## Syntax
 
-```C++
+```c++
 typedef enum CV_access_e {
     CV_private   = 1,
     CV_protected = 2,
@@ -35,12 +36,15 @@ typedef enum CV_access_e {
 | CV_public    | Member has public access.    |
 
 ## Remarks
+
 The `friend` access specifier is not included here because it is typically used by non-member functions that have access to both private and protected elements of the class. Use the [IDiaSymbol::get_symTag](../../debugger/debug-interface-access/idiasymbol-get-symtag.md) method to find symbols with `SymTagFriend` access.
 
 ## Requirements
+
 Header: cvconst.h
 
 ## See also
+
 - [Enumerations and Structures](../../debugger/debug-interface-access/enumerations-and-structures.md)
 - [IDiaSymbol::get_access](../../debugger/debug-interface-access/idiasymbol-get-access.md)
 - [IDiaSymbol::get_symTag](../../debugger/debug-interface-access/idiasymbol-get-symtag.md)

docs/debugger/debug-interface-access/cv-call-e.md

@@ -1,5 +1,5 @@
 ---
-title: "CV_call_e"
+title: CV_call_e
 description: Get reference information about the CV_call_e enumeration type, which specifies the calling convention for a function in the debug interface access SDK.
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,6 +12,7 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # CV_call_e
 
 Specifies the calling convention for a function.
@@ -21,7 +22,7 @@ Specifies the calling convention for a function.
 
 ## Syntax
 
-```C++
+```c++
 typedef enum CV_call_e {
     CV_CALL_NEAR_C    = 0x00,
     CV_CALL_NEAR_FAST = 0x04,
@@ -44,11 +45,14 @@ typedef enum CV_call_e {
 | CV_CALL_CLRCALL   | Specifies a function-calling convention used by the Common Language Runtime (CLR)</br> (also known as a managed code calling convention).                            |
 
 ## Remarks
+
 The values in this enumeration are returned by a call to the [IDiaSymbol::get_callingConvention](../../debugger/debug-interface-access/idiasymbol-get-callingconvention.md) method.
 
 ## Requirements
+
 Header: cvconst.h
 
 ## See also
+
 - [Enumerations and Structures](../../debugger/debug-interface-access/enumerations-and-structures.md)
 - [IDiaSymbol::get_callingConvention](../../debugger/debug-interface-access/idiasymbol-get-callingconvention.md)

docs/debugger/debug-interface-access/cv-cfl-lang.md

@@ -1,5 +1,5 @@
 ---
-title: "CV_CFL_LANG"
+title: CV_CFL_LANG
 description: Get information about the CV_CFL_LANG enumeration type, which specifies the code language of the application or linked module in the debug interface access SDK.
 ms.date: "4/04/2023"
 ms.topic: "reference"
@@ -12,13 +12,14 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # CV_CFL_LANG
 
 Specifies the source code language of the application or linked module.
 
 ## Syntax
 
-```C++
+```c++
 typedef enum CV_CFL_LANG {
     CV_CFL_C        = 0x00,
     CV_CFL_CXX      = 0x01,
@@ -75,11 +76,14 @@ typedef enum CV_CFL_LANG {
 | CV_CFL_GO       | Application language is Go.                                                                 |
 
 ## Remarks
+
 The values in this enumeration are returned by a call to the [IDiaSymbol::get_language](../../debugger/debug-interface-access/idiasymbol-get-language.md) method.
 
 ## Requirements
+
 Header: cvconst.h
 
 ## See also
+
 - [Enumerations and Structures](../../debugger/debug-interface-access/enumerations-and-structures.md)
 - [IDiaSymbol::get_language](../../debugger/debug-interface-access/idiasymbol-get-language.md)

docs/debugger/debug-interface-access/cv-cpu-type-e.md

@@ -1,5 +1,5 @@
 ---
-title: "CV_CPU_TYPE_e"
+title: CV_CPU_TYPE_e
 description: Get reference information about the CV_CPU_TYPE_e enumeration type, which specifies the target processor in the debug interface access SDK.
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,6 +12,7 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # CV_CPU_TYPE_e
 
 Specifies the target processor.
@@ -21,7 +22,7 @@ Specifies the target processor.
 
 ## Syntax
 
-```C++
+```c++
 typedef enum CV_CPU_TYPE_e {
     CV_CFL_8080         = 0x00,
     CV_CFL_8086         = 0x01,
@@ -90,11 +91,14 @@ typedef enum CV_CPU_TYPE_e {
 ```
 
 ## Remarks
+
 The values in this enumeration are returned by a call to the [IDiaSymbol::get_platform](../../debugger/debug-interface-access/idiasymbol-get-platform.md) method.
 
 ## Requirements
+
 Header: cvconst.h
 
 ## See also
+
 - [Enumerations and Structures](../../debugger/debug-interface-access/enumerations-and-structures.md)
 - [IDiaSymbol::get_platform](../../debugger/debug-interface-access/idiasymbol-get-platform.md)

docs/debugger/debug-interface-access/cv-hreg-e.md

@@ -1,5 +1,5 @@
 ---
-title: "CV_HREG_e"
+title: CV_HREG_e
 description: Get reference information about the CV_HREG_e enumeration type, which specifies a target register in the debug interface access SDK.
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,6 +12,7 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # CV_HREG_e
 
 Specifies a target register.
@@ -21,7 +22,7 @@ Specifies a target register.
 
 ## Syntax
 
-```C++
+```c++
 enum CV_HREG_e {
     // Register subset shared by all processor types
     CV_ALLREG_ERR    = 30000,
@@ -408,7 +409,7 @@ enum CV_HREG_e {
 | ---------------------- | --------------------------------------------------------------------------- |
 | CV_REG_*               | Registers used by Intel 80x86 and ix86 processors and p-code.               |
 | CV_R68_*               | Registers used by 68K processor.                                            |
-| CV_M4_*                | Registers used by MIPS 4000 series processor.                               |
+| CV_M4_*                | <!-- docutune:ignoredChange 'MIPS' --> Registers used by MIPS 4000 series processor.                               |
 | CV_ALPHA_*             | Registers used by Digital Equipment Corporation Alpha AXP series processor. |
 | CV_PPC_*               | Registers used by Motorola/IBM PowerPC processor.                           |
 | CV_SH3_* and CV_SH_\\* | Registers used by Hitachi SH3 and Hitachi SH series processor.              |
@@ -419,6 +420,7 @@ enum CV_HREG_e {
 | CV_M32R_*              | Registers used by Mitsubishi M32R processor.                                |
 
 ## Remarks
+
 Each processor type uses its own unique set of registers.
 
 The values in this enumeration are passed to the following methods:
@@ -434,9 +436,11 @@ The values in this enumeration are passed to the following methods:
 - [IDiaStackFrame::get_registerValue](../../debugger/debug-interface-access/idiastackframe-get-registervalue.md)
 
 ## Requirements:
+
 Header: cvconst.h
 
 ## See also
+
 - [Enumerations and Structures](../../debugger/debug-interface-access/enumerations-and-structures.md)
 - [IDiaStackWalkFrame::get_registerValue](../../debugger/debug-interface-access/idiastackwalkframe-get-registervalue.md)
 - [IDiaStackWalkFrame::put_registerValue](../../debugger/debug-interface-access/idiastackwalkframe-put-registervalue.md)

docs/get-started/csharp/tutorial-wasdk.md

@@ -3,7 +3,7 @@ title: "Tutorial: Create Windows App SDK Apps with Visual Studio & C#"
 description: Create a Windows App SDK application in Visual Studio by using the Extensible Application Markup Language (XAML) and C#.
 titleSuffix: ""
 ms.custom: vs-acquisition
-ms.date: "04/27/2023"
+ms.date: 5/21/2024
 ms.subservice: general-ide
 ms.topic: tutorial
 ms.devlang: csharp
@@ -23,6 +23,28 @@ In this introduction to the Visual Studio integrated development environment (ID
 
 If you haven't already installed Visual Studio, go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/?cid=learn-onpage-download-cta) page to install it for free.
 
+::: moniker range=">=vs-2022"
+## Prerequisites
+
+- You need Visual Studio to complete this tutorial.
+Visit the [Visual Studio downloads page](https://visualstudio.microsoft.com/vs/) for a free version.
+- Workloads and components required for developing with WinUI and the Windows App SDK. To verify or install a workload in Visual Studio, select **Tools** > **Get Tools and Features**. For more information, see [Change workloads or individual components](../../install/modify-visual-studio.md#change-workloads-or-individual-components).
+    
+    On the **Workloads** tab of the Visual Studio Installer, select the following workloads and components:
+
+    ### [Visual Studio 2022 version 17.10 and later](#tab/vs-2022-17-10)
+    
+    * For **C#** app development using the Windows App SDK, select **Windows application development**.
+    
+    ### [Visual Studio 2022 version 17.1 - 17.9](#tab/vs-2022-17-1)
+    
+    * For **C#** app development using the Windows App SDK, select **.NET Desktop Development**.
+    * Then in the **Installation details** pane of the installation dialog box, select **Windows App SDK C# Templates** (near the bottom of the list).
+    
+    ---
+
+::: moniker-end
+
 ## Create a project
 
 First, create a WinUI 3 project. The project type comes with all the template files you need, before you've even added anything!
@@ -43,6 +65,7 @@ The Windows App SDK 1.1.x templates are available by installing a [Visual Studio
 > [Download Windows App SDK C# SDK VS2019 Templates](https://aka.ms/windowsappsdk/1.1/1.1.5/WindowsAppSDK.Cs.Extension.Dev16.vsix)
 
 After the templates extension has been installed, you can create your first project. For more information about Visual Studio 2019 support, see [Install tools for the Windows App SDK](/windows/apps/windows-app-sdk/set-up-your-development-environment). The rest of this tutorial will assume you're using Visual Studio 2022.
+
 ::: moniker-end
 
 1. Open Visual Studio, and on the start window, choose **Create a new project**.
@@ -51,9 +74,6 @@ After the templates extension has been installed, you can create your first proj
 
    :::image type="content" source="media/vs-2022/winui-create-new-project.png" alt-text="Screenshot of the 'Create a new project' dialog with 'WinUI' entered in the search box, and the 'Blank App, Packaged (WinUI 3 in Desktop)' project template highlighted.":::
 
-   > [!NOTE]
-   > If you don't see the **Blank App, Packaged (WinUI 3 in Desktop)** project template, click the **Install more tools and features** link.<br><br>:::image type="content" source="media/vs-2022/winui-not-finding.png" alt-text="Screenshot of the Create a new project window showing the 'Install more tools and features' link.":::<br><br>The Visual Studio Installer launches. Choose the **.NET Desktop Development** workload, then in the **Installation details** pane of the installation dialog box, select **Windows App SDK C# Templates** (at the bottom of the list). Now select **Modify**.<br><br>:::image type="content" source="media/vs-2022/winui-desktop-dev-workload.png" alt-text="Screenshot of the Visual Studio Installer showing the .NET Desktop Development workload.":::
-
 1. Give the project a name, *HelloWorld*, and choose **Create**.
 
    :::image type="content" source="media/vs-2022/winui-configure-your-project.png" alt-text="Screenshot of the 'Configure your new project' dialog with 'HelloWorld' entered in the Project name field.":::

docs/install/use-command-line-parameters-to-install-visual-studio.md

@@ -2,7 +2,7 @@
 title: Use command-line parameters to install Visual Studio
 titleSuffix: ''
 description: Use command-line parameters with your Visual Studio installation and start the installation with preselected options or automate the installation and update process.
-ms.date: 03/11/2024
+ms.date: 05/20/2024
 ms.topic: conceptual
 f1_keywords:
 - command-line parameters
@@ -185,8 +185,10 @@ Syntax examples:
    C:\>"C:\Program Files\Microsoft\Visual Studio\2022\Enterprise\vs_enterprise.exe" modifySettings --channelUri https://aka.ms/vs/17/release.LTSC.17.0/channel --productID Microsoft.VisualStudio.Product.Enterprise --newChannelUri \\layoutserver\share\path\channelmanifest.json --removeOos true --quiet
   ``` 
 
+::: moniker range="vs-2022"
+
 ## Rollback command and command-line parameters
-You can roll back the update programmatically by using the installer on the client machine, and passing in the rollback command alongside the installation path instance.  
+Starting in Visual Studio 2022, you can [roll back an update](/troubleshoot/developer/visualstudio/installation/troubleshoot-installation-issues?toc=%2Fvisualstudio%2Ftoc.json#7-roll-back-to-a-previous-install-for-visual-studio-2022-only) programmatically by using the installer on the client machine and passing in the rollback command alongside the installation path instance. 
 
 | **Command** | **Description**                                                                                                         |
 |-------------|-------------------------------------------------------------------------------------------------------------------------|
@@ -201,6 +203,8 @@ Syntax examples:
   ```shell
   "C:\Program Files (x86)\Microsoft Visual Studio\Installer\setup.exe" rollback -–installPath "C:\Program Files\Microsoft Visual Studio\2022\Enterprise"
   ```
+
+::: moniker-end
 
 ## Administrator Update command and command-line parameters