Merged main into live

Author: mijacobs

docs/azure/media/vs-azure-tools-optimizing-azure-code-in-visual-studio/IC796660.png

@@ -25,7 +25,7 @@ This article describes how to attach the Visual Studio debugger to an ASP.NET Co
 
 ## Enable remote debugging
 
-Before you can debug this issue with Visual Studio, you must enable the remote debugging feature on the App Service. This setting will allow the Visual Studio debugger to connect to the main App Service web hosting process.
+Before you can debug this issue with Visual Studio, you must enable the remote debugging feature on the App Service. This setting allows the Visual Studio debugger to connect to the main App Service web hosting process.
 
 1. Sign into your own [Azure portal](https://portal.azure.com/).
 
@@ -45,16 +45,14 @@ Your app service instance now supports remote debugging through Visual Studio.
 
 ## Configure debugging settings
 
-Make sure you have completed the following steps in Visual Studio before debugging an app in Azure to ensure success.
-
-1. First, make sure you have successfully built your project at least one time. A successful build ensures the source code and any necessary compiled files are ready to go. If your application is running locally, make sure to stop the app.
+1. Build your app without errors. Stop your app if it's running locally.
 
    > [!NOTE]
    > Make sure the state of your local code matches what was deployed to Azure. This ensures that the local symbol files and source code line up with the deployed app.
 
 1. Select **Debug > Options** from the top Visual Studio menu. Ensure that **Enable Just My code** is *unchecked* (as shown below), and then select **OK**.
 
-    Changing this setting allows Visual Studio to debug the optimized code that was deployed to Azure using the necessary symbol files from your local bin folder. Symbol files are used by the debugger as a bridge between compiled, executing code and the source code in Visual Studio, which is why it's important that your local source code matched the deploy app.
+    Changing this setting allows Visual Studio to debug the optimized code that was deployed to Azure using the necessary symbol files from your local bin folder. Symbol files are used by the debugger as a bridge between compiled, executing code and the source code in Visual Studio. Matching symbol files are required for remote debugging.
 
     :::image type="content" source="../debugger/media/vs-2022/visual-studio-remote-debug-settings.png" alt-text="A screenshot of the Visual Studio debugging settings.":::
 
@@ -70,14 +68,17 @@ Make sure you have completed the following steps in Visual Studio before debuggi
 
 1. Locate and select the App Service instance you created in the previous step, and then choose **OK**.
 
-1. The `w3wp.exe` process should appear in the list of available processes to connect to, which is the main process of the Azure App Service that hosts the deployed application. Select that process and then choose **Attach** in the bottom right to connect the Visual Studio debugger.
+1. The `w3wp.exe` process should appear in the list of available processes to connect to. `w3wp.exe` is the main process of the Azure App Service that hosts the deployed application. Select the `w3wp.exe` process and then choose **Attach** in the bottom right.
 
     :::image type="content" source="../debugger/media/vs-2022/visual-studio-remote-debug-attach-to-process.png" alt-text="A screenshot of the attach to process features." lightbox="../debugger/media/vs-2022/visual-studio-remote-debug-attach-to-process.png":::
 
-1. In a C# application file such as `Index.cshtml.cs`, set a breakpoint by clicking in the left margin. (Or, right-click and choose **Breakpoint** > **Insert breakpoint**.)
+1. In a C# application file such as `Index.cshtml.cs`, set a breakpoint by clicking in the left margin. Alternatively, right-click and choose **Breakpoint** > **Insert breakpoint**.
 
-1. Take action in the web app to hit the breakpoint. If you're attached to the process but can't hit the breakpoint, make sure your publish profile in Visual Studio is set to a Debug configuration instead of a Release configuration.
+1. In the web app, navigate to the endpoint with the breakpoint. If you're attached to the process but can't hit the breakpoint, make sure your publish profile in Visual Studio is set to a Debug configuration instead of a Release configuration.
 
-1. (Optional) you can also verify that Visual Studio has loaded the symbol files for your debugging session. Navigate to **Debug > Windows > Modules** to open the modules window. This window should indicate that the symbol files were successfully loaded after the **Just my code** configuration changes you made earlier.
+1. Optional: To verify that Visual Studio has loaded the symbol files for your debugging session. Navigate to **Debug > Windows > Modules** to open the modules window. This window indicates that the symbol files were successfully loaded after the **Just my code** configuration changes you made earlier.
 
     :::image type="content" source="../debugger/media/vs-2022/visual-studio-symbol-files.png" alt-text="A screenshot of the symbol files window.":::
+
+> [!NOTE]
+> For subsequent debugging of the app service, select the select **Debug** > **Reattach to w3wp.exe** or use the Shift+Alt+P hot keys.

docs/azure/media/vs-azure-tools-publishing-a-cloud-service/IC744134.png

@@ -159,37 +159,37 @@ dotnet tool install --global --add-source <path-to-folder> <tool-name> --version
 - Sign *contoso.vsix* with a certificate imported to the **user** certificate store:
 
   ```dotnetcli
-  sign contoso.vsix -cfp 24D589...FB9523B36E -d "Constoso VSIX Signature" -u "http://www.contoso.com"
+  sign code certificate-store contoso.vsix -cfp 24D589...FB9523B36E -d "Constoso VSIX Signature" -u "http://www.contoso.com"
   ```
 
 - Sign *contoso.vsix* with certificate *cert.pfx* (not password protected) using a SHA-512 fingerprint:
 
   ```dotnetcli
-  sign contoso.vsix -cfp A87A6F...894559B981 -cfpa sha512 -cf D:\certificates\cert.pfx -d "Constoso VSIX Signature" -u "http://www.contoso.com"
+  sign code certificate-store contoso.vsix -cfp A87A6F...894559B981 -cfpa sha512 -cf D:\certificates\cert.pfx -d "Constoso VSIX Signature" -u "http://www.contoso.com"
   ```
 
 - Sign *contoso.vsix* with certificate *cert.pfx* (password protected):
 
   ```dotnetcli
-  sign contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -cf cert.pfx -p <password> -d "Constoso VSIX Signature" -u "http://www.contoso.com"
+  sign code certificate-store contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -cf cert.pfx -p <password> -d "Constoso VSIX Signature" -u "http://www.contoso.com"
   ```
 
 - Sign multiple VSIX packages - *contoso.vsix* and *all .vsix files in the directory specified* with certificate *cert.pfx* (not password protected):
 
   ```dotnetcli
-  sign *.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -cf cert.pfx -d "Constoso VSIX Signature" -u "http://www.contoso.com"
+  sign code certificate-store *.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -cf cert.pfx -d "Constoso VSIX Signature" -u "http://www.contoso.com"
   ```
 
 - Sign *contoso.vsix* with a certificate stored in a secure USB drive.
 
   ```dotnetcli
-  sign contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -d "Constoso VSIX Signature" -u "http://www.contoso.com"
+  sign code certificate-store contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -d "Constoso VSIX Signature" -u "http://www.contoso.com"
   ```
 
 - Sign *contoso.vsix* with a certificate stored in a secure USB drive and accessed from the **machine** certificate store (-km option).
 
   ```dotnetcli
-  sign contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -km -d "Constoso VSIX Signature" -u "http://www.contoso.com"
+  sign code certificate-store contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -km -d "Constoso VSIX Signature" -u "http://www.contoso.com"
   ```
 
   > [!NOTE]
@@ -198,5 +198,5 @@ dotnet tool install --global --add-source <path-to-folder> <tool-name> --version
 - Sign *contoso.vsix* with a certificate stored in a secure USB drive specifying file digest algorithm (-fd), timestamp server (-t), and a custom output path (-o) for the signed VSIX.
 
   ```dotnetcli
-  sign contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -d "Constoso VSIX Signature" -u "http://www.contoso.com" -t "http://timestamp.acs.microsoft.com/" -fd sha256 -o "ContosoSigned.vsix"
+  sign code certificate-store contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -d "Constoso VSIX Signature" -u "http://www.contoso.com" -t "http://timestamp.acs.microsoft.com/" -fd sha256 -o "ContosoSigned.vsix"
   ```

docs/debugger/remote-debugging-azure-app-service.md

@@ -383,7 +383,7 @@ See [the full Dotfuscator Community User Guide at preemptive.com][full] for deta
 [attributes-checks]: https://www.preemptive.com/dotfuscator/ce/docs/help/attributes_checks.html
 [attributes-obfuscation]: https://www.preemptive.com/dotfuscator/ce/docs/help/attributes_obfuscation.html
 
-[verbosity]: ../how-to-view-save-and-configure-build-log-files.md#to-change-the-amount-of-information-included-in-the-build-log
+[verbosity]: ../how-to-view-save-and-configure-build-log-files.md#specify-data-verbosity-for-build-logs
 [dotnet-attributes]: /dotnet/standard/attributes
 [application-insights]: /azure/azure-monitor/app/app-insights-overview
 [nuget-org]: https://www.nuget.org/

docs/extensibility/dotnet-sign-cli-reference-vsix.md

@@ -1,8 +1,8 @@
 ---
 title: Locate and organize project templates
-description: Locate and organize project templates, including installed templates and user templates (.vstemplate files), in Visual Studio.
-ms.date: 11/15/2022
-ms.topic: how-to
+description: Locate and organize project and item templates in Visual Studio, including installed templates and user templates (.vstemplate files).
+ms.date: 08/21/2024
+ms.topic: concept-article
 helpviewer_keywords:
 - project templates [Visual Studio], locations
 - item templates [Visual Studio], locations
@@ -11,18 +11,21 @@ author: ghogen
 ms.author: ghogen
 manager: mijacobs
 ms.subservice: general-ide
+
+#customer intent: As a developer, I want to locate and organize project and item templates in Visual Studio, so I can easily access them to create code for new projects and items.
 ---
+
 # Locate and organize project and item templates
 
-Template files must be placed in a known location in order for them to be shown in the new project and new item dialog boxes..
+When template files are placed in a known location, Visual Studio can locate the files and make them available for creating new projects and new items. Templates provide a convenient way to create applications, access class libraries, implement unit tests, and set up configuration files.
 
-## Locate templates
+Installed templates and user templates (*.vstemplate* files) are stored in different locations. You can also customize the locations with Visual Studio options.
 
-Installed templates and user templates are stored in two different locations.
+This article describes the template file locations recognized by Visual Studio.
 
-### Installed templates
+## Location for installed templates
 
-By default, templates installed with Visual Studio are located in:
+By default, templates installed with Visual Studio are placed in the following locations:
 
 ::: moniker range="vs-2019"
 
@@ -35,7 +38,6 @@ For example, the following directory has the Visual Basic item templates for Eng
 *C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\Common7\\IDE\\ItemTemplates\\VisualBasic\\1033*
 
 ::: moniker-end
-
 ::: moniker range="vs-2022"
 
 - *%ProgramFiles%\\Microsoft Visual Studio\\2022\\\<edition>\\Common7\IDE\ProjectTemplates\\<Language\>\\<Locale ID\>*
@@ -48,9 +50,9 @@ For example, the following directory has the Visual Basic item templates for Eng
 
 ::: moniker-end
 
-### User templates
+## Location for user templates
 
-If you add a compressed (*.zip*) file that includes a *.vstemplate* file to the user template directory, the template appears in the new project and new item dialog boxes. By default, user templates are located in:
+When you add a compressed (*.zip*) file that includes a *.vstemplate* file to the user template directory, Visual Studio makes the template available in the **New project** and **New item** dialogs. By default, user templates are placed in the following locations:
 
 ::: moniker range="vs-2019"
 
@@ -76,18 +78,12 @@ For example, the following directory has user project templates for C#:
 
 ::: moniker-end
 
-> [!TIP]
-> You can change the known location for user templates in **Tools** > **Options** > **Projects and Solutions** > **Locations**.
-
-## Next steps
-
-To learn more about .NET SDK templates and their locations, reference the following articles.
+### Change location for user templates
 
-|Article  |Description  |
-|---------|---------|
-|[.NET default templates](/dotnet/core/tools/dotnet-new-sdk-templates) | When you install the .NET SDK, you receive over a dozen built-in templates for creating projects and files, including console apps, class libraries, unit test projects, ASP.NET Core apps (including Angular and React projects), and configuration files.  This article lists the templates that come pre-installed with the .NET SDK and describes how to interact with them. |
-|[Manage .NET project and item templates](/dotnet/core/install/templates?pivots=os-windows&preserve-view=true) | .NET provides a template system that enables users to install or uninstall packages containing templates from NuGet, a NuGet package file, or a file system directory. This article describes how to manage .NET templates through the .NET SDK CLI. |
+You can change the location for user templates in Visual Studio with the **Tools** > **Options** dialog. The location settings are on the **Projects and Solutions** > **Locations** page.
 
 ## Related content
 
-- [Visual Studio template schema reference (extensibility)](../extensibility/visual-studio-template-schema-reference.md)
+- Review the [Visual Studio template schema reference (extensibility)](../extensibility/visual-studio-template-schema-reference.md)
+- Use [prebuilt templates installed with the .NET SDK](/dotnet/core/tools/dotnet-new-sdk-templates)
+- [Manage .NET project and item templates with the .NET SDK CLI](/dotnet/core/install/templates?pivots=os-windows&preserve-view=true)