Commit graph

9 commits

Author SHA1 Message Date
Carl Morris 1226540fb7 Quote arguments in .vscode/tasks.json in case of spaces (#10204) 2019-07-29 13:27:41 -07:00
Steve Lee 2f8e691e05 Fix build in vscode (#5453)
- Fix build in vscode
- Add v2.0.0 tasks.json thanks to Keith Hill
- Add '/property:GenerateFullPaths=true' to build to fix the $mscompile 'problem matcher' not working issue.
2017-11-15 11:40:49 -08:00
Steve Lee 33b4e67d37 Change VSCode build task to use pwsh (#5255) 2017-10-30 09:58:44 -07:00
Andrew Schwartzmeyer 4298f11fa4 Fix VS Code debug output (#2425) 2016-10-05 10:47:33 -07:00
v-alexjo d3e2ef5307 Suppressing taskname in tasks.json so 'build' is not being sent as cmd 2016-05-24 15:50:09 -07:00
Andrew Schwartzmeyer 403ba4f735 Use -Output switch to fix VS Code debugging story 2016-05-06 10:30:48 -07:00
Andrew Schwartzmeyer b88980590c Put version back to make VS Code happy 2016-04-01 10:26:50 -07:00
Andrew Schwartzmeyer b8435da8db Fix up .vscode files 2016-03-30 23:30:26 -07:00
Andrew Schwartzmeyer 94e3a905bd Add VS Code launch and task files
This enables building PowerShell through VS Code. The build task
launches the installed version of PowerShell and runs
`Start-PSBuild` (after importing the module).

This enables a `launch` debug task to immediately debug the `powershell`
process, without having to attach to an external process.

The defaults of `justMyCode` and `stopAtEntry` have been reversed, so
that all code is debugged, and the process is stopped at entry for
easier debugging.

Note that an interactive PowerShell process requires access to `stdin`,
which the debug console does not provide, so once it requests access,
`System.Console` will throw a (correct) exception.
2016-03-24 16:26:05 -07:00