VS Code extension detects latest Azure Functions Core Tools detected as v4.0.1
HolisticDeveloper opened this issue · comments
I've recently moved to a new computer and I'm trying to set up Durable Functions Monitor in VS Code again. After installing Azure Function Core Tools globally via chocolatey (choco install azure-functions-core-tools), I get the following error when trying to attach to a task hub:
Default backend now requires at least Azure Functions Core Tools v4.0.4629 (currently discovered is v4.0.1). Install latest Azure Functions Core Tools or, alternatively, select a custom backend in extension's settings.
The package version installed by chocolatey is 4.0.5907, and I get the following output from func.exe:
Core Tools Version: 4.0.1 Commit hash: N/A +807e89766a92b14fd07b9f0bc2bea1d8777ab209 (32-bit)
Function Runtime Version: 4.834.3.22875
Have I misconfigured something?
@HolisticDeveloper , can you post the output from your 'DURABLE FUNCTIONS MONITOR' output channel (omitting anything sensitive), when trying to attach?
@HolisticDeveloper , do you still need help on this?
Sorry for the delay, I got sidetracked by a pressing issue...
Here's the output:
yarn global bin failed. Command failed: yarn global bin
'yarn' is not recognized as an internal or external command,
operable program or batch file.
Using Functions host: funcI've learned that yarn isn't supposed to be installed globally anymore but I did run corepack enable which made the yarn error go away. Now my output is just the last line:
Using Functions host: func@HolisticDeveloper , the logic of discovering the path to func.exe is here.
It is a multi-stage process, that checks all known homes of Azure Functions Core Tools (as an npm package, via yarn, as an .MSI file etc.). If you're saying that you only see that one line in the output, then I'm afraid I cannot explain it.
Anyway, you can always explicitly specify the full path to func.exe via this setting:
Well, even the tool itself thinks it is old. 🤷🏻♂️
Maybe there has been a change in what is reported by func --version. I don't have older versions around to check.
Since the extension is looking for a minimum version of 4.0.4629, I decided to download that version and set an explicit path to it. The download links were contained in %LocalAppData%\AzureFunctionTools\feed-v{0000000}.json (where 0000000 varies). The output of func --version for this binary is 4.0.4629.
The extension is working after doing this. Feel free to close if you don't plan to work around this issue.