Commit Graph

8 Commits

Author SHA1 Message Date
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
77ffc715dc Make VS Code debug powershell with -NonInteractive 2016-05-06 10:48:01 -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
18ba3f3365 Fix VS Code attach debugging configuration
Needs to be `processName`, not `program`. Go figure.
2016-03-26 15:27:15 -07:00
Andrew Schwartzmeyer
840d14e6df Add attach configuration 2016-03-25 14:16:38 -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