Azure / Azure/azure-functions-core-tools
Logic App (Standard) - Unable to find Microsoft.Azure.Functions.ExtensionBundle.Workflows
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 498
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 14
Description
When attempting to debug a Logic App (Standard) app in VS Code, I seem to be running into the same issue as stated at azure/logicapps#518.
This seems to be a problem only when debugging in VS Code. If I run `func host start`, the Logic App starts successfully. Running `func host start --verbose`, shows the runtime does find the extension bundle, but at a different location, **/home/vscode/data/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Workflows**.
I do have a folder at ~/.azure-functions-core-tools/Functions/ExtensionBundles, but it doesn't contain Microsoft.Azure.Functions.ExtensionBundle.Workflows, only Microsoft.Azure.Functions.ExtensionBundle.
- What func.exe returns: /home/vscode/.azure-functions-core-tools/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Workflows
- Where the bundle actually is: /home/vscode/data/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle.Workflows
It seems that the Logic Apps VSCode extension is asking `func.exe` for the path to the bundle, and the path returned is different than the actual location of the bundle.


Contributor guide
Research direction
Start by reproducing the issue with `func host start` and `func host start --verbose` while debugging the Logic App in VS Code. Compare the path returned by `func.exe` with the bundle location under `/home/vscode/data/Functions/ExtensionBundles`; done means VS Code debugging locates and loads `Microsoft.Azure.Functions.ExtensionBundle.Workflows` successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, vscode
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100