Closed novenera closed 1 year ago
@novenera thanks for reporting this, to confirm, is this happening on vscode Logic Apps version 1.80.2? cause it may just be that version that is not working. I'd recommend seeing if updating to latest version 2.45.4 fixes your issue. If not we can look into it further
Hi @novenera, did you try to create a normal/simple logic apps project or did you indeed want a workspace with a functions and logic app projects. Just want to confirm if we should change the wording of the second one?
@novenera thanks for reporting this, to confirm, is this happening on vscode Logic Apps version 1.80.2? cause it may just be that version that is not working. I'd recommend seeing if updating to latest version 2.45.4 fixes your issue. If not we can look into it further
Hi @Eric-B-Wu - I am using Logic Apps (Standard) VS Code extension v2.45.4
Also sharing the current version of extensions it depends on: Azurite v3.25.0 Azure Functions v1.12.2 Azure Function Core Tools Version 4.0.4865 .NET 7.0.306
Hi @novenera, did you try to create a normal/simple logic apps project or did you indeed want a workspace with a functions and logic app projects. Just want to confirm if we should change the wording of the second one?
Hi @ccastrotrejo - I created a workspace with a Function and Logic App project, no additional logic added. See screenshots above.
hi @novenera would you mind sharing your csproj file here/ the contents of the file?
hi @novenera would you mind sharing your csproj file here/ the contents of the file?
@swghimire - See attached.
For some reason you are missing a launch.json file in the LogicApps/.vscode directory. Can you please insert a file named "launch.json" in LogicApp/.vscode? And add this as the file content. I'm not sure if that will fix the entire issue, but that is something that came to my immediate attention.
{
"version": "0.1.0",
"configurations": [
{
"name": "Attach to logic app",
"type": "coreclr",
"request": "attach",
"processId": "${command:azureLogicAppsStandard.pickProcess}"
}
]
}
Additionally, please check the version of azure core tools you have in C:
Thanks @swghimire. I am going to check if there was a code change or anything on why the file wasn't created.
C: .azure-functions-core-tools\Functions\ExtensionBundles\Microsoft.Azure.Functions.ExtensionBundle.Workflows
Hi @swghimire -
I have added launch.json to LogicApp.vscode as follows:
I also checked the version of Azure Function Core Tools and see that I have v 1.28.4...
Nonetheless, I deleted that folder to force reinstall.
Tried opening the workflow designer again and got the same error:
However, I did some digging and found that this might be related to issue with Azure Function Core tools and .NET 6.0 needed to be reinstalled (https://github.com/Azure/azure-functions-core-tools/issues/3115). I did just that and now I am able to load the workflow designer.
Thanks for your help @swghimire and @ccastrotrejo !
I am glad it worked out. Thanks for letting us know about the solution!
Describe the Bug with repro steps
Select Create new Logic App workspace.
Follow the prompts which would create the following workspace with a folder for Function App project and another for Logic App project.
Right-click workflow.json and choose Open Designer
Workflow designer does not start.
Logs returned as follows:
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
Screenshots or Videos
No response
Browser
Debugging from VS Code 1.80.2
Additional context
Logic Apps (Standard) VS Code extension v2.45.4 Azurite v3.25.0 Azure Functions v1.12.2 Azure Function Core Tools Version 4.0.4865 Function Runtime Version: 4.12.2.19454 .NET 7.0.306
AB#24719974