PowerShell/.vscode/launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": ".NET Core Launch",
            "type": "coreclr",
            "request": "launch",
            "justMyCode": false,
            "stopAtEntry": true,
            "program": "${workspaceRoot}/debug/powershell",
            "preLaunchTask": "build",
            "externalConsole": true,
            "cwd": "${workspaceRoot}"
        },
        {
            "name": ".NET Core Attach",
            "type": "coreclr",
            "request": "attach",
            "justMyCode": false,
            "processId": "${command:pickProcess}"
        }
    ]
}
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-18 20:22:00 +01:00			`{`
Put version back to make VS Code happy 2016-04-01 19:26:50 +02:00			`"version": "0.2.0",`
Fix up .vscode files 2016-03-31 07:59:48 +02:00			`"configurations": [`
			`{`
			`"name": ".NET Core Launch",`
			`"type": "coreclr",`
			`"request": "launch",`
			`"justMyCode": false,`
			`"stopAtEntry": true,`
Use -Output switch to fix VS Code debugging story 2016-05-06 19:30:48 +02:00			`"program": "${workspaceRoot}/debug/powershell",`
Fix up .vscode files 2016-03-31 07:59:48 +02:00			`"preLaunchTask": "build",`
Enable external console for VS Code debugging Instead of half-running PowerShell with -noninteractive (and expecting the user debugging to enter more arguments), the latest stable version of VS Code allows us to launch an external console. This requires either Gnome Terminal or xterm (sadly not Xfce Terminal), but given either (and xterm is almost always available to install), we can now launch an interactive PowerShell session to debug. 2016-07-22 01:18:32 +02:00			`"externalConsole": true,`
Fix up .vscode files 2016-03-31 07:59:48 +02:00			`"cwd": "${workspaceRoot}"`
			`},`
			`{`
			`"name": ".NET Core Attach",`
			`"type": "coreclr",`
			`"request": "attach",`
			`"justMyCode": false,`
Update launch.json Attach config to use process picker. (#3928) 2017-06-03 19:59:30 +02:00			`"processId": "${command:pickProcess}"`
Fix up .vscode files 2016-03-31 07:59:48 +02:00			`}`
			`]`
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-18 20:22:00 +01:00			`}`