Merge branch 'main' of github.com:MicrosoftDocs/visualstudio-docs-pr into msbuild-3283

Author: ghogen

.openpublishing.redirection.json

@@ -2523,6 +2523,16 @@
       "redirect_url": "/troubleshoot/developer/visualstudio/ide/troubleshooting-docker-errors",
       "redirect_document_id": false
     },
+    {
+      "source_path": "docs/test/using-microsoft-visualstudio-testtools-unittesting-members-in-unit-tests.md",
+      "redirect_url": "/dotnet/core/testing/unit-testing-mstest-writing-tests-attributes",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/test/using-the-assert-classes.md",
+      "redirect_url": "/dotnet/core/testing/unit-testing-mstest-writing-tests-assertions",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/test/analyzing-coded-ui-tests-using-coded-ui-test-logs.md",
       "redirect_url": "/previous-versions/visualstudio/visual-studio-2017/test/analyzing-coded-ui-tests-using-coded-ui-test-logs",

docs/containers/docker-compose-properties.md

@@ -50,7 +50,7 @@ In addition, the property `DockerComposeProjectPath` in a `.csproj` or `.vbproj`
 
 ## Example
 
-If you change the location of the `docker-compose` files, by setting `DockerComposeBaseFilePath` to a relative path, then you also need to make sure that the build context is changed so that it references the solution folder. For example, if your `docker-compose` file is a folder called *DockerComposeFiles*, then Docker Compose file should set the build context to ".." or "../..", depending on where it's relative to the solution folder.
+If you change the location of the `docker-compose` files, by setting `DockerComposeBaseFilePath` to a relative path, then you also need to make sure that the build context is changed so that it references the solution folder. For example, if your `docker-compose` file is a folder called *DockerComposeFiles*, then Docker Compose file should set the build context to ".." or "../..", depending on where it is relative to the solution folder.
 
 ```xml
 <?xml version="1.0" encoding="utf-8"?>

docs/debugger/debugger-cannot-display-source-code-or-disassembly.md

@@ -27,7 +27,7 @@ This error reads:
 
 - If you are debugging script, you may have hit a breakpoint while there were no threads in your program. Choose **Step** or **Continue** from the **Debug** menu to resume debugging.
 
-- Security considerations may have prevented the debugger from reading stack, thread, register, and other context information from the program you are debugging. This is most likely to happen if you are debugging a Web application and don't have the right permission to access the virtual directory. Set security for the virtual directory to Anonymous and try again.
+- Security considerations may have prevented the debugger from reading stack, thread, register, and other context information from the program you are debugging. This is most likely to happen if you are debugging a Web application and don't have the right permission to access the virtual directory. Set security for the virtual directory to Anonymous and try again. For more information about setting this in IIS, see [IIS](/aspnet/core/security/authentication/windowsauth?tabs=visual-studio#iis).
 
 ## Related content
 - [Debugging in Visual Studio](../debugger/index.yml)

docs/debugger/watch-and-quickwatch-windows.md

@@ -1,7 +1,7 @@
 ---
 title: Set a watch on variables and expressions
 description: While you debug, see variables and expressions in Watch and QuickWatch. Watch can display several variables, QuickWatch only one, and only while in break.
-ms.date: 04/25/2024
+ms.date: 02/10/2025
 ms.topic: how-to
 f1_keywords:
   - "vs.debug.quickwatch"
@@ -133,11 +133,11 @@ To make your search more or less thorough, use the **Search Deeper** dropdown at
 >[!NOTE]
 > This feature is supported in .NET Core 3.0 or higher.
 
-You can quickly inspect objects by their properties in the Watch window with the **Pinnable Properties** tool.  To use this tool, hover over a property and select the pin icon that appears or right-click and select the **Pin Member as Favorite** option in the resulting context menu.  This bubbles up that property to the top of the object’s property list, and the property name and value is displayed in the **Value** column.  To unpin a property, select the pin icon again or select the **Unpin Member as Favorite** option in the context menu.
+You can quickly inspect objects by their properties in the Watch window with the **Pinnable Properties** tool. To use this tool, hover over a property and select the pin icon that appears or right-click and select the **Pin Member as Favorite** option in the resulting context menu. This action bubbles up that property to the top of the object’s property list, and the property name and value is displayed in the **Value** column. To unpin a property, select the pin icon again or select the **Unpin Member as Favorite** option in the context menu.
 
 ![Screenshot of Pin properties in the Watch window.](../debugger/media/basic-pin-watch.gif "Pin properties in the Watch window")
 
-You can also toggle property names and filter out non-pinned properties when viewing the object’s property list in the Watch window.  You can access both options by selecting the buttons in the toolbar above the watch window.
+You can also toggle property names and filter out non-pinned properties when viewing the object’s property list in the Watch window. You can access both options by selecting the buttons in the toolbar above the watch window.
 
 ::: moniker-end
 
@@ -149,7 +149,7 @@ To refresh the value, select the refresh icon, or press the spacebar. The debugg
 
 Hover over the refresh icon or see the **Value** column for the reason the expression wasn't evaluated. Reasons include:
 
-- An error occurred as the expression was being evaluated, as in the previous example. A timeout might occur, or a variable might be out of scope.
+- An error occurred as the expression was being evaluated, as in the previous example. A  time-out might occur, or a variable might be out of scope.
 
 - The expression has a function call that could trigger a side effect in the app. See [Expression side effects](#bkmk_sideEffects).
 
@@ -209,7 +209,7 @@ For C# only, when evaluation of properties or implicit function calls is turned
 Sometimes you want to observe the behavior of a specific object. For example, you might want to track an object referred to by a local variable after that variable has gone out of scope. In C# and Visual Basic, you can create Object IDs for specific instances of reference types, and use them in the **Watch** window and in breakpoint conditions. The Object ID is generated by the common language runtime (CLR) debugging services and associated with the object.
 
 > [!NOTE]
-> Object IDs create weak references that don't prevent the object from being garbage collected. They are valid only for the current debugging session.
+> Object IDs create weak references that don't prevent the object from being garbage collected. They're valid only for the current debugging session.
 
 In the following code, the `MakePerson()` method creates a `Person` using a local variable:
 
@@ -353,10 +353,16 @@ To observe the `a` variable,
 
 1. To add the variable or expression from **QuickWatch** to the **Watch** window, select **Add Watch**.
 
-1. Select **Close** to close the **QuickWatch** window. (**QuickWatch** is a modal dialog, so you can't continue debugging as long as it is open.)
+1. Select **Close** to close the **QuickWatch** window. (**QuickWatch** is a modal dialog, so you can't continue debugging as long as it's open.)
 
 1. Continue debugging. You can observe the variable in the **Watch** window.
 
+::: moniker range=">= vs-2022"
+## Get AI assistance
+
+If you have [Copilot](../ide/visual-studio-github-copilot-extension.md), you can get AI assistance while you're looking at variables in the Watch windows. Right-click on a variable and use the **Ask Copilot** ![Screenshot of Ask Copilot button.](../debugger/media/vs-2022/debug-with-copilot-ask-copilot-button.png) button. In this scenario, Copilot already knows the context for your question, so you don't need to provide context yourself in chat. For more information, see [Debug with Copilot](../debugger/debug-with-copilot.md).
+::: moniker-end
+
 ## Related content
 - [What is debugging?](../debugger/what-is-debugging.md)
 - [Debugging techniques and tools](../debugger/write-better-code-with-visual-studio.md)

docs/deployment/application-deployment-prerequisites.md

@@ -1,7 +1,7 @@
 ---
 title: "Application Deployment Prerequisites"
 description: Learn about the deployment prerequisites for your applications, including using the Prerequisites Dialog Box and bootstrapper packages.
-ms.date: "09/23/2021"
+ms.date: "02/10/2025"
 ms.topic: "conceptual"
 dev_langs:
   - "FSharp"
@@ -21,16 +21,16 @@ ms.subservice: deployment
 ---
 # Application deployment prerequisites (Windows desktop)
 
-To have your Windows desktop application install and run successfully, first install all components upon which your application is dependent onto the target computer. For example, most applications created using Visual Studio have a dependency on the .NET Framework. In this case, the correct version of the common language runtime must be present on the destination computer before the application is installed.
+To successfully install and run a Windows desktop application, the components upon which your application depends must be installed onto the target computer. This article provides an overview of the installation of required components for [ClickOnce](../deployment/clickonce-security-and-deployment.md) and Windows Installer [Setup](../deployment/deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop-1) projects.
 
-You can select these prerequisites in the **Prerequisites Dialog Box** and install the .NET Framework and any other redistributable as a part of your installation. This practice is known as *bootstrapping*. Visual Studio generates a Windows executable program named *Setup.exe*, also known as a *bootstrapper*. The bootstrapper is responsible for installing these prerequisites before your application runs. For more information about selecting these prerequisites, see [Prerequisites dialog box](../ide/reference/prerequisites-dialog-box.md).
+You can select required components, called prerequisites, such as the .NET Framework and any other redistributable as a part of your installation. The process of installing prerequisites is known as *bootstrapping*. Visual Studio generates a Windows executable program named *Setup.exe*, also known as a *bootstrapper*. The bootstrapper is responsible for installing these prerequisites before your application runs. For more information about selecting these prerequisites, see [Prerequisites dialog box](../ide/reference/prerequisites-dialog-box.md).
 
-Each prerequisite is a bootstrapper package. A bootstrapper package is a group of directories and files containing the manifest files that describe how the prerequisites are installed. If your application prerequisites are not listed in the **Prerequisite Dialog Box**, you can create custom bootstrapper packages and add them to Visual Studio. Then you can select the prerequisites in the **Prerequisites Dialog Box**. For more information, see [Create bootstrapper packages](../deployment/creating-bootstrapper-packages.md).
+A *bootstrapper package* is a group of directories and files containing the manifest files that describe how the prerequisites are installed. Each prerequisite that appears in the **Prerequisites Dialog Box** is a bootstrapper package. If your application prerequisites aren't listed in the **Prerequisite Dialog Box**, you can create custom bootstrapper packages and add them to Visual Studio. Then you can select the prerequisites in the **Prerequisites Dialog Box**. For more information, see [Create bootstrapper packages](../deployment/creating-bootstrapper-packages.md).
 
-By default, bootstrapping is enabled for both Windows Installer deployment (by using Setup projects in Visual Studio) and ClickOnce deployment. The bootstrapper generated for Windows Installer deployment is not signed, but in ClickOnce deployment, the bootstrapper is signed. You can disable bootstrapping for a component, but you should do so only if you are sure that the correct version of the component is already installed on all target computers.
+By default, bootstrapping is enabled for both Windows Installer deployment (by using Setup projects in Visual Studio) and ClickOnce deployment. The bootstrapper generated for Windows Installer deployment isn't signed, but in ClickOnce deployment, the bootstrapper is signed. You can disable bootstrapping for a component, but you should do so only if you're sure that the correct version of the component is already installed on all target computers.
 
 ## Bootstrapping and ClickOnce deployment
- Before installing an application on a client computer, ClickOnce examines the client to ensure that it has the requirements specified in the application manifest. These include the following requirements:
+ Before installing an application on a client computer, ClickOnce examines the client to ensure that it has the requirements specified in the application manifest. These requirements include the following:
 
 - The minimum required version of the common language runtime, which is specified as an assembly dependency in the application manifest.
 
@@ -45,17 +45,12 @@ By default, bootstrapping is enabled for both Windows Installer deployment (by u
 
  If you use Visual Studio and ClickOnce to deploy your application, the bootstrapper packages that are selected by default depend on the version of the .NET Framework in the solution. However, if you change the target .NET Framework version, you must update the options in the **Prerequisites Dialog Box** manually.
 
-|Target .NET Framework|Selected Bootstrapper Packages|
-|---------------------------|------------------------------------|
-|.NET Framework 4 Client Profile|.NET Framework 4 Client Profile<br /><br /> Windows Installer 3.1|
-|.NET Framework 4|.NET Framework 4<br /><br /> Windows Installer 3.1|
-
  With ClickOnce deployment, the *Publish.htm* page generated by the ClickOnce Publish Wizard points either to a link that installs only the application, or to a link that installs both the application and the bootstrapped components.
 
  If you generate the bootstrapper by using the ClickOnce Publish Wizard or the Publish Page in Visual Studio, the *Setup.exe* is automatically signed. However, if you want to use your customer's certificate to sign the bootstrapper, you can sign the file later.
 
 ## Bootstrapping and MSBuild
- If you do not use Visual Studio, but rather compile your applications on the command line, you can create the ClickOnce bootstrapping application by using a Microsoft Build Engine (MSBuild) task. For more information, see [GenerateBootstrapper task](../msbuild/generatebootstrapper-task.md).
+ If you don't use Visual Studio, but rather compile your applications on the command line, you can create the ClickOnce bootstrapping application by using a Microsoft Build Engine (MSBuild) task. For more information, see [GenerateBootstrapper task](../msbuild/generatebootstrapper-task.md).
 
  As an alternative to bootstrapping, you can pre-deploy components using an electronic software distribution system, such as Microsoft Systems Management Server (SMS).
 
@@ -73,7 +68,7 @@ By default, bootstrapping is enabled for both Windows Installer deployment (by u
 | **-homesite=** `true` **&#124;** `false` | When `true`, downloads the dependencies from the preferred location on the vendor's site. This setting overrides the **-componentsurl** setting. When `false`, downloads the dependencies from the URL specified by **-componentsurl**. |
 
 ## Operating system support
- The Visual Studio bootstrapper is not supported on Windows Server 2008 Server Core or Windows Server 2008 R2 Server Core, as they provide a low-maintenance server environment with limited functionality. For example, the Server Core installation option only supports the .NET Framework 3.5 Server Core profile, which cannot run the Visual Studio features that depend on the full .NET Framework.
+ The Visual Studio bootstrapper isn't supported on Windows Server 2008 Server Core or Windows Server 2008 R2 Server Core, as they provide a low-maintenance server environment with limited functionality. For example, the Server Core installation option only supports the .NET Framework 3.5 Server Core profile, which can't run the Visual Studio features that depend on the full .NET Framework.
 
 ## Related content
 - [Choose a ClickOnce deployment strategy](../deployment/choosing-a-clickonce-deployment-strategy.md)

docs/deployment/index.yml

@@ -60,7 +60,7 @@ landingContent:
           - text: ClickOnce
             url: quickstart-deploy-using-clickonce-folder.md
           - text: Installer package
-            url: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop
+            url: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop-1
       - linkListType: how-to-guide
         links:
           - text: Package a desktop app for Windows Store
@@ -74,7 +74,7 @@ landingContent:
           - text: ClickOnce
             url: how-to-publish-a-clickonce-application-using-the-publish-wizard.md
           - text: Installer package
-            url: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop
+            url: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop-1
 
   # Card
   - title: Deploy to Azure

docs/deployment/toc.yml

@@ -226,7 +226,7 @@
       - name: Visual Studio Installer Projects Extension and .NET 6.0
         href: installer-projects-net-core.md
       - name: Create an installer package (Windows desktop)
-        href: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop
+        href: deploying-applications-services-and-components.md#create-an-installer-package-windows-desktop-1
     - name: Custom bootstrapper
       items:
       - name: Application deployment prerequisites

docs/extensibility/visualstudio.extensibility/editor/editor.md

@@ -43,6 +43,11 @@ Extensions can contribute new CodeLenses to the Visual Studio editor. A CodeLens
 
 For detailed walkthrough of how to provide your own CodeLens with your extension, refer to [Extending Visual Studio editor with a new CodeLens](./walkthroughs/codelens.md)
 
+### Taggers
+Extensions can contribute new taggers to the Visual Studio editor. Taggers are used to associate data with spans of text, such data is consumed by other Visual Studio features (E.g., CodeLens).
+
+For detailed walkthrough of how to provide your own taggers with your extension, refer to [Extending Visual Studio editor with a new tagger](./walkthroughs/taggers.md)
+
 ## Related content
 
 Learn about the editor interfaces and types at [Editor concepts](editor-concepts.md).