Prelaunch task not working with tasks v2.

[dbaeumer]

• VSCode Version: 1.10.0

From #981

I have another problem with this:
in launch.json (v 0.2.0) i have added some debugging entries with a preLaunchTask.
when i now debug, i get: There is a task {0} running. Can not run pre launch task build.
if i empty the content of the preLaunchTask, it works but the code is not built before.
Could it be that upgrading the tasks,json to v2.0.0 while having a launch,json at version 0.2.0 creates some incompatibilities?
launch.json
"version": "0.2.0",
"configurations": [{
{
"name": ".NET Core Launch (myapp)",
"type": "coreclr",
"request": "launch",
"preLaunchTask": "build",
"program": "${workspaceRoot}/Services/myapp/src/bin/Debug/netcoreapp1.1/myapp.dll",
"args": [],
"cwd": "${workspaceRoot}/Services/myapp/src/bin/Debug/netcoreapp1.1/",
"stopAtEntry": false,
"externalConsole": false,
"env": {
"ASPNETCORE_ENVIRONMENT": "Local",
"ASPNETCORE_URLS": "http://*:5000"
}
}]
tasks.json
"version": "2.0.0",
"command": "",
"isShellCommand": true,
"args": [],
"tasks": [{
"taskName": "build",
"command": "dotnet",
"args": [
"build"
],
"options": {
"cwd": "${workspaceRoot}"
},
"isBuildCommand": true,
"showOutput": "always",
"problemMatcher": "$msCompile"
},
//... some other tasks here not related to build and a dependency between those.
]}

[Jonathan34]

Thanks!

[dbaeumer]

OK. The problem seems to be that the terminal doesn't signal a process end if that process has never written to the console. Therefore the debugger thinks that the build hasn't finished.

[dbaeumer]

Dups #23119

[Jonathan34]

@dbaeumer This still does not work with Version 1.11.0-insider although i see the dup is set as fixed.
There is a task {0} running. Can not run pre launch task build.

tasks.json is "version": "2.0.0",
and launch.json is "version": "0.2.0",

[dbaeumer]

@Jonathan34 this is strange. I tested this two days ago and it worked for me without any problems using a comparable TS setup.

[dbaeumer]

@Jonathan34 can you provide me with a sample I can clone to further investigate ?

[dbaeumer]

Here is what I see with dotnet core and a simple console app.

[dbaeumer]

So there must be something different with our setup which I don't see.

[Jonathan34]

I just received an update to commit: cc46bbf (2017-03-31T13:40:54.578Z) and now it seems to work!

I did an update yesterday, may be it was not there yet?

Can be closed!

[alexriedl]

I just got the latest inside build and I am still having this issue. It seems to happen after I run a different task, then try to launch my application.
Example steps I ran:

1. "ctrl+p" - type in "task test"
2. Let tests run and finish
3. "f5" - to launch the application

There is a task {0} running. Can not run pre launch task build. message pops up.

[dbaeumer]

@alexriedl thanks a lot for the steps. Was able to reproduce.

[Jonathan34]

Sorry, if i click the play button on the top left to start debugging, it says There is a task {0} running. Can not run pre launch task build. so this is not yet fixed i guess.

I can send the launch.json and tasks.json if you need, just give me one email address

Updated up to 2017-04-03T05:22:32.677Z

[dbaeumer]

@Jonathan34 this needs a released insider build which has not happened yet since we are in endgame process. The build must be at least 2017-04-04:....

[dbaeumer]

If you can still reproduce in a newer build can you please provider a reproducible case. Simply having the tasks.json and launch.json is most of the time not enough. Best would be a GitHub repository to clone from.

[Jonathan34]

@dbaeumer works with 2017-04-04T10:14:08.729Z!
thanks

[alexriedl]

The issue is still happening with the insider build 2017-04-04T10:22:56:510Z.

I through together a small project that is structured similar to my project to demo the issue in my github. Steps to reproduce are in the readme. Let me know if you need any other details.

[Jonathan34]

yes i confirm @alexriedl ! i just got it again... not sure what happens :s

[dbaeumer]

@alexriedl @Jonathan34 sorry, my fault. The fix went into master, but the current insiders are build for the release/1.11 branch. When we have released 1.11 the insider will switch to master again and then the fix will be available there. Sorry for the confusion around this.

[jagadeesh1492]

any solution for this https://stackoverflow.com/questions/43627751/visual-studio-code-could-not-find-the-prelaunchtask-build#

[dbaeumer]

@jagadeesh1492 This got addressed in the latest inside build and will be available in the next release. A workaround is to close and reopen VS Code on the workspace.