Instructions for setting up a custom code workspace don't work as described

TWolversonReply commented 1 week ago

Describe the Bug with repro steps

Follow https://learn.microsoft.com/en-us/azure/logic-apps/create-run-custom-code-functions exactly
At the step 'Debug your code and workflow`, clicking 'Attach to logic app' yields the following errors in the terminal:

Could not execute because the specified command or file was not found.

Possible reasons for this include:

You misspelled a built-in dotnet command.
You intended to execute a .NET program, but dotnet-C:\Users\t_wol.azure-functions-core-tools\Functions\ExtensionBundles\Microsoft.Azure.Functions.ExtensionBundle.Workflows\1.70.60\bin\Microsoft.Azure.Workflows.BuildTasks.DebugSymbolGenerator.dll does not exist.
You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.
Executing task: C:\Users\t_wol.azurelogicapps\dependencies\FuncCoreTools\func host start

Unable to find project root. Expecting to find one of host.json, local.settings.json in project root.

What type of Logic App Is this happening in?

Standard (VSCode)

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

No response

Screenshots or Videos

No response

Browser

nothing to do with the browser

Additional context

No response

TWolversonReply commented 1 week ago

The suggestion on Mike Stephenson's blog suggesting that this is a corrupt directory under the extension bundles directory seemed to bear out, the version specified in the error message was completely empty, and deleting it causes the error regarding the DebugSymbolGenerator.dll to go away.

The error message about host.json persists though, and I can't tell where it expects to find this. The logic app folder, the one I am trying to debug, does have a host.json.

TWolversonReply commented 1 week ago

After further investigation, I've found that opening the workspace progresses past this error, although I have other parameterisation-related issues left to resolve. The screenshots show the workspace is open, but I can't find anywhere in the text that says to open it. The debug tab will present the 'Attach to logic app' option in both modes, and one mode - open the root of the repo - doesn't work. This begs the question, what does it mean to 'open a workspace', anyway? Why can't it just work from the repo-root, which is what most developers will want to do?

Azure / LogicAppsUX