edits

Author: Mikejo5000

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/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,9 +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 range=">=visualstudio"
+```
+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
 
 ::: moniker-end
 

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"