Merged main into live

Author: mijacobs

docs/containers/tutorial-multicontainer.md

@@ -218,8 +218,6 @@ Add a project to the same solution and call it *MyWebAPI*. Select **API** as the
    The *docker-compose.yml* appears as follows:
 
    ```yaml
-   version: '3.4'
-
     services:
       webfrontend:
         image: ${DOCKER_REGISTRY-}webfrontend
@@ -242,8 +240,6 @@ Add a project to the same solution and call it *MyWebAPI*. Select **API** as the
     Visual Studio makes some changes to your Docker Compose YML file. Now both services are included.
 
     ```yaml
-    version: '3.4'
-
     services:
       webfrontend:
         image: ${DOCKER_REGISTRY-}webfrontend
@@ -344,8 +340,6 @@ Congratulations, you're running a Docker Compose application with a custom Docke
    The *docker-compose.yml* appears as follows:
 
    ```yaml
-   version: '3.4'
-
     services:
       webfrontend:
         image: ${DOCKER_REGISTRY-}webfrontend
@@ -368,8 +362,6 @@ Congratulations, you're running a Docker Compose application with a custom Docke
     Visual Studio makes some changes to your `docker-compose` YML file. Now both services are included.
 
     ```yaml
-    version: '3.4'
-
     services:
       webfrontend:
         image: ${DOCKER_REGISTRY-}webfrontend

docs/debugger/debugging-absolute-beginners.md

@@ -77,7 +77,9 @@ Next, you create an application that has a few bugs.
 
 1. Open Visual Studio.
 
-    On the start window, choose **Create a new project**. Type **console** in the search box, select either **C#** or **Visual Basic** as the language, and then choose **Console App** for .NET. Choose **Next**. Type a project name like **ConsoleApp_FirstApp** and select **Next**.
+    On the start window, choose **Create a new project**. Type **console** in the search box, select either **C#** or **Visual Basic** as the language, and then choose **Console App** for .NET. Choose **Next**. Type **ConsoleApp_FirstApp** as the project name and select **Next**.
+
+    If you use a different project name, you will need to modify the namespace value to match your project name when you copy the example code.
 
     Choose either the recommended target framework or .NET 8, and then choose **Create**.
 

docs/extensibility/internals/command-implementation.md

@@ -25,26 +25,25 @@ The following sections explain how to register and implement commands.
 ## Register commands with Visual Studio
  If your command is to appear on a menu, you must add the <xref:Microsoft.VisualStudio.Shell.ProvideMenuResourceAttribute> to your VSPackage, and use as a value either the name of the menu or its resource ID.
 
-```
+```c#
 [ProvideMenuResource("Menus.ctmenu", 1)]
-...
-    public sealed class MyPackage : Package
-    {.. ..}
-
+public sealed class MyPackage : Package
+{
+    // ...
+}
 ```
 
  In addition, you must register the command with the <xref:Microsoft.VisualStudio.Shell.OleMenuCommandService>. You can get this service by using the <xref:Microsoft.VisualStudio.Shell.Package.GetService%2A> method if your VSPackage is derived from <xref:Microsoft.VisualStudio.Shell.Package>.
 
-```
+```c#
 OleMenuCommandService mcs = GetService(typeof(IMenuCommandService)) as OleMenuCommandService;
-if ( null != mcs )
+if (mcs is not null)
 {
     // Create the command for the menu item.
     CommandID menuCommandID = new CommandID(guidCommandGroup, myCommandID);
-    MenuCommand menuItem = new MenuCommand(MenuItemCallback, menuCommandID );
-    mcs.AddCommand( menuItem );
+    MenuCommand menuItem = new MenuCommand(MenuItemCallback, menuCommandID);
+    mcs.AddCommand(menuItem);
 }
-
 ```
 
 ## Implement commands

docs/extensibility/roslyn-version-support.md

@@ -18,7 +18,9 @@ As an example, to ensure that your custom analyzer works on all versions of Visu
 
 | Roslyn package version | Minimum supported Visual Studio version |
 | - | - |
-| 4.8.0 | Visual Studio 2022 version 17.8 (Preview) |
+| 4.10.0 | Visual Studio 2022 version 17.10 |
+| 4.9.2 | Visual Studio 2022 version 17.9 |
+| 4.8.0 | Visual Studio 2022 version 17.8 |
 | 4.7.0 | Visual Studio 2022 version 17.7 |
 | 4.6.0 | Visual Studio 2022 version 17.6 |
 | 4.5.0 | Visual Studio 2022 version 17.5 |

docs/ide/how-to-sign-application-and-deployment-manifests.md

@@ -21,7 +21,7 @@ manager: mijacobs
 
 If you want to publish an application by using ClickOnce deployment, the application and deployment manifests must be signed with a public/private key pair and signed using Authenticode technology. You can sign the manifests by using a certificate from the Windows certificate store or a key file.
 
-The information in this article applies only if you're using the .NET Framework 4.7.2 or earlier. If you're using .NET 5 or later, follow the steps in [Deploy a .NET Windows desktop application using ClickOnce](../deployment/quickstart-deploy-using-clickonce-folder.md).
+The information in this article applies only if you're using the .NET Framework 4.8.1 or earlier. If you're using .NET 5 or later, follow the steps in [Deploy a .NET Windows desktop application using ClickOnce](../deployment/quickstart-deploy-using-clickonce-folder.md).
 
 For more information about ClickOnce deployment, see [ClickOnce security and deployment](../deployment/clickonce-security-and-deployment.md).
 

docs/ide/reference/how-to-manage-word-wrap-in-the-editor.md

@@ -43,8 +43,8 @@ You can set and clear the **Word wrap** option. When this option is set, the por
 
 If you're familiar with word wrap in Notepad++, Sublime Text, or Visual Studio Code (VS Code), be aware of the following issues where Visual Studio behaves differently to other editors:
 
-* [Triple-click doesn't select whole line](https://developercommunity.visualstudio.com/t/fix-known-issues-in-word-wrap/351760)
-* [Pressing End key twice doesn't move cursor to end of line](https://developercommunity.visualstudio.com/t/fix-known-issues-in-word-wrap/351760)
+* [Unexpected and sporadic indents](https://developercommunity.visualstudio.com/t/Unexpected-and-sporadic-indents-when-usi/10635809)
+* [Pressing Home key twice should move cursor to very beginning of line](https://developercommunity.visualstudio.com/t/Pressing-Home-key-twice-should-move-curs/10635835)
 
 ## Related content
 

docs/javascript/debug-nodejs.md

@@ -176,7 +176,7 @@ with this code:
 ```javascript
   output: {
     filename: "./app-bundle.js", // Replace with the filename in your project
-    devtoolModuleFilenameTemplate: '[resource-path]'  // Removes the webpack:/// prefix
+    devtoolModuleFilenameTemplate: '[absolute-resource-path]'  // Removes the webpack:/// prefix
   },
 ```
 

docs/test/configure-unit-tests-by-using-a-dot-runsettings-file.md

@@ -164,7 +164,7 @@ The **RunConfiguration** element can include the following elements:
 |**TreatTestAdapterErrorsAsWarnings**|false|false, true|
 |**TestAdaptersPaths**||One or more paths to the directory where the TestAdapters are located|
 |**TestCaseFilter**|| A filter expression in the format \<property>\<operator>\<value>[\|\&amp;\<Expression>]. The boolean operator **\&** should be represented by the HTML entity **\&amp;**. Expressions can be enclosed in parentheses. For detailed syntax on expression structure, see [vstest/docs/filter.md](https://github.com/microsoft/vstest/blob/main/docs/filter.md). |
-|**TestSessionTimeout**||Allows users to terminate a test session when it exceeds a given timeout. Setting a timeout ensures that resources are well consumed and test sessions are constrained to a set time. The setting is available in **Visual Studio 2017 version 15.5** and later.|
+|**TestSessionTimeout**||Allows users to terminate a test session when it exceeds a given timeout, specified in milliseconds. Setting a timeout ensures that resources are well consumed and test sessions are constrained to a set time. The setting is available in **Visual Studio 2017 version 15.5** and later.|
 |**DotnetHostPath**||Specify a custom path to dotnet host that is used to run the testhost. It's useful when you're building your own dotnet, for example when building the dotnet/runtime repository. Specifying this option skips looking for testhost.exe, and forces the use of testhost.dll.|
 |**TreatNoTestsAsError**|false| true or false <br>Specify a Boolean value, which defines the exit code when no tests are discovered. If the value is `true` and no tests are discovered, a nonzero exit code is returned. Otherwise, zero is returned.|
 

docs/test/remote-testing.md

@@ -78,16 +78,16 @@ For a Dockerfile, the environment can be specified in the *testEnvironments.json
 }
 ```
 
-The following example shows the *testenvironments.json* file for a local container image named `<mcr.microsoft.com/dotnet/core/sdk>`.
+The following example shows the *testenvironments.json* file for a local container image named `<mcr.microsoft.com/dotnet/sdk>`.
 
 ```json
 {
     "version": "1",
     "environments": [
         {
-            "name": "linux dotnet-core-sdk-3.1",
+            "name": "linux dotnet-sdk-5.0",
             "type": "docker",
-            "dockerImage": "mcr.microsoft.com/dotnet/core/sdk"
+            "dockerImage": "mcr.microsoft.com/dotnet/sdk"
         }
     ]
 }
@@ -96,7 +96,7 @@ The following example shows the *testenvironments.json* file for a local contain
 The following example shows a Dockerfile for running tests targeting .NET 5.0. The second line makes sure the debugger can connect and run in your container.
 
 ```dockerfile
-FROM mcr.microsoft.com/dotnet/core/sdk:5.0
+FROM mcr.microsoft.com/dotnet/sdk:5.0
 
 RUN wget https://aka.ms/getvsdbgsh && \
     sh getvsdbgsh -v latest  -l /vsdbg