From a86679a55bedc7756e17764ba9ede8282293dab0 Mon Sep 17 00:00:00 2001
From: Matt Wojciakowski <mattwoj@microsoft.com>
Date: Mon, 13 Dec 2021 14:32:56 -0800
Subject: [PATCH] Sync main > live (#463)

* Update dynamic-profiles.md (#438)

* Update dynamic-profiles.md

Create section for dynamic profile for `Developer Powershell for VS 2019`

* Update dynamic-profiles.md

Update name and remove `startingDirectory`

* Update dynamic-profiles.md

Explain a little better

* Update VS version info in 3rd party (#462)

Co-authored-by: Shubham Gogna <36936863+shgogna@users.noreply.github.com>
---
 TerminalDocs/dynamic-profiles.md | 30 ++++++++++++++++++++++++++++--
 1 file changed, 28 insertions(+), 2 deletions(-)

diff --git a/TerminalDocs/dynamic-profiles.md b/TerminalDocs/dynamic-profiles.md
index a7be5723..93f26070 100644
--- a/TerminalDocs/dynamic-profiles.md
+++ b/TerminalDocs/dynamic-profiles.md
@@ -140,12 +140,38 @@ For more details, see the Terminals section of the [MSYS2 documentation](https:/
 
 ### Developer Command Prompt for Visual Studio
 
-Assuming that you've installed [Visual Studio 2019 Professional](https://visualstudio.microsoft.com/downloads/):
+Assuming that you've installed [Visual Studio](/visualstudio/install/install-visual-studio):
 
 ```json
 {
-    "name": "Developer Command Prompt for VS 2019",
+    "name": "Developer Command Prompt",
     "commandline": "cmd.exe /k \"C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/Common7/Tools/VsDevCmd.bat\"",
     "startingDirectory": "%USERPROFILE%"
 }
 ```
+
+> [!NOTE]
+> Visual Studio’s “Developer Powershell” and “Developer Command Prompt” include shell environment variables and tools settings that would not be available in the default Command Prompt or Powershell instance.
+
+### Developer Powershell for Visual Studio
+
+Assuming that you've installed [Visual Studio](/visualstudio/install/install-visual-studio):
+
+```json
+{
+    "name": "Developer Powershell",
+    "commandline": "powershell.exe -noe -c \"&{Import-Module \"\"\"C:/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/Common7/Tools/Microsoft.VisualStudio.DevShell.dll\"\"\"; Enter-VsDevShell 994a9d58}\""
+}
+```
+
+To find the `commandline` path to use in the Windows Terminal settings for your Visual Studio instance:
+
+1. Find the shortcut to `Developer Powershell for VS 2019` in the start menu
+2. Right-click and select `Open File Location`
+3. Right-click and select `Properties` on the shortcut
+4. Inspect the `Target` field. It will be some value like `C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -noe -c "&{Import-Module """C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\Tools\Microsoft.VisualStudio.DevShell.dll"""; Enter-VsDevShell 994a9d58}"`
+5. Use `Target` field value to update the file path for `Import-Module` in the profile `commandline`
+6. Use `Target` field value to update the unique instance ID used with the `Enter-VsDevShell` command in the profile `commandline`
+
+> [!NOTE]
+> Visual Studio’s “Developer Powershell” and “Developer Command Prompt” include shell environment variables and tools settings that would not be available in the default Command Prompt or Powershell instance.