From 35ab4293e391a70c49c9c80a8e80e45703ba5e8d Mon Sep 17 00:00:00 2001 From: Mike Richmond Date: Thu, 20 Oct 2016 14:02:45 -0700 Subject: [PATCH] Adding Windows path to the VS Code Debugging setup document. (#2512) --- docs/debugging/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/debugging/README.md b/docs/debugging/README.md index e946d9aa7e..6683190014 100644 --- a/docs/debugging/README.md +++ b/docs/debugging/README.md @@ -13,9 +13,9 @@ addition to being able to build PowerShell, you need: - `powershell` executable in your path (self-host if not on Windows) The .NET CLI tools *must* be on your path for Visual Studio Code. -`Start-PSBootstrap` installs the tools to `~/.dotnet`, +`Start-PSBootstrap` installs the tools to `~/.dotnet` (non-Windows) or `"$env:LocalAppData\Microsoft\dotnet"` (Windows), but does not add this to your `PATH`. -You can do this in Bash with `export PATH=$PATH:$HOME/.dotnet`. +You can do this in Bash with `export PATH=$PATH:$HOME/.dotnet` or in PowerShell with `$env:path = $env:path+";$env:LocalAppData\Microsoft\dotnet"`. Once the extension is installed, you have to open a C# file to force VS Code to install the actual .NET Core debugger (the editor will tell you to do this if