Merged main into live

Author: mijacobs

docs/debugger/configure-the-windows-firewall-for-remote-debugging.md

@@ -94,11 +94,11 @@ If you select **Use Managed Compatibility Mode** under **Tools** > **Options** >
 
 ::: moniker-end
 
-If your domain policy requires network communication to be performed through Internet Protocol Security (IPSec), you must open additional ports on both the Visual Studio and remote computers. To debug on a remote Internet Information Services (IIS) web server, open port 80 on the remote computer.
+If your domain policy requires network communication to be performed through Internet Protocol Security (IPsec), you must open additional ports on both the Visual Studio and remote computers. To debug on a remote Internet Information Services (IIS) web server, open port 80 on the remote computer.
 
 |**Ports**|**Incoming/Outgoing**|**Protocol**|**Description**|
 |-|-|-|-|
-|500, 4500|Outgoing|UDP|Required if your domain policy requires network communication to be performed through IPSec.|
+|500, 4500|Outgoing|UDP|Required if your domain policy requires network communication to be performed through IPsec.|
 |80|Outgoing|TCP|Required for web server debugging.|
 
 To allow specific apps through the Windows Firewall, see [Configure remote debugging through Windows Firewall](#allow-the-remote-debugger-through-windows-firewall).

docs/debugger/how-to-enable-and-disable-edit-and-continue.md

@@ -1,7 +1,7 @@
 ---
 title: Configure Edit and Continue
 description: Learn how to enable, disable, and configure Edit and Continue, in Visual Studio Options at design time. Edit and Continue works only in debug builds.
-ms.date: 02/22/2023
+ms.date: 01/24/2025
 ms.topic: how-to
 dev_langs: 
   - CSharp
@@ -56,13 +56,13 @@ Or, open **Tools** > **Options** > **Debugging** > **.NET/C++ Hot Reload**.
 
 The settings for Hot Reload include:
 
-* **Enable Hot Reload and Edit and Continue when debugging**. Enables Hot Reload when starting with the debugger attached (F5).
+- **Enable Hot Reload**. Enables Hot Reload when starting with the debugger attached (F5).
 
-* **Enable Hot Reload when starting without debugging**. Enables Hot Reload when starting without the debugger attached (Ctrl+F5).
+- **Enable Hot Reload when starting without debugging**. Enables Hot Reload when starting without the debugger attached (Ctrl+F5).
 
-* **Apply Hot Reload on File Save**. Applies code changes when you save the file.
+- **Apply Hot Reload on File Save**. Applies code changes when you save the file.
 
-* **Logging Verbosity**. Filters amount of information displayed in the Hot Reload Output window.
+- **Logging Verbosity**. Filters amount of information displayed in the Hot Reload Output window.
 
 ![Screenshot of settings for .NET Hot Reload.](../debugger/media/vs-2022/dotnet-hot-reload-settings.png)
 

docs/debugger/how-to-enable-debugging-for-aspnet-applications.md

@@ -22,7 +22,7 @@ ms.subservice: debug-diagnostics
 You can debug ASP.NET and ASP.NET Core apps in Visual Studio. The process differs between ASP.NET and ASP.NET Core, and whether you run it on IIS Express or a local IIS server.
 
 >[!NOTE]
->The following steps and settings apply only to debugging apps on a local server. Debugging apps on a remote IIS server uses **Attach to Process**, and ignores these settings. For more information and instructions for remote debugging ASP.NET apps on IIS, see [Remote debug ASP.NET on an IIS computer](../debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md) or [Remote debug ASP.NET Core on a remote IIS computer](../debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md).
+>The following steps and settings apply only to debugging apps on a local server. Debugging apps on a remote IIS server uses **Attach to Process**, and ignores these settings. For more information and instructions for remote debugging ASP.NET and ASP.NET Core, see [Remote debug ASP.NET Core on a remote IIS computer](../debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md), and [Remote debug Azure App Service](../debugger/remote-debugging-azure-app-service.md).
 
 ::: moniker range=">=vs-2022"
 The built-in Kestrel and IIS Express servers are included with Visual Studio. Kestrel is the default debug server for ASP.NET Core projects, and is preconfigured. IIS Express is the default debug server for ASP.NET.
@@ -43,7 +43,7 @@ You can also debug an ASP.NET or ASP.NET Core app on a local IIS server (version
 
 - Run Visual Studio as an administrator.
 - Install and correctly configure IIS with the appropriate version(s) of ASP.NET and/or ASP.NET Core. For more information on using IIS with ASP.NET Core, see [Host ASP.NET Core on Windows with IIS](/aspnet/core/host-and-deploy/iis/index). For ASP.NET, see [Install IIS and ASP.NET Modules](/iis/application-frameworks/scenario-build-an-aspnet-website-on-iis/configuring-step-1-install-iis-and-asp-net-modules).
-- Make sure the app runs on IIS without errors.
+- Make sure the app runs on IIS and opens in the browser.
 
 ::: moniker range=">=vs-2022"
 ## Debug ASP.NET Core apps

docs/debugger/includes/remote-debugger-requirements.md

@@ -31,9 +31,6 @@ The remote computer must be running one of the following operating systems:
 - Windows Server 2012 or Windows Server 2012 R2  
 
 - Windows Server 2008 Service Pack 2, Windows Server 2008 R2 Service Pack 1
-
-> [!NOTE]
-> Windows Phone requires a USB connection to debug (it does not require the remote tools).
 
 ### Supported Hardware Configurations  
 

docs/debugger/media/vs-2022/dotnet-hot-reload-settings.png

@@ -26,13 +26,13 @@ For in-depth instructions on remote debugging, see these topics.
 
 |Scenario|Link|
 |-|-|
-|Azure App Service|[Remote debug ASP.NET Core on Azure](../debugger/remote-debugging-azure-app-service.md) or, for Visual Studio Enterprise, the [Snapshot Debugger](../debugger/debug-live-azure-applications.md)|
-|Azure VM|[Remote debug ASP.NET on an Azure VM](../debugger/remote-debugging-azure.md)|
-|ASP.NET|[Remote debug ASP.NET Core](../debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md) or [Remote Debug ASP.NET](../debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md)|
 |C# or Visual Basic|[Remote debug a C# or Visual Basic project](../debugger/remote-debugging-csharp.md)|
 |C++|[Remote debug a C++ project](../debugger/remote-debugging-cpp.md)|
-|Docker|[Attach to a process running in a Docker container](../debugger/attach-to-process-running-in-docker-container.md)|
+|Azure App Service|[Remote debug ASP.NET Core on Azure](../debugger/remote-debugging-azure-app-service.md) or, for Visual Studio Enterprise, the [Snapshot Debugger](../debugger/debug-live-azure-applications.md)|
+|ASP.NET|[Remote debug ASP.NET Core](../debugger/remote-debugging-aspnet-on-a-remote-iis-computer.md) or [Remote Debug ASP.NET](../debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md)|
+|Azure VM|[Remote debug ASP.NET on an Azure VM](../debugger/remote-debugging-azure.md)|
 |Linux|[Debug .NET Core on Linux using SSH by attaching to a process](../debugger/remote-debugging-dotnet-core-linux-with-ssh.md)|
+|Docker|[Attach to a process running in a Docker container](../debugger/attach-to-process-running-in-docker-container.md)|
 |Universal Windows Apps (UWP)|[Run UWP apps on a remote machine](../debugger/run-windows-store-apps-on-a-remote-machine.md) or [Debug an installed app package](../debugger/debug-installed-app-package.md)|
 
 If you just want to download and install the remote debugger and don't need any additional instructions for your scenario, follow the steps in this article.
@@ -88,13 +88,21 @@ You can change some aspects of the configuration of the remote debugger after yo
 
      Alternatively, you can start the remote debugger from the command line with the **/allow \<username>** parameter: **msvsmon /allow \<username@computer>**.
 
-- If you need to change the Authentication mode or the port number, or specify a timeout value for the remote tools: choose **Tools > Options**.
+- If you need to change the Authentication mode or the port number, or specify a time-out value for the remote tools: choose **Tools > Options**.
 
      For a listing of the port numbers used by default, see [Remote Debugger Port Assignments](../debugger/remote-debugger-port-assignments.md).
 
      > [!WARNING]
      > You can choose to run the remote tools in No Authentication mode, but this mode is strongly discouraged. There's no network security when you run in this mode. Choose the No Authentication mode only if you're sure that the network isn't at risk from malicious or hostile traffic.
 
+## Configure Visual Studio for remote debugging
+
+For detailed instructions to connect to the app from Visual Studio, use the links related to your specific scenario at the beginning of this article.
+
+Some scenarios require the use of Attach to Process to connect to a remote app that is already started. However, for .NET Core, .NET 5+, .NET Framework, and C++ apps, you can start the remote app from Visual Studio by configuring project properties and starting the debugger. For more information, see [Remote debug a C# or Visual Basic project](../debugger/remote-debugging-csharp.md) or [Remote debug a C++ project](../debugger/remote-debugging-cpp.md).
+
+You can also remote debug an executable that is not part of a Visual Studio project, although the supported debugging features depend on configuration such as the availability of symbols. For more information, see [Debug an app that isn't part of a Visual Studio solution](../debugger/how-to-debug-an-executable-not-part-of-a-visual-studio-solution.md).
+
 ## <a name="bkmk_configureService"></a> (Optional) Configure the remote debugger as a service
 
 For debugging in ASP.NET and other server environments, you must either run the remote debugger as an Administrator or, if you want it always running,  run the remote debugger as a service.

docs/debugger/remote-debugging.md

@@ -100,13 +100,13 @@ function Foo(param1) {
 }
 ```
 
-See the JsDoc information in [Type Checking JavaScript Files](https://www.typescriptlang.org/docs/handbook/type-checking-javascript-files.html#supported-jsdoc) for the JsDoc annotations currently supported.
+See the JSDoc information in [Type Checking JavaScript Files](https://www.typescriptlang.org/docs/handbook/type-checking-javascript-files.html#supported-jsdoc) for the JSDoc annotations currently supported.
 
 ## IntelliSense based on TypeScript declaration files
 
-Because JavaScript and TypeScript are based on the same language service, they are able to interact in a rich way. For example, JavaScript IntelliSense can be provided for values declared in a *.d.ts* file (see [TypeScript documentation](https://www.typescriptlang.org/docs/handbook/declaration-files/introduction.html)), and types such as interfaces and classes declared in TypeScript are available for use as types in JsDoc comments.
+Because JavaScript and TypeScript are based on the same language service, they are able to interact in a rich way. For example, JavaScript IntelliSense can be provided for values declared in a *.d.ts* file (see [TypeScript documentation](https://www.typescriptlang.org/docs/handbook/declaration-files/introduction.html)), and types such as interfaces and classes declared in TypeScript are available for use as types in JSDoc comments.
 
-Below, we show a simple example of a TypeScript definition file providing such type information (via an interface) to a JavaScript file in the same project (using a `JsDoc` tag).
+Below, we show a simple example of a TypeScript definition file providing such type information (via an interface) to a JavaScript file in the same project (using a `JSDoc` tag).
 
 ![TypeScript definition file](https://raw.githubusercontent.com/wiki/Microsoft/TypeScript/images/decl1.png)
 

docs/ide/javascript-intellisense.md

@@ -73,11 +73,11 @@ For this example, you use an empty ASP.NET Core Application (C#). However, you c
     app.UseStaticFiles(); // Marks files on the web root as servable.
     ```
 
-### Install the vue CLI
+### Install the Vue CLI
 
 To install the vue-cli npm module, open a command prompt and type `npm install --g vue-cli` or `npm install -g @vue/cli` for version 3.0 (currently in beta).
 
-### Scaffold a new client application using the vue CLI
+### Scaffold a new client application using the Vue CLI
 
 1. Go to your command prompt and change the current directory to your project root folder.
 
@@ -121,7 +121,7 @@ These steps require vue-cli 3.0, which is currently in beta.
 
 1. Type `vue create client-app`, and then choose **Manually select features**.
 
-1. Choose **Typescript**, and then select other desired options.
+1. Choose **TypeScript**, and then select other desired options.
 
 1. Follow the remaining steps and respond to the questions.
 

docs/javascript/create-application-with-vuejs.md

@@ -51,7 +51,7 @@ The complete code is in the *PetReaderExecTaskExample* folder; you can download
 
 1. In the `PetShopRestClient` project, add a folder (named `PetShopRestClient`) for the code generation and delete the *Class1.cs* that was automatically generated.
 
-1. Create a text file named *petshop-openapi-spec.json* at the root of the project. Copy the OpenApi spec from [here](https://petstore.swagger.io/v2/swagger.json) and save it in the file. It's best to copy a snapshot of the spec instead of reading it online during the build. You always want a consistently reproducible build that depends only on the input. Consuming the API directly could transform a build which works today to a build which fails tomorrow from the same source. The snapshot saved on *petshop-openapi-spec.json* will allow us to still have a version that builds even if the spec changes.
+1. Create a text file named *petshop-openapi-spec.json* at the root of the project. Copy the OpenAPI spec from [here](https://petstore.swagger.io/v2/swagger.json) and save it in the file. It's best to copy a snapshot of the spec instead of reading it online during the build. You always want a consistently reproducible build that depends only on the input. Consuming the API directly could transform a build which works today to a build which fails tomorrow from the same source. The snapshot saved on *petshop-openapi-spec.json* will allow us to still have a version that builds even if the spec changes.
 
 1. Next, modify PetShopRestClient.csproj and add a [MSBuild targets](msbuild-targets.md) to generate the client during build process.
 
@@ -121,7 +121,7 @@ Congratulations! Now, you can execute the program to see how it works.
 
 In many cases, using the `Exec` task is good enough to execute an external tool to do something like REST API client code generation, but what if you want to allow REST API client code generation if and only if you don't use an absolute Windows path as input? Or what if you need to calculate in some way where the executable is? When there's any situation where you need to execute some code to do extra work, the [MSBuild Tool Task](/dotnet/api/microsoft.build.utilities.tooltask) is the best solution. The `ToolTask` class is an abstract class derived from MSBuild `Task`. You can define a concrete subclass, which creates a custom MSBuild task. This approach lets you run any code that is needed to prepare for command execution. You should read the tutorial [Create a custom task for code generation](tutorial-custom-task-code-generation.md) first.
 
-You'll create a custom task derived from [MSBuild ToolTask](/dotnet/api/microsoft.build.utilities.tooltask) which will generate a REST API client, but it will be designed to emit an error if you try to reference the OpenApi spec using an http address. NSwag supports an http address as OpenApi spec input, but for the purposes of this example, let's suppose there's a design requirement to disallow that.
+You'll create a custom task derived from [MSBuild ToolTask](/dotnet/api/microsoft.build.utilities.tooltask) which will generate a REST API client, but it will be designed to emit an error if you try to reference the OpenAPI spec using an http address. NSwag supports an http address as OpenAPI spec input, but for the purposes of this example, let's suppose there's a design requirement to disallow that.
 
 The complete code is in this `PetReaderToolTaskExample` folder; you can download and take a look. In this tutorial, you'll go through step by step and learn some concepts that you can apply to your own scenarios.
 
@@ -237,7 +237,7 @@ The next step is to create an app that uses the task.
    - Newtonsoft.Json, needed to compile the generated client
    - System.ComponentModel.Annotations, needed to compile the generated client
 
-1. In the `PetRestApiClient` project, create a text file named *petshop-openapi-spec.json* (in the project folder). To add the OpenApi spec, copy the content from [here](https://petstore.swagger.io/v2/swagger.json) into the file. We like a reproducible build that depends only on the input, as discussed previously. In this example, you'll raise a build error if a user chooses a URL as the OpenApi spec input.
+1. In the `PetRestApiClient` project, create a text file named *petshop-openapi-spec.json* (in the project folder). To add the OpenAPI spec, copy the content from [here](https://petstore.swagger.io/v2/swagger.json) into the file. We like a reproducible build that depends only on the input, as discussed previously. In this example, you'll raise a build error if a user chooses a URL as the OpenAPI spec input.
 
    > [!IMPORTANT]
    > A general rebuild won't work. You'll see errors that indicate it's unable to copy or delete `RestApiClientGenerator`.dll'. This is because it's trying to build the MBuild custom task in the same build process which uses it. Select `PetReaderToolTaskConsoleApp` and rebuild only that project. The another solution is put the custom task in a completely independent Visual Studio solution as you did in [Tutorial: Create a custom task](tutorial-custom-task-code-generation.md) example.
@@ -276,7 +276,7 @@ The next step is to create an app that uses the task.
 
       ```xml
        <PropertyGroup>
-          <!--The place where the OpenApi spec is in-->
+          <!--The place where the OpenAPI spec is in-->
          <PetClientInputOpenApiSpec>petshop-openapi-spec.json</PetClientInputOpenApiSpec>
          <PetClientClientClassName>PetRestApiClient</PetClientClientClassName>
          <PetClientClientNamespaceName>PetRestApiClient</PetClientClientNamespaceName>

docs/msbuild/tutorial-rest-api-client-msbuild.md

@@ -4,7 +4,7 @@ author: joseb-rdc
 ms.author: amast
 manager: shve
 ms.assetid: e49242bc-e9f2-49e8-8caa-f574d508aba6
-ms.date: 09/16/2024
+ms.date: 01/24/2025
 ms.topic: how-to
 description:  Learn how admins can delete subscription assignments in the Visual Studio Subscriptions Admin Portal.
 ---
@@ -18,7 +18,7 @@ When a subscriber no longer requires a Visual Studio subscription, you can remov
 
 Watch this video or read on to learn how to delete assignments. 
 
-> [!VIDEO https://learn-video.azurefd.net/vod/player?id=f7d7388b-d823-4020-9f04-baaa1677e3d7]
+> [!VIDEO https://www.microsoft.com/videoplayer/embed/RE4yG2q]
 
 ## Delete a subscription assignment