vscode-azurefunctions
vscode-azurefunctions copied to clipboard
A warning "No job functions found..." displays in Terminal logs when debugging a C# project
OS: All Azure Resources extension: 20231123.1 Azure Functions Extension: 20231123.5 .NET Core SDK Version: 8.0.100
Repro Steps:
- Create a C# project with HttpTrigger function.
- F5.
- Check whether succeeds to debug the project.
Expect: Succeed to debug the project.
Actual:
A warning "No job functions found..." displays in Terminal logs.
More Info:
- This issue does not reproduce for .NET 6.0 (LTS) runtime.
- This issue does not reproduce for JavaScript/TypeScript/Python/PowerShell project.
Does this occur for every C# project created with .NET 8? As in, does the project fail to debug with any of these options?
@nturinski Yes, except .NET 6.0 LTS runtime.
I am seeing the same thing. Total bare bones project, latest everything. 7.0 LTS with the default HttpTrigger
What's curious is that an existing functions project, also 7.0, is still working and is finding the functions. But I cannot see what's different between the two of them - I've side by sided.
Seems like something to do with the basic template set up perhaps? Something changed?
It does the same for me with 6.0 as well. Both these are isolated
Just to add to this, I found that adding
<FunctionsEnableWorkerIndexing>False</FunctionsEnableWorkerIndexing>
Seems to have worked with the bare bones project...
Thanks for pointing this out. It seems like this bug is related to the worker sdk version. There is a blog post about it here.
There's a bug on the Azure Functions repo tracking it here.
Thanks for updating @nturinski
I am also having issues deploying a function app to Azure itself with this - the azure based function app see's no functions in it - can you confirm whether those local apps when deployed are working for you?
thanks Paul
Are you deploying through the extension? Could I see what your .vscode/settings.json
and .vscode/tasks.json
look like?
EDIT: Also, what extension version are you using? We just released a patch fix yesterday that may have broken deployment.