Adding Windows path to the VS Code Debugging setup document. (#2512)

This commit is contained in:
Mike Richmond 2016-10-20 14:02:45 -07:00 committed by Dongbo Wang
parent ed38d70cf6
commit 35ab4293e3

View File

@ -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