PowerShell/.vscode/tasks.json

{
    "version": "0.1.0",
    "command": "powershell",
    "isShellCommand": true,
    "showOutput": "always",
    "suppressTaskName": true,
    "args": [ "-command" ],

    "tasks": [
        {
            "taskName": "build",
            "args": [ "Import-Module ${workspaceRoot}/build.psm1; Start-PSBuild -Output ${workspaceRoot}/debug" ],
            "isBuildCommand": true,
            "problemMatcher": "$msCompile"
        }
    ]
}
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.1.0",`
Fix up .vscode files 2016-03-31 07:59:48 +02:00			`"command": "powershell",`
			`"isShellCommand": true,`
Put version back to make VS Code happy 2016-04-01 19:26:50 +02:00			`"showOutput": "always",`
Suppressing taskname in tasks.json so 'build' is not being sent as cmd 2016-05-25 00:50:09 +02:00			`"suppressTaskName": true,`
			`"args": [ "-command" ],`
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
Fix up .vscode files 2016-03-31 07:59:48 +02:00			`"tasks": [`
			`{`
			`"taskName": "build",`
Fix VS Code debug output (#2425) 2016-10-05 19:47:33 +02:00			`"args": [ "Import-Module ${workspaceRoot}/build.psm1; Start-PSBuild -Output ${workspaceRoot}/debug" ],`
Fix up .vscode files 2016-03-31 07:59:48 +02:00			`"isBuildCommand": true,`
			`"problemMatcher": "$msCompile"`
			`}`
			`]`
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			`}`