Merge pull request #14342 from Mikejo5000/mikejo-br27

Update paths for PS, debugger

Author: v-regandowner

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

@@ -46,6 +46,15 @@ To open a port using PowerShell:
 
 For Windows Firewall, you can use PowerShell commands such as [New-NetFirewallRule](/powershell/module/netsecurity/new-netfirewallrule).
 
+::: moniker range="visualstudio"
+The following example opens port 4026 for the remote debugger on the remote computer. The port and path you need to use might be different.
+
+```ps
+New-NetFirewallRule -DisplayName "msvsmon" -Direction Inbound -Program "Program Files\Microsoft Visual Studio\18\Enterprise\Common7\IDE\Remote Debugger\x64\msvsmon.exe" -LocalPort 4026 -Protocol TCP -Authentication Required -Action Allow
+```
+
+::: moniker-end
+
 ::: moniker range="vs-2022"
 The following example opens port 4026 for the remote debugger on the remote computer. The port and path you need to use might be different.
 

docs/debugger/using-the-intellitrace-stand-alone-collector.md

@@ -71,8 +71,12 @@ The **IntelliTrace stand-alone collector** lets you collect IntelliTrace diagnos
 2. Get the collector from the Visual Studio installation folder.
 
    1. Copy IntelliTraceCollection.cab from the folder where the collector is installed, for example:
-
+        ::: moniker range=">=visualstudio"
+        **..\Microsoft Visual Studio\18\Enterprise\Common7\IDE\CommonExtensions\Microsoft\IntelliTrace**
+        ::: moniker-end
+        ::: moniker range="<=vs-2022"
         **..\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\CommonExtensions\Microsoft\IntelliTrace**
+        ::: moniker-end
 
         or, for previous versions of Visual Studio:
 

docs/ide/reference/command-prompt-powershell.md

@@ -3,7 +3,7 @@ title: Command-Line Shells & Prompt For Developers
 description: Learn about the two command-line shells for developers in Visual Studio, the Developer Command Prompt and the Developer PowerShell.
 author: Mikejo5000
 ms.author: mikejo
-ms.date: 08/06/2025
+ms.date: 09/23/2025
 ms.topic: conceptual
 helpviewer_keywords:
   - "Visual Studio command prompt"
@@ -149,6 +149,15 @@ Since Visual Studio 2015, the Developer Command Prompt sets the `VSCMD_VER` envi
 
 Search for a PowerShell script file named *Launch-VsDevShell.ps1*, or go to the Tools folder for Visual Studio, such as *%ProgramFiles(x86)%\Microsoft Visual Studio\2019\Community\Common7\Tools*. The path changes according to your Visual Studio version, edition, and installation location. After you locate the PowerShell file, run it by entering the following command at a Windows PowerShell or PowerShell 6 prompt.
 
+::: moniker range="visualstudio"
+For Visual Studio 2022:
+
+```powershell
+& 'C:\Program Files\Microsoft Visual Studio\18\Community\Common7\Tools\Launch-VsDevShell.ps1'
+```
+
+::: moniker-end
+
 ::: moniker range="vs-2022"
 For Visual Studio 2022:
 

docs/javascript/unit-testing-javascript-with-visual-studio.md

@@ -115,7 +115,7 @@ The following example is based on the TypeScript React project template provided
    > For TypeScript, don't use the `outfile` option in *tsconfig.json*, because Test Explorer won't be able to find your unit tests. You can use the `outdir` option, but make sure that configuration files such as `package.json` and `tsconfig.json` are in the project root.
 
    > [!IMPORTANT]
-   > If the output from **Tests** in the Output window shows a `ReadOnlySpan` error during test discovery, use the following workaround for a known [MSBuild issue](https://github.com/dotnet/msbuild/issues/7873). Open the folder, *Program Files\Microsoft Visual Studio\2022\\<version\>\Common7\IDE\Extensions\TestPlatform*, and rename *System.Memory.dll* to a different name. This fix enables test discovery.
+   > If the output from **Tests** in the Output window shows a `ReadOnlySpan` error during test discovery, use the following workaround for a known [MSBuild issue](https://github.com/dotnet/msbuild/issues/7873). For Visual Studio 2022, open the folder, *Program Files\Microsoft Visual Studio\2022\\<version\>\Common7\IDE\Extensions\TestPlatform*, and rename *System.Memory.dll* to a different name. This fix enables test discovery.
 
 ### Run tests (.esproj)
 
@@ -139,10 +139,17 @@ You can run unit tests directly from the command line for your unit test framewo
 
 You may also choose to run the tests from the command line using *vstest.console*. For example, you may want to use vstest.console to maintain consistency with C# unit tests, or to run in Azure DevOps. Use the following command, but replace `MyProj` with your project name.
 
+::: moniker-end
+::: moniker range=">=visualstudio"
 ```
-vstest.console .\MyProj.esproj /TestAdapterPath:"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\Extensions\Microsoft\JavaScript"
+vstest.console .\MyProj.esproj /TestAdapterPath:"C:\Program Files\Microsoft Visual Studio\18\Enterprise\Common7\IDE\Extensions\Microsoft\JavaScript"
 ```
+::: moniker-end
 
+::: moniker range="vs-2022"
+```
+vstest.console .\MyProj.esproj /TestAdapterPath:"C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\Extensions\Microsoft\JavaScript"
+```
 ::: moniker-end
 
 ## Write unit tests for ASP.NET Core
@@ -366,7 +373,7 @@ The following example is based on the ASP.NET Core Model-View-Controller project
 
    ::: moniker range="vs-2022"
    > [!IMPORTANT]
-   > If the output from **Tests** in the Output window shows a `ReadOnlySpan` error during test discovery, use the following workaround for a known [MSBuild issue](https://github.com/dotnet/msbuild/issues/7873). Open the folder, *Program Files\Microsoft Visual Studio\2022\\<version\>\Common7\IDE\Extensions\TestPlatform*, and rename *System.Memory.dll* to a different name. This fix enables test discovery.
+   > If the output from **Tests** in the Output window shows a `ReadOnlySpan` error during test discovery, use the following workaround for a known [MSBuild issue](https://github.com/dotnet/msbuild/issues/7873). In Visual Studio 2022, open the folder, *Program Files\Microsoft Visual Studio\2022\\<version\>\Common7\IDE\Extensions\TestPlatform*, and rename *System.Memory.dll* to a different name. This fix enables test discovery.
    ::: moniker-end
 
 ### Run tests (ASP.NET Core)

docs/profiling/profile-apps-from-command-line.md

@@ -40,7 +40,10 @@ Profiling using the Visual Studio Diagnostics CLI tools works by attaching the p
 
 1. Open a command prompt and change to the directory with the collection agent executable, typically here (for Visual Studio Enterprise).
 
-   ::: moniker range=">= vs-2022"
+   ::: moniker range=">=visualstudio"
+   `<Visual Studio installation folder>\18\Enterprise\Team Tools\DiagnosticsHub\Collector\`
+   ::: moniker-end
+   ::: moniker range="vs-2022"
    `<Visual Studio installation folder>\2022\Enterprise\Team Tools\DiagnosticsHub\Collector\`
    ::: moniker-end
    ::: moniker range="vs-2019"

docs/test/migrate-testsettings-to-runsettings.md

@@ -13,7 +13,10 @@ ms.subservice: test-tools
 # Upgrade from .testsettings to .runsettings
 
 You can upgrade your test configuration file from *.testsettings* to *.runsettings* with the SettingsMigrator tool that installs along with Visual Studio. Depending on your Visual Studio install location, you can find the settings migrator tool in the following path:
-::: moniker range=">=vs-2022"
+::: moniker range=">=visualstudio"
+`C:\Program Files\Microsoft Visual Studio\18\Enterprise\Common7\IDE\Extensions\TestPlatform\SettingsMigrator.exe`
+::: moniker-end
+::: moniker range="vs-2022"
 `C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\Extensions\TestPlatform\SettingsMigrator.exe`
 ::: moniker-end
 ::: moniker range="vs-2019"

docs/test/using-code-coverage-to-determine-how-much-code-is-being-tested.md

@@ -27,14 +27,17 @@ Code coverage option is available under the Test menu when you run test methods
 ::: moniker range=">=visualstudio"
 >[!NOTE]
 > Code coverage is available in Visual Studio Enterprise, Community, and Professional editions. In Visual Studio 2022 and previous versions, the code coverage feature was limited to Visual Studio Enterprise edition.
+
 ::: moniker-end
 ::: moniker range="<=vs-2022"
 >[!NOTE]
 > Code coverage is available only with Visual Studio Enterprise.
+
 ::: moniker-end
 
 >[!NOTE]
 > For .NET code coverage, you can alternatively use the command-line tool, [dotnet-coverage](/dotnet/core/additional-tools/dotnet-coverage).
+
 ::: moniker-end
 
 ## Analyze code coverage