Could not find the Task 'func : host start'

Question

I am trying to run azure on my PC. I am using VS Code, Windows 64 bit

I have installed Azure SDK - .NET Core 2.2.x SDK - Cosmos Emulator - Storage Emulator and also installed azure-functions-core-tools V2

when i try to run debugger by using f5 key , I am getting below error

How did you debug? And please use func --version to check the tools. — George Chen, Jul 04 '19 at 06:41
Check Prerequisites - https://code.visualstudio.com/tutorials/functions-extension/getting-started — Agrawal Shraddha, Jul 04 '19 at 06:41
And about how to debug you could refer to this blog.https://cmatskas.com/debugging-c-net-core-azure-functions-with-vs-code/ — George Chen, Jul 04 '19 at 06:42
@AgrawalShraddha. I have checked. Yeah its installed, but thing is I can't run it by pressing f5, I have to mannualy run `func host start` in VS Code. and my breakpoints are also not working — Sudharshan Nair, Jul 05 '19 at 05:50
@GeorgeChen. Thanks for the link, but i dont think that link would resolve my issue ;-( — Sudharshan Nair, Jul 05 '19 at 05:51
Are you running "func host start" from a terminal window or from the VS Code Run Task option? — PerfectlyPanda, Jul 15 '19 at 17:27

score 20 · Answer 1 · answered Feb 06 '20 at 09:39

20

I fixed this by installing the Azure Functions extension for Visual Studio Code then restarting Visual Studio Code.

Changing terminal did not help.

answered Feb 06 '20 at 09:39

Alastair

201
2
3

9

better wording here is you uninstall and install the Azure Functions extension and it fixes the issue – Ankit Kumar Jan 10 '22 at 13:30

score 8 · Answer 2 · answered Nov 11 '22 at 03:51

8

I resolved this by ensuring I was connected to Azure. Opening Azure on the side menu (Shift+Alt+A) was sufficient.

answered Nov 11 '22 at 03:51

EnterpriseMike

165
2
7

score 6 · Answer 3 · answered Aug 18 '22 at 11:24

6

I had a similar problem. I started VSCode as an Administrator and debugging worked as expected.

answered Aug 18 '22 at 11:24

Ismail

101
1
2

score 4 · Answer 4 · answered Sep 11 '19 at 15:56

I believe this was because your VSCode instance is set to use version 5.0 of Powershell when debugging. I followed these instructions on my machine to reference Powershell Core 6 instead and the debugging worked flawlessly afterward. I intend to put it back for normal development so that I use v5.0 for day-to-day work:

In VSCode: Ctrl-Shift-P
Preferences: Open User Settings Search for: terminal.integrated.shell.windows
Save the original value: "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe" (for use after you finish playing with Azure Functions In Powershell)
Replace it with the new value: "c:/Program Files/PowerShell/6/pwsh.exe"
Save
Restart VSCode

This solved it for me! Thanks – T. de Jong Jan 11 '22 at 10:49 — T. de Jong, Jan 11 '22 at 10:49

score 3 · Answer 5 · answered Jun 28 '21 at 23:21

3

If its a fresh installation of VS Code, this happens if the Python Extension is not installed. Install the recommended extensions and this error went away

answered Jun 28 '21 at 23:21

Priya

31
1

score 2 · Answer 6 · answered Jul 02 '23 at 20:47

2

I had Azure Functions extension installed already. Restarting VS Code resolved the issue.

answered Jul 02 '23 at 20:47

Fayyaz Naqvi

695
7
19

score 1 · Answer 7 · answered Aug 05 '22 at 17:45

1

In my case, the solution was simpler. There was some malformed json code in host.json. As soon as I fixed it, I was able to run the debugger again.

I would review host.json and see if you have the same problem. I hope that helps!

answered Aug 05 '22 at 17:45

Irina

1,333
3
17
37

score 0 · Answer 8 · answered Sep 19 '22 at 01:18

0

This happened when updated the VS code version.

Try uninstalling and reinstalling azure functions extention. It should work then.

answered Sep 19 '22 at 01:18

Rushi patel

522
7
17

score 0 · Answer 9 · answered Oct 13 '22 at 15:56

Assuming you have Azure Function Extensions installed correctly, another way you can see this error is if you change the command line arguments in tasks.json, this will change the generated task label. You can solve it by manually setting the label to match the previously generated one.

Example:

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "func: host start",
      "type": "func",
      "command": "host start --port 5022",
      "problemMatcher": "$func-node-watch",
      "isBackground": true,
      "dependsOn": "npm build (functions)"
    },
    ...
  ]
}

Alternatively you can update the task reference in launch.json to include the command line arguments, but setting the task label will be more resilient to future configuration changes.

sprash95 · Answer 10 · 2022-11-16T04:39:18.087

0

One hack that is working is deploying the Azure Functions to a Function app (not used) from VS Code itself. After this, the functions are running/debugging normally after pressing F5. What I infer is that deployment is initiating the right of terminals or resetting some background variables to right values.

edited Nov 16 '22 at 04:39

answered Nov 07 '22 at 09:34

sprash95

137
9

score 0 · Answer 11 · edited May 17 '23 at 00:18

0

I faced a similar issue, VSC asked me to install the Azure Functions Core Tools, but after I did, I got the message "Could not find the Task 'func : host start'". This happend each time I pressed F5.

None of the solutions from above worked.But finally, I managed to solve it with the method described by @ValentinPetkov:

choco install azure-functions-core-tools-3 --params="'/x64:true'"

edited May 17 '23 at 00:18

Jeremy Caney

7,102
69
48
77

answered May 16 '23 at 21:41

Pablo Castrejón

21
3

score -1 · Answer 12 · answered Jun 14 '21 at 06:20

-1

I had the same issue. Compared the tasks.jason file with that of another project that worked fine and found no difference. Saved my workspace and re-launched vscode. That worked without changing any thing

answered Jun 14 '21 at 06:20

funintech

1

3

this answer has no purpose – Christian Matthew Sep 19 '21 at 17:09

score -1 · Answer 13 · answered Aug 27 '21 at 15:53

I fixed mine using these steps:

Press F1, type settings.json to open the local settings.json file.
Look for the key "terminal.integrated.automationShell.windows" and update to:

"terminal.integrated.automationShell.windows": "c:\windows\system32\cmd.exe"

Could not find the Task 'func : host start'

13 Answers13